public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56635] [4.8/4.9 regression] internal compiler error: in find_lattice_value, at tree-complex.c:15
Date: Mon, 18 Mar 2013 08:27:00 -0000	[thread overview]
Message-ID: <bug-56635-4-WNyKPUMwiP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56635-4@http.gcc.gnu.org/bugzilla/>


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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-03-18
            Summary|[4.8 regression] internal   |[4.8/4.9 regression]
                   |compiler error: in          |internal compiler error: in
                   |find_lattice_value, at      |find_lattice_value, at
                   |tree-complex.c:15           |tree-complex.c:15
     Ever Confirmed|0                           |1

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-03-18 08:26:32 UTC ---
Reduced testcase (-O3):
struct A { _Complex double a; };
struct B { A *b; void foo (void *); };

A
operator / (A x, A y)
{
  A r;
  r.a = x.a / y.a;
  return r;
}

void
B::foo (void *x)
{
  if (__real__ b[0].a)
    b[0] = (static_cast <B *>(x))->b[0] / b[0];
  else
    b[0] = (static_cast <B *>(x))->b[0];
}

The ICE is actually
pr56635.C: In member function ‘void B::foo(void*)’:
pr56635.C:13:1: error: invalid PHI argument
 B::foo (void *x)
 ^
MEM[(const struct A &)_9]
pr56635.C:13:1: error: incompatible types in PHI argument 1
complex double

const struct A

cstore_10 = PHI <_11(3), MEM[(const struct A &)_9](4)>

pr56635.C:13:1: internal compiler error: verify_gimple failed

and looks like cselim bug.
Started with http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=186501 but guess
it just has been latent before that.


  parent reply	other threads:[~2013-03-18  8:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16 15:11 [Bug c/56635] New: [4.8 " orion at cora dot nwra.com
2013-03-16 16:20 ` [Bug c/56635] " jakub at gcc dot gnu.org
2013-03-17  1:44 ` orion at cora dot nwra.com
2013-03-17  4:45 ` markus at trippelsdorf dot de
2013-03-17  5:53 ` [Bug tree-optimization/56635] " pinskia at gcc dot gnu.org
2013-03-18  8:27 ` jakub at gcc dot gnu.org [this message]
2013-03-18  8:47 ` [Bug tree-optimization/56635] [4.8/4.9 " jakub at gcc dot gnu.org
2013-03-18  9:03 ` jakub at gcc dot gnu.org
2013-03-18 13:02 ` jakub at gcc dot gnu.org
2013-03-20  8:43 ` jakub at gcc dot gnu.org
2013-03-20  8:43 ` 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-56635-4-WNyKPUMwiP@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).