From: Mike Stump <mrs@apple.com>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: dave.korn@artimi.com (Dave Korn),
pkoning@equallogic.com (Paul Koning),
gcc@sources.redhat.com, sjackman@gmail.com (Shaun Jackman)
Subject: Re: memcpy to an unaligned address
Date: Tue, 02 Aug 2005 21:05:00 -0000 [thread overview]
Message-ID: <33EADFBB-0C16-4FD9-BC0D-E681C0A61C46@apple.com> (raw)
In-Reply-To: <200508022037.j72Kbr4T012558@earth.phy.uc.edu>
On Aug 2, 2005, at 1:37 PM, Andrew Pinski wrote:
> No it is not,
:-) Ah, yes, the old, we don't have pointers to unaligned types
problem... anyway, we can at least agree that this is a gapping hole
people can drive trucks though in the type system, but I'm still
claiming it isn't a feature on theoretic grounds.
:-(
Shaun, want to do up an entry in the manual describing this? We have
known about this for years and years, but, we don't do a good job
communicating it to users. Essentially, & doesn't work as one would
expect on unaligned data, as it produces a pointer to an aligned
object instead of a pointer to unaligned object. Essentially, we
don't have a type system that contains pointer to unaligned types.
The compiler then goes on to make codegen choices based upon the fact
that the data are known to be aligned, and bad things happen.
next prev parent reply other threads:[~2005-08-02 21:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 17:32 Shaun Jackman
2005-08-02 17:43 ` Dave Korn
2005-08-02 19:13 ` Shaun Jackman
2005-08-02 19:19 ` Paul Koning
2005-08-02 19:26 ` Shaun Jackman
2005-08-02 19:40 ` Dave Korn
2005-08-02 19:48 ` Paul Koning
2005-08-02 20:15 ` Shaun Jackman
2005-08-02 20:29 ` Paul Koning
2005-08-02 20:29 ` Mike Stump
2005-08-02 20:38 ` Andrew Pinski
2005-08-02 20:45 ` Ian Lance Taylor
2005-08-02 21:30 ` Mike Stump
2005-08-02 21:34 ` Joe Buck
2005-08-03 18:00 ` Richard Henderson
2005-08-03 18:15 ` Shaun Jackman
2005-08-03 18:19 ` Dave Korn
2005-08-03 21:26 ` Richard Henderson
2005-08-04 4:42 ` Ian Lance Taylor
2005-08-04 12:40 ` Paul Koning
2005-08-02 20:46 ` Paul Koning
2005-08-02 22:17 ` Shaun Jackman
2005-08-03 17:16 ` Paul Koning
2005-08-02 22:26 ` Shaun Jackman
2005-08-02 22:29 ` Shaun Jackman
2005-08-02 21:05 ` Mike Stump [this message]
2005-08-02 21:11 ` Joe Buck
2005-08-02 22:15 ` Shaun Jackman
2005-08-02 22:12 ` Joe Buck
2005-08-02 17:48 ` Falk Hueffner
2005-08-02 18:03 ` Mike Stump
[not found] <345be691050804025955c0b4ab@mail.gmail.com>
2005-08-04 15:06 ` Shaun Jackman
2005-08-04 15:09 ` Christian Joensson
2005-08-05 8:41 ` Carl Whitwell
2005-08-05 16:09 ` Shaun Jackman
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=33EADFBB-0C16-4FD9-BC0D-E681C0A61C46@apple.com \
--to=mrs@apple.com \
--cc=dave.korn@artimi.com \
--cc=gcc@sources.redhat.com \
--cc=pinskia@physics.uc.edu \
--cc=pkoning@equallogic.com \
--cc=sjackman@gmail.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).