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/35227] [4.1/4.2/4.3 regression] gcc ICEs for functions with unused complex argument Date: Sun, 17 Feb 2008 14:13:00 -0000 [thread overview] Message-ID: <20080217141222.9953.qmail@sourceware.org> (raw) In-Reply-To: <bug-35227-10160@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from rguenth at gcc dot gnu dot org 2008-02-17 14:12 ------- Unrelated to the implicit cabs() decl: double cabs(double _Complex); double mandel(double _Complex C) { int py; C = (__extension__ 1.0iF) * (double)py; return cabs(C); } I have a patch. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code Priority|P3 |P1 Summary|[4.1/4.2/4.3 regression] gcc|[4.1/4.2/4.3 regression] gcc |ICEs/segfaults when using |ICEs for functions with |implicit cabs() with -O1 |unused complex argument http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35227
next prev parent reply other threads:[~2008-02-17 14:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-17 8:23 [Bug c/35227] New: [4.1/4.2 regression] gcc ICEs/segfaults when using implicit cabs() with -O1 vapier at gentoo dot org 2008-02-17 8:24 ` [Bug c/35227] " vapier at gentoo dot org 2008-02-17 8:33 ` [Bug middle-end/35227] [4.1/4.2/4.3 " pinskia at gcc dot gnu dot org 2008-02-17 12:17 ` rguenth at gcc dot gnu dot org 2008-02-17 14:03 ` rguenth at gcc dot gnu dot org 2008-02-17 14:13 ` rguenth at gcc dot gnu dot org [this message] 2008-02-17 15:08 ` [Bug middle-end/35227] [4.1/4.2/4.3 regression] gcc ICEs for functions with unused complex argument rguenth at gcc dot gnu dot org 2008-02-17 15:11 ` [Bug middle-end/35227] [4.1/4.2 " rguenth at gcc dot gnu dot org 2008-05-19 20:34 ` jsm28 at gcc dot gnu dot org 2008-07-04 23:01 ` [Bug middle-end/35227] [4.2 " jsm28 at gcc dot gnu dot org 2009-03-31 15:14 ` jsm28 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=20080217141222.9953.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).