public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/30826] alignment error when optimizing with inlining
Date: Fri, 16 Feb 2007 23:26:00 -0000	[thread overview]
Message-ID: <20070216232610.26348.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30826-9385@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from sje at cup dot hp dot com  2007-02-16 23:26 -------
It looks like GCC is running afoul of the IA64 Runtime standard.  In section
8.6 (return values) it says that aggregates larger than 256 bytes (mallinfo is
320 bytes), the caller must allocate a buffer and pass a pointer to that buffer
to the callee.  It also says that the buffer must be 16 byte aligned.  GCC is
passing a pointer to the local mi variable.  That local variable is only
required to have 4 byte alignment because that is the maximum alignment of any
of its fields.

The inlining is incidental in that it is what results in mi being 4 (but not 8)
byte aligned and thus causing the segfault.

There is another bug (PR15087) about GCC not obeying the IA64 runtime alignment
requrements in other cases.


-- 

sje at cup dot hp dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sje at cup dot hp dot com
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2007-02-16 23:26:10
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30826


  parent reply	other threads:[~2007-02-16 23:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 17:45 [Bug tree-optimization/30826] New: " michael dot haubenwallner at salomon dot at
2007-02-16 17:50 ` [Bug tree-optimization/30826] " michael dot haubenwallner at salomon dot at
2007-02-16 17:56 ` michael dot haubenwallner at salomon dot at
2007-02-16 17:58 ` michael dot haubenwallner at salomon dot at
2007-02-16 18:06 ` michael dot haubenwallner at salomon dot at
2007-02-16 23:26 ` sje at cup dot hp dot com [this message]
2007-02-17 14:35 ` [Bug target/30826] " michael dot haubenwallner at salomon dot at
2007-02-17 15:01 ` michael dot haubenwallner at salomon dot at
2007-02-19 12:19 ` michael dot haubenwallner at salomon dot at
2007-02-20 17:06 ` sje at cup dot hp dot com
2008-01-07 18:32 ` [Bug target/30826] alignment error tom dot culliton at oracle dot com

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=20070216232610.26348.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).