public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "whaley at cs dot utsa dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38496] Gcc misaligns arrays when stack is forced follow the x8632 ABI
Date: Fri, 12 Dec 2008 00:53:00 -0000	[thread overview]
Message-ID: <20081212005142.31940.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38496-12761@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from whaley at cs dot utsa dot edu  2008-12-12 00:51 -------
>I suppose that by "32-bit ABI for the x86" you mean a document with
>1990-1996 SCO copyrights.

I was going by the linux standards base, which still links to:
   http://www.caldera.com/developers/devspecs/abi386-4.pdf
which I believe is still the current official ABI of Linux.

>This document should be considered of only marginal relevant to current
>systems; it may have described an ABI for some particular system that is
>>now obsolete, but is not an accurate description of (for example) the ABI
>used on IA32 GNU/Linux

I thought that was precisely what the linux standards base was, and it says
word (4-byte) alignment of the stack.

>which is a de facto ABI with no written document corresponding precisely.

This is a link where people mention that fact that gcc is behaving
non-standardly, so people who want to interoperate with gcc better adopt their
non-standard behavior.  How do you like it when MS does that?  It seems
incredibly foolish to me that just because gcc doesn't want to do some trivial
bit twiddling in the function prologue, you've decided to break the ABI, all so
that you can lose performance when people need ABI compliance, as well as
making interoperation much harder for everyone.


-- 


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


  parent reply	other threads:[~2008-12-12  0:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 22:54 [Bug fortran/38496] New: " whaley at cs dot utsa dot edu
2008-12-11 23:03 ` [Bug fortran/38496] " whaley at cs dot utsa dot edu
2008-12-11 23:05 ` [Bug target/38496] " pinskia at gcc dot gnu dot org
2008-12-11 23:06 ` pinskia at gcc dot gnu dot org
2008-12-11 23:26 ` whaley at cs dot utsa dot edu
2008-12-11 23:29 ` pinskia at gcc dot gnu dot org
2008-12-11 23:44 ` whaley at cs dot utsa dot edu
2008-12-12  0:02 ` joseph at codesourcery dot com
2008-12-12  0:53 ` whaley at cs dot utsa dot edu [this message]
2008-12-12  1:06 ` hjl dot tools at gmail dot com
2008-12-12  1:26 ` joseph at codesourcery dot com
2008-12-12  1:50 ` whaley at cs dot utsa dot edu
2008-12-15  0:23 ` joseph at codesourcery dot com
2008-12-15 14:54 ` whaley at cs dot utsa dot edu
2008-12-15 18:19 ` joseph at codesourcery dot com
2008-12-15 21:34 ` whaley at cs dot utsa dot edu
2008-12-15 21:39   ` Andrew Thomas Pinski
2008-12-15 21:40 ` pinskia at gmail dot com
2008-12-15 22:03 ` whaley at cs dot utsa dot edu
2008-12-15 23:02   ` Andrew Pinski
2008-12-15 23:03 ` pinskia at gmail dot com
2008-12-15 23:40 ` whaley at cs dot utsa dot edu
2008-12-16  0:10 ` joseph at codesourcery dot com
2009-03-18 13:25 ` sliwa at cft dot edu dot pl
2009-07-23 13:14 ` jakub at gcc dot gnu dot org
2009-07-23 14:35 ` mikulas at artax dot karlin dot mff dot cuni dot cz
2009-07-24 12:16 ` rguenth at gcc dot gnu dot org
2009-07-24 17:05 ` whaley at cs dot utsa dot edu
2009-07-31  1:18 ` mikulas at artax dot karlin dot mff dot cuni dot cz
2009-10-23  9:45 ` rguenth at gcc dot gnu dot org
     [not found] <bug-38496-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 13:12 ` jackie.rosen at hushmail 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=20081212005142.31940.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).