public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "raj dot khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/26765]  New: ICE in in extract_insn, at recog.c:2036
Date: Mon, 20 Mar 2006 08:31:00 -0000	[thread overview]
Message-ID: <bug-26765-10179@http.gcc.gnu.org/bugzilla/> (raw)

GCC trunk gets this ICE when building glibc. The ICE happens on gcc 4.1 too.
This happens when -O2 is turned on. Here is a reduced testcase to reproduce the
problem.

example.c
==================
__thread int *a = 0;

void foo (void)
{
  extern int *b;
  b = (int *) ((*a));
}


how to reproduce 

mips-elf-gcc -O2 -c example.c


example.c: In function 'foo':
example.c:7: error: unrecognizable insn:
(insn 14 13 15 3 (set (reg/f:SI 193)
        (mem/c/i:SI (lo_sum:SI (reg:SI 195)
                (const:SI (unspec:SI [
                            (symbol_ref:SI ("a") [flags 0x22] <var_decl
0xb7c4a840 a>)
                        ] 114))) [2 a+0 S4 A32])) -1 (nil)
    (nil))
example.c:7: internal compiler error: in extract_insn, at recog.c:2036
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.


-- 
           Summary: ICE in in extract_insn, at recog.c:2036
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: raj dot khem at gmail dot com
 GCC build triplet: i386-redhat-linux
  GCC host triplet: i386-redhat-linux
GCC target triplet: mips-unknown-elf


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


             reply	other threads:[~2006-03-20  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20  8:31 raj dot khem at gmail dot com [this message]
2006-03-20 17:30 ` [Bug target/26765] " pinskia at gcc dot gnu dot org
2006-03-20 17:56 ` [Bug target/26765] ICE in in extract_insn with __thread and optimization pinskia at gcc dot gnu dot org
2006-03-21  1:20 ` raj dot khem at gmail dot com
2006-04-10  7:38 ` raj dot khem at gmail dot com
2006-05-04 20:07 ` kazu at gcc dot gnu dot org
2006-05-04 20:13 ` kazu at gcc dot gnu dot org
2006-05-04 20:15 ` kazu at gcc dot gnu dot org
2006-05-04 20:18 ` kazu at gcc dot gnu dot org
2006-05-04 20:21 ` kazu 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=bug-26765-10179@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).