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: Mon, 15 Dec 2008 21:34:00 -0000 [thread overview] Message-ID: <20081215213300.32138.qmail@sourceware.org> (raw) In-Reply-To: <bug-38496-12761@http.gcc.gnu.org/bugzilla/> ------- Comment #15 from whaley at cs dot utsa dot edu 2008-12-15 21:32 ------- >GCC chose to change the *unwritten* standard for the ABI in use for IA32 GNU/Linux. This is not true. Prior to this change, gcc followed the *written* standard provided by the LSB. You chose to violate the standard, or to put as you seem to prefer, you chose to declare that you followed no standard, as the written standard previously used by pretty much all OSes on the x86 was suddenly unusable. >The SCO document may have been useful before SSE, but processor architecture and language developments have made it problematic for many years. This is not even trivially true. SSE requires no change in the ABI to support: it is purely convenience to start with a known 16-byte alignment: an andb and a register save/restore fixes the problem completely, without abandoning the standard. I believe gcc still abides by this "problematic for many years" standard in all respects except stack alignment, which is a trivial problem to solve and still abide by the standard. So, you abandoned standard compliance to solve a minor irritant, that you yourself have fixed in the new 4.4 series. >From 4.4 on, you broke the standard for no gain at all, since you have now added the minor complexity of manually aligning the stack anyway. Of course the standard seems outdated to us: it is supporting an architecture that is decades old, and that is the strength of it. If you want the shiny new stuff, you go to x86-64. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38496
next prev parent reply other threads:[~2008-12-15 21:34 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 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 [this message] 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=20081215213300.32138.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: linkBe 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).