public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49731] New: internal compiler error: verify_gimple failed
Date: Wed, 13 Jul 2011 12:36:00 -0000	[thread overview]
Message-ID: <bug-49731-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: internal compiler error: verify_gimple failed
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hjl.tools@gmail.com


[hjl@gnu-6 tests]$ cat foo.c
void g_hash_table_insert (void *, void*);
void int64_hash_test ()
{
     int i;
     long long values[4];
     for (i=0; i<4; i++)
       {
          values[i] = i + 42;
          g_hash_table_insert (&values[i], ((void *) (i + 42)));
       }
}
[hjl@gnu-6 tests]$ /usr/gcc-4.7.0-x32/bin/x86_64-unknown-linux-gnu-gcc   -O2 
-mx32  -S foo.c
foo.c: In function \u2018int64_hash_test\u2019:
foo.c:2:6: error: invalid types in nop conversion
void *
long long unsigned int
D.2730_20 = (void *) ivtmp.14_13;

foo.c:2:6: internal compiler error: verify_gimple failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
[hjl@gnu-6 tests]$


             reply	other threads:[~2011-07-13 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 12:36 hjl.tools at gmail dot com [this message]
2011-07-13 13:03 ` [Bug middle-end/49731] " hjl.tools at gmail dot com

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-49731-4@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).