public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/44583] [4.6 Regression] c-c++-common/torture/complex-sign-add.c Date: Sat, 19 Jun 2010 10:58:00 -0000 [thread overview] Message-ID: <20100619105821.22698.qmail@sourceware.org> (raw) In-Reply-To: <bug-44583-682@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2010-06-19 10:58 ------- Bah - gigantic testcases. And maybe not mine (I tought r160903 is the cause). But the testcase do not even run into gimplify_modify_expr_complex_part. And I do not see any references to uninitialized data in the .optimized dump (just testing i?86 here). HJ, can you reduce one of the execute fails to a single type and arith? -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu dot | |org AssignedTo|rguenth at gcc dot gnu dot |unassigned at gcc dot gnu |org |dot org Status|ASSIGNED |NEW Target Milestone|--- |4.6.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44583
next prev parent reply other threads:[~2010-06-19 10:58 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-18 18:29 [Bug middle-end/44583] New: " hjl dot tools at gmail dot com 2010-06-19 10:39 ` [Bug middle-end/44583] " rguenth at gcc dot gnu dot org 2010-06-19 10:58 ` rguenth at gcc dot gnu dot org [this message] 2010-06-25 20:22 ` sje at cup dot hp dot com 2010-06-25 20:51 ` rguenth at gcc dot gnu dot org 2010-06-25 22:48 ` sje at cup dot hp dot com 2010-06-26 9:18 ` rguenther at suse dot de 2010-06-26 9:28 ` [Bug target/44583] " rguenth at gcc dot gnu dot org 2010-06-26 10:05 ` rguenth at gcc dot gnu dot org 2010-07-23 12:04 ` [Bug target/44583] [4.6 Regression] c-c++-common/torture/complex-sign-add.c fails for signed zeros rguenth at gcc dot gnu dot org 2010-07-29 21:32 ` sje at cup dot hp dot com 2010-08-04 18:33 ` sje at gcc dot gnu dot org 2010-08-04 19:25 ` sje at cup dot hp 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=20100619105821.22698.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).