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 middle-end/16670] struct { type:0; } passing bugs Date: Thu, 22 Jul 2004 10:26:00 -0000 [thread overview] Message-ID: <20040722102653.7554.qmail@sourceware.org> (raw) In-Reply-To: <20040722101856.16670.jakub@gcc.gnu.org> ------- Additional Comments From jakub at gcc dot gnu dot org 2004-07-22 10:26 ------- Argh, make the testcase for x86-64 instead: extern void abort (void); struct S { int:0; } a, b; void foo (int c, int d, int e, int f, int g, int h, struct S x, struct S *y) { if (y != &b) abort (); } int main (void) { foo (0, 1, 2, 3, 4, 5, a, &b); return 0; } (there was a collision between the dummy arg names and structure variables). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16670
next prev parent reply other threads:[~2004-07-22 10:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-22 10:19 [Bug middle-end/16670] New: " jakub at gcc dot gnu dot org 2004-07-22 10:26 ` jakub at gcc dot gnu dot org [this message] 2004-07-22 11:43 ` [Bug middle-end/16670] " giovannibajo at libero dot it 2004-09-27 16:26 ` reichelt at gcc dot gnu dot org 2005-04-16 22:37 ` pinskia at gcc dot gnu dot 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=20040722102653.7554.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).