public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/56015] expand expands p[9] = COMPLEX_EXPR <-IMAGPART_EXPR <p[9]>, REALPART_EXPR <p[9]>>; incorrectly.
Date: Thu, 17 Jan 2013 08:52:00 -0000	[thread overview]
Message-ID: <bug-56015-4-8VvONCPdS0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56015-4@http.gcc.gnu.org/bugzilla/>


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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-01-17
          Component|fortran                     |middle-end
            Summary|Option -ffast-math reveals  |expand expands p[9] =
                   |i*(a+bi) -> -b-bi, a        |COMPLEX_EXPR
                   |complex multiplication bug  |<-IMAGPART_EXPR <p[9]>,
                   |                            |REALPART_EXPR <p[9]>>;
                   |                            |incorrectly.
     Ever Confirmed|0                           |1
      Known to fail|4.4.6, 4.6.3, 4.7.2         |4.3.5, 4.4.5, 4.8.0

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-01-17 08:52:25 UTC ---
Actually it is not the multiplication that goes wrong.  In fact the code looks
correct before expand.  Turning off TER (-fno-tree-ter) will work around this
expand issue though.


  reply	other threads:[~2013-01-17  8:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17  8:40 [Bug fortran/56015] New: Option -ffast-math reveals i*(a+bi) -> -b-bi, a complex multiplication bug t_nissie at yahoo dot co.jp
2013-01-17  8:52 ` pinskia at gcc dot gnu.org [this message]
2013-01-17 10:30 ` [Bug middle-end/56015] [4.6/4.7/4.8 Regression] expand expands p[9] = COMPLEX_EXPR <-IMAGPART_EXPR <p[9]>, REALPART_EXPR <p[9]>>; incorrectly jakub at gcc dot gnu.org
2013-01-17 10:31 ` jakub at gcc dot gnu.org
2013-01-17 10:48 ` rguenth at gcc dot gnu.org
2013-01-17 11:58 ` t_nissie at yahoo dot co.jp
2013-01-18 17:15 ` jakub at gcc dot gnu.org
2013-01-18 17:26 ` [Bug middle-end/56015] [4.6/4.7 " jakub at gcc dot gnu.org
2013-02-01 14:11 ` jakub at gcc dot gnu.org
2013-02-01 14:32 ` [Bug middle-end/56015] [4.6 " jakub at gcc dot gnu.org
2013-04-03 18:20 ` jakub at gcc dot gnu.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=bug-56015-4-8VvONCPdS0@http.gcc.gnu.org/bugzilla/ \
    --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).