From: "Shaun Jackman" <shaunj@gray-interfaces.com>
To: "crossgcc list" <crossgcc@sources.redhat.com>
Subject: unaligned pointers
Date: Thu, 14 Sep 2000 08:49:00 -0000 [thread overview]
Message-ID: <007d01c01e63$59b1e440$6801a8c0@gray.internal> (raw)
Can GCC generate the code necessary to load from and store to unaligned
pointers? Ditto for unaligned members of structures.
In the case of structure members the compiler knows compile-time which are
aligned and which are unaligned, and genereate the respective code. Although
it doesn't at the moment. Nor does it warn me of the access to an unaligned
structure member (w/ -Wall).
For pointers though, how do I indicate a given pointer can possibly be
unaligned, and needs odd-alignment safe dereferncing?
Thanks,
Shaun Jackman
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-09-14 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-14 8:49 Shaun Jackman [this message]
2000-10-29 19:19 ` Jonathan Larmour
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='007d01c01e63$59b1e440$6801a8c0@gray.internal' \
--to=shaunj@gray-interfaces.com \
--cc=crossgcc@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).