public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/38151] structures with _Complex arguments are not passed correctly
Date: Sun, 16 Nov 2008 20:59:00 -0000 [thread overview]
Message-ID: <20081116205810.24738.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38151-11113@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from ubizjak at gmail dot com 2008-11-16 20:58 -------
Real bug with argument passing. Confirmed on x86_64-linux-gnu with the
testcase:
--cut here--
struct S2848
{
unsigned int a;
_Complex int b;
};
struct S2848 s2848;
void __attribute__((noinline))
check2848 (struct S2848 arg0)
{
if (arg0.b != s2848.b)
abort ();
}
int main()
{
s2848.a = 4027477739U;
s2848.b = (723419448 + -218144346 * __extension__ 1i);
check2848 (s2848);
return 0;
}
--cut here--
> gcc -O2 t.c
> ./a.out
Aborted
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl at gcc dot gnu dot org,
| |hubicka at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
GCC host triplet|i686-apple-darwin9 |
GCC target triplet|i686-apple-darwin9 |x86_64
Keywords| |ABI, wrong-code
Known to fail| |4.3.0 4.4.0
Last reconfirmed|0000-00-00 00:00:00 |2008-11-16 20:58:10
date| |
Summary|tmpdir-gcc.dg-struct-layout-|structures with _Complex
|1/t028 failure at -m64 on |arguments are not passed
|i686-apple-darwin9 |correctly
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38151
next prev parent reply other threads:[~2008-11-16 20:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 2:57 [Bug testsuite/38151] New: tmpdir-gcc.dg-struct-layout-1/t028 failure at -m64 on i686-apple-darwin9 howarth at nitro dot med dot uc dot edu
2008-11-16 2:58 ` [Bug testsuite/38151] " howarth at nitro dot med dot uc dot edu
2008-11-16 3:00 ` howarth at nitro dot med dot uc dot edu
2008-11-16 3:00 ` howarth at nitro dot med dot uc dot edu
2008-11-16 3:01 ` howarth at nitro dot med dot uc dot edu
2008-11-16 3:02 ` howarth at nitro dot med dot uc dot edu
2008-11-16 3:02 ` howarth at nitro dot med dot uc dot edu
2008-11-16 3:05 ` howarth at nitro dot med dot uc dot edu
2008-11-16 15:57 ` howarth at nitro dot med dot uc dot edu
2008-11-16 20:29 ` ubizjak at gmail dot com
2008-11-16 20:59 ` ubizjak at gmail dot com [this message]
2008-11-16 21:10 ` [Bug testsuite/38151] structures with _Complex arguments are not passed correctly ubizjak at gmail dot com
2008-11-19 19:34 ` [Bug target/38151] " ubizjak at gmail dot com
2008-11-19 21:18 ` ubizjak at gmail dot com
2008-11-20 1:11 ` howarth at nitro dot med dot uc dot edu
2008-11-20 12:57 ` howarth at nitro dot med dot uc dot edu
2008-11-20 19:51 ` ubizjak at gmail dot com
2008-11-20 21:14 ` uros at gcc dot gnu dot org
2008-11-20 21:15 ` ubizjak at gmail dot com
2008-11-20 21:38 ` ubizjak at gmail dot com
2008-11-21 0:06 ` howarth at nitro dot med dot uc dot edu
2008-11-22 12:34 ` ubizjak at gmail dot com
2008-11-22 17:08 ` ubizjak at gmail dot com
2008-11-22 17:41 ` howarth at nitro dot med dot uc dot edu
2008-11-22 18:21 ` rguenth at gcc dot gnu dot org
2008-11-22 19:32 ` ubizjak at gmail dot com
2008-11-22 20:42 ` rguenth at gcc dot gnu dot org
2008-11-22 20:42 ` rguenth at gcc dot gnu dot org
2008-11-25 10:36 ` [Bug middle-end/38151] " rguenth at gcc dot gnu dot org
2008-11-25 10:37 ` rguenth 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=20081116205810.24738.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: link
Be 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).