public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pip88nl at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/47120] New: -malign-double does not align doubles in function calls Date: Wed, 29 Dec 2010 15:54:00 -0000 [thread overview] Message-ID: <bug-47120-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47120 Summary: -malign-double does not align doubles in function calls Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: pip88nl@gmail.com According to the gcc manual, -malign-double creates object code with an ABI that is incompatible to code that was not compiled with that switch. With this switch, structs containing doubles are aligned correctly (according to double's alignment requirements) but doubles passed to functions are not. E.g.: void foo (int i, double d); int main () { foo (1, 2); return 0; } On x86, this will emit code storing the double value of 2.0 to a word-aligned stack location, not a double-word aligned location, as the manual implies. I suppose the reason for not aligning doubles on a two word boundary in this instance is that it would, in addition to the struct ABI, break the x86 calling convention. However, not aligning the double correctly will make code fail that requires aligned access.
next reply other threads:[~2010-12-29 15:54 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-29 15:54 pip88nl at gmail dot com [this message] 2010-12-29 16:07 ` [Bug target/47120] " rguenth at gcc dot gnu.org
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=bug-47120-4@http.gcc.gnu.org/bugzilla/ \ --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).