public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: blofeldus@yahoo.com To: gcc-gnats@gcc.gnu.org Subject: c/6543: Internal compiler error in extract_insn, at recog.c:2132 Date: Thu, 02 May 2002 19:16:00 -0000 [thread overview] Message-ID: <20020503021425.24475.qmail@sources.redhat.com> (raw) >Number: 6543 >Category: c >Synopsis: Internal compiler error in extract_insn, at recog.c:2132 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Thu May 02 19:16:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: blofeldus@yahoo.com >Release: gcc version 3.1 20020502 (prerelease) >Organization: >Environment: glibc-2.2.5 cvs GNU ld version 2.12.90.0.3 20020323 gcc version 3.1 20020502 (prerelease) >Description: gcc -DHAVE_CONFIG_H -I. -I. -I. -O2 -fsigned-char -c ltdl.c -Wall -fPIC -DPIC -save-temps -o .libs/ltdl.lo ltdl.c: In function `try_dlopen': ltdl.c:2883: unrecognizable insn: (insn 2417 1249 2418 (parallel[ (set (reg/v:SI 24 r24 [128]) (plus:SI (eq:SI (reg:SI 0 r0 [421]) (const_int 0 [0x0])) (reg/v:SI 24 r24 [128]))) (clobber (reg:SI 9 r9)) ] ) -1 (nil) (nil)) ltdl.c:2883: Internal compiler error in extract_insn, at recog.c:2132 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. >How-To-Repeat: rpm --rebuild libtool-1.4.2-8.rpm from redhat rawhide >Fix: similar to c/6497? >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-03 2:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-02 19:16 blofeldus [this message] 2002-05-03 5:20 jakub 2002-05-03 6:53 sirl 2002-05-03 10:38 dje 2002-05-04 16:14 dje
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=20020503021425.24475.qmail@sources.redhat.com \ --to=blofeldus@yahoo.com \ --cc=gcc-gnats@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: linkBe 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).