public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vda dot linux at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/27537] XMM alignment fault when compiling for i386 with -Os Date: Mon, 23 Jul 2007 00:48:00 -0000 [thread overview] Message-ID: <20070723004814.4686.qmail@sourceware.org> (raw) In-Reply-To: <bug-27537-12669@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from vda dot linux at googlemail dot com 2007-07-23 00:48 ------- You have it reversed here: "8. Stack alignment is already implemented in Gcc and existing code relies on it." No, stack alignment is _not_ in current de-facto i386 Linux ABI and there are tons of existing object code which will call new shiny 4.2.x compiled SSE code without aligning stack first. kaboom. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27537
next prev parent reply other threads:[~2007-07-23 0:48 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-10 19:54 [Bug c++/27537] New: XMM alignment fault when compiling for i386 with -Os. Needs ABI specification agner at agner dot org 2006-05-10 20:39 ` [Bug target/27537] " pinskia at gcc dot gnu dot org 2006-05-10 20:44 ` pinskia at gcc dot gnu dot org 2006-05-10 20:50 ` [Bug target/27537] XMM alignment fault when compiling for i386 with -Os pinskia at gcc dot gnu dot org 2006-05-11 7:11 ` agner at agner dot org 2006-06-07 15:58 ` hjl at lucon dot org 2006-06-08 6:35 ` agner at agner dot org 2006-08-03 16:58 ` hjl at lucon dot org 2006-08-03 20:20 ` agner at agner dot org 2006-08-20 22:30 ` mmitchel at gcc dot gnu dot org 2006-08-21 17:42 ` hjl at lucon dot org 2006-08-23 8:04 ` agner at agner dot org 2006-09-08 0:46 ` hjl at lucon dot org 2006-09-11 21:34 ` hjl at gcc dot gnu dot org 2006-09-12 2:55 ` hjl at gcc dot gnu dot org 2007-07-23 0:04 ` vda dot linux at googlemail dot com 2007-07-23 0:48 ` vda dot linux at googlemail dot com [this message] 2007-08-26 7:58 ` zuxy dot meng at gmail 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=20070723004814.4686.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).