public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/13718] Miscompilation of comparison of complex values Date: Sat, 17 Jan 2004 15:00:00 -0000 [thread overview] Message-ID: <20040117150044.20614.qmail@sources.redhat.com> (raw) In-Reply-To: <20040117140859.13718.pbrook@gcc.gnu.org> ------- Additional Comments From steven at gcc dot gnu dot org 2004-01-17 15:00 ------- Here is another nice one: --------------------------- extern void foo( _Complex float a, _Complex float b); int main() { _Complex float v; v = 0; foo (v, v); } --------------------------- ----> t.c.t23.sra: Scalar replacements for main: __real__ v -> SR.1 __imag__ v -> SR.2 ;; Function main (main) main () { float SR.2; float SR.1; complex float v; <bb 0>: SR.1_2 = 0.0; SR.2_3 = 0.0; v = COMPLEX_EXPR <SR.1_2, SR.2_3>; v = COMPLEX_EXPR <SR.1_2, SR.2_3>; foo (v, v); return; } ----> t.c.t33.optimized ;; Function main (main) main () { complex float v; <bb 0>: v = __complex__ (0.0, 0.0); v = __complex__ (0.0, 0.0); foo (v, v); return; } SRA for complex seems to just not work yet. RTH, you worked on this, so I have assigned this bug to you. -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |rth at redhat dot com |dot org | Status|NEW |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13718
next prev parent reply other threads:[~2004-01-17 15:00 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-17 14:09 [Bug optimization/13718] New: " pbrook at gcc dot gnu dot org 2004-01-17 14:33 ` [Bug optimization/13718] " steven at gcc dot gnu dot org 2004-01-17 15:00 ` steven at gcc dot gnu dot org [this message] 2004-01-17 20:30 ` [Bug optimization/13718] [tree-ssa] " pinskia at gcc dot gnu dot org 2004-01-17 20:51 ` cvs-commit at gcc dot gnu dot org 2004-01-17 20:55 ` rth at gcc dot gnu dot org 2004-01-17 21:00 ` 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=20040117150044.20614.qmail@sources.redhat.com \ --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).