public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rth@gcc.gnu.org
To: 136659@bugs.debian.org, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, lists@lina.inka.de, nobody@gcc.gnu.org,
	rth@gcc.gnu.org
Subject: Re: target/9080: optimisation on sparc leads to unalligned access in memcpy
Date: Sun, 26 Jan 2003 10:13:00 -0000	[thread overview]
Message-ID: <20030126101338.2759.qmail@sources.redhat.com> (raw)

Synopsis: optimisation on sparc leads to unalligned access in memcpy

Responsible-Changed-From-To: unassigned->rth
Responsible-Changed-By: rth
Responsible-Changed-When: Sun Jan 26 10:13:38 2003
Responsible-Changed-Why:
    .
State-Changed-From-To: open->closed
State-Changed-By: rth
State-Changed-When: Sun Jan 26 10:13:38 2003
State-Changed-Why:
    I'm fairly sure this has been discussed before, but I can't find
    the reference right away.  The problem is known, and I consider
    the input program incorrect.
    
    The problem is that alignof(struct iphdr) == 4, and yet the
    given pointer to that structure is only 2 byte aligned.  This
    violates section 6.3.2.3/7, to wit:
    
            If the resulting pointer is not correctly aligned for the
            pointed-to type, the behavior is undefined.
    
    GCC uses this clause to infer from the type of the pointer the
    alignment that it *must* have.
    
    There are two solutions for this piece of code.
    
    One, use packed data structures, so that they are 1 byte aligned.
    In this case something like
    
            struct iphdr_u {
              struct iphdr h __attribute__((packed));
            };
    
    followed by
            &tmp_iphdr->h.saddr
    
    Two, don't cast to struct iphdr at all.  Instead use offsetof
    to find the proper displacement into the buffer.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9080


             reply	other threads:[~2003-01-26 10:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26 10:13 rth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-28  5:56 Matthias Klose

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=20030126101338.2759.qmail@sources.redhat.com \
    --to=rth@gcc.gnu.org \
    --cc=136659@bugs.debian.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=lists@lina.inka.de \
    --cc=nobody@gcc.gnu.org \
    /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).