From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] c compiler bug
Date: Wed, 15 Sep 2010 09:37:50 +0100 [thread overview]
Message-ID: <805e42c0155b88900921831b032c748e@terzarima.net> (raw)
In-Reply-To: <2947a8c22b8274d84c68f633ae888de7@plan9.bell-labs.com>
actually, it gets worse. i looked up the stuff for ARM, and it was much
as i expected, but they also pointed out another problem, obvious in retrospect.
you say you want structure assignments to work, or at least not
fail. fair enough, but what about this:
S s;
int *p = &s.c;
*p = 1;
int x = *p;
the point is that in general given an int*, there's no way to know that
the target is misaligned. ARM thoughtfully provides a __packed attribute,
as in
__packed int *p;
and then an appropriate sequence of byte-by-byte loads (or stores) will be
used to access it, but a normal int* will produce an alignment trap.
next prev parent reply other threads:[~2010-09-15 8:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 15:25 erik quanstrom
2010-09-14 20:20 ` Charles Forsyth
2010-09-14 20:59 ` Brantley Coile
2010-09-14 21:07 ` ron minnich
2010-09-15 7:06 ` Sape Mullender
2010-09-15 8:30 ` Charles Forsyth
2010-09-15 8:37 ` Charles Forsyth [this message]
2010-09-15 12:20 ` Charles Forsyth
2010-09-15 8:32 ` Charles Forsyth
2013-02-17 2:38 erik quanstrom
2013-02-18 13:02 ` Comeau At9Fans
2013-02-18 14:38 ` Charles Forsyth
2013-02-18 15:02 ` erik quanstrom
2013-02-18 15:10 ` Charles Forsyth
2013-02-21 17:17 ` Comeau At9Fans
2013-02-21 17:13 ` Comeau At9Fans
2013-02-21 18:13 ` hiro
2013-02-21 18:22 ` John Floren
2013-02-21 18:39 ` erik quanstrom
2013-02-21 18:46 ` Comeau At9Fans
2013-02-21 18:51 ` John Floren
2013-02-21 19:36 ` hiro
2013-02-21 19:58 ` andrey mirtchovski
2013-02-21 20:24 ` Matthew Veety
2013-02-21 20:27 ` David Leimbach
2013-02-21 20:36 ` steve
2013-02-21 18:51 ` Kurt H Maier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=805e42c0155b88900921831b032c748e@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).