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 14:33:00 -0000	[thread overview]
Message-ID: <20040117143321.2107.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 14:33 -------
Yup. 
 
Dump "t.c.t22.complex": 
;; Function foo (foo) 
foo (a, b) 
{ 
  complex float T.2; 
  complex float T.1; 
<bb 0>: 
  T.1 = *a_1; 
  T.2 = *b_4; 
  if (T.1 != T.2) goto <L0>; else goto <L1>; 
<L0>:; 
  abort (); 
<L1>:; 
  return; 
} 
 
Dump "t.c.t23.sra": 
Scalar replacements for foo: 
__real__ T.1 -> SR.4 
__imag__ T.1 -> SR.5 
__real__ T.2 -> SR.6 
__imag__ T.2 -> SR.7 
 
;; Function foo (foo) 
foo (a, b) 
{ 
  float SR.7; 
  float SR.6; 
  float SR.5; 
  float SR.4; 
  complex float T.2; 
  complex float T.1; 
<bb 0>: 
  SR.4_6 = REALPART_EXPR <*a_1>; 
  SR.5_3 = IMAGPART_EXPR <*a_1>; 
  SR.6_8 = REALPART_EXPR <*b_4>; 
  SR.7_9 = IMAGPART_EXPR <*b_4>; 
  if (T.1 != T.2) goto <L0>; else goto <L1>; 
<L0>:; 
  abort (); 
<L1>:; 
  return; 
} 
 
Dump "t.c.t25.dce3": 
;; Function foo (foo) 
foo (a, b) 
{ 
  float SR.7; 
  float SR.6; 
  float SR.5; 
  float SR.4; 
  complex float T.2; 
  complex float T.1; 
<bb 0>: 
  if (T.1 != T.2) goto <L0>; else goto <L1>; 
<L0>:; 
  abort (); 
<L1>:; 
  return; 
} 
 
Now where did the assignments go? 
 
BTW why isn't T.1 != T.2 folded to compare the real and imag parts? 
 
 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2004-01-17 14:33:20
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13718


  reply	other threads:[~2004-01-17 14:33 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 ` steven at gcc dot gnu dot org [this message]
2004-01-17 15:00 ` [Bug optimization/13718] " steven at gcc dot gnu dot org
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=20040117143321.2107.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: 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).