From: Falk Hueffner <falk@debian.org>
To: Shaun Jackman <sjackman@gmail.com>
Cc: gcc@sources.redhat.com
Subject: Re: memcpy to an unaligned address
Date: Tue, 02 Aug 2005 17:48:00 -0000 [thread overview]
Message-ID: <87d5ow1b92.fsf@debian.org> (raw)
In-Reply-To: <7f45d9390508021032aea5a61@mail.gmail.com> (Shaun Jackman's message of "Tue, 2 Aug 2005 11:32:38 -0600")
Shaun Jackman <sjackman@gmail.com> writes:
> In a typical Ethernet/IP ARP header the source IP address is
> unaligned. Instead of using...
> out->srcIPAddr = in->dstIPAddr;
> ... I used...
> memcpy(&out->srcIPAddr, &in->dstIPAddr, sizeof(uint32_t));
> ... to account for the unaligned destination. This worked until gcc 4,
> which now generates a simple load/store.
> ldr r3, [r6, #24]
> adds r2, r4, #0
> adds r2, #14
> str r3, [r2, #0]
> A nice optimisation, but in this case it's incorrect. $r4 is aligned,
> and the result of adding #14 to $r4 is an unaligned pointer.
It isn't incorrect; gcc can assume that pointers are always correctly
aligned for their type. Anything else would result in horrible code.
If your program forms a pointer that is not properly aligned, it is
already invalid, and later breakage is only a symptom of that.
--
Falk
next prev parent reply other threads:[~2005-08-02 17:48 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 ` 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
2005-08-02 21:11 ` Joe Buck
2005-08-02 22:15 ` Shaun Jackman
2005-08-02 22:12 ` Joe Buck
2005-08-02 20:29 ` Paul Koning
2005-08-02 17:48 ` Falk Hueffner [this message]
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=87d5ow1b92.fsf@debian.org \
--to=falk@debian.org \
--cc=gcc@sources.redhat.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).