public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/44948] New: -mavx changes ABI Date: Thu, 15 Jul 2010 12:14:00 -0000 [thread overview] Message-ID: <bug-44948-87@http.gcc.gnu.org/bugzilla/> (raw) With two sources: struct A { long b[8] __attribute__((aligned (32))); }; void foo (long double, struct A); int main (void) { struct A a = { { 0, 1, 2, 3, 4, 5, 6, 7 } }; foo (8.0L, a); return 0; } and: struct A { long b[8] __attribute__((aligned (32))); }; void foo (long double x, struct A y) { int i; if (x != 8.0L) __builtin_abort (); for (i = 0; i < 8; i++) if (y.b[i] != i) __builtin_abort (); } when one of these is compiled with -mavx while the other one is not, the testcase ICEs, while when -mavx is used in both or none of the compilations, it works. This is because ix86_function_arg_boundary returns 16 for -mno-avx while 32 for -mavx in this case. Shouldn't it return > 16 only if the mode is for 256-bit vector modes or aggregate which contains some 256-bit vector somewhere in it? -- Summary: -mavx changes ABI Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jakub at gcc dot gnu dot org GCC target triplet: x86_64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44948
next reply other threads:[~2010-07-15 12:14 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-15 12:14 jakub at gcc dot gnu dot org [this message] 2010-07-15 13:12 ` [Bug target/44948] " hjl dot tools at gmail dot com 2010-07-15 13:15 ` jakub at gcc dot gnu dot org 2010-07-15 13:26 ` hjl dot tools at gmail dot com 2010-07-15 13:34 ` hjl dot tools at gmail dot com 2010-07-15 13:42 ` hjl dot tools at gmail dot com 2010-07-15 13:56 ` hjl dot tools at gmail dot com 2010-07-15 14:10 ` hjl dot tools at gmail dot com 2010-07-15 16:02 ` rguenth at gcc dot gnu dot org 2010-07-15 16:06 ` hjl dot tools at gmail dot com 2010-07-15 16:21 ` hjl dot tools at gmail dot com 2010-07-15 16:28 ` jakub at gcc dot gnu dot org 2010-07-15 16:41 ` hjl dot tools at gmail dot com 2010-07-15 16:47 ` hjl dot tools at gmail dot com 2010-07-15 19:07 ` hjl dot tools at gmail dot com 2010-07-15 22:29 ` hjl dot tools at gmail dot com 2010-07-15 22:47 ` hjl dot tools at gmail dot com 2010-07-15 23:26 ` hjl dot tools at gmail dot com 2010-07-16 13:32 ` [Bug target/44948] -msse/-mavx change ABI hjl dot tools at gmail dot com 2010-07-16 13:42 ` hjl dot tools at gmail dot com 2010-07-16 13:55 ` hjl dot tools at gmail dot com 2010-08-21 17:07 ` hjl dot tools 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=bug-44948-87@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).