public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: aaronl@vitelus.com To: gcc-gnats@gcc.gnu.org Subject: optimization/4711: ICE in eliminate_regs, at reload1.c:2576 Date: Sat, 27 Oct 2001 12:26:00 -0000 [thread overview] Message-ID: <20011027192403.20653.qmail@sourceware.cygnus.com> (raw) >Number: 4711 >Category: optimization >Synopsis: ICE in eliminate_regs, at reload1.c:2576 >Confidential: no >Severity: critical >Priority: high >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Sat Oct 27 12:26:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: aaronl@vitelus.com >Release: gcc version 3.1 20011027 (experimental) >Organization: >Environment: Linux endquote 2.4.9-ac10 #1 Fri Sep 14 00:02:50 PDT 2001 i686 unknown >Description: Hello, I notice that this bug has been reported many times, for example in #4555, #4387, #4384, #3835, #3214, and #2426. However, the bug reporting guidelines say to report new bugs as followups to old ones. I have developed a minimal test case that will reproduce "Internal compiler error in eliminate_regs, at reload1.c:2576": void testfunc(char* foo, int bar) { fd_set readfds; fd_set rfds = readfds; switch (bar) { case 0: break; default: if ((__extension__ ({register char __result; __asm__ __volatile__ ("btl %1,%2 ; setcb %b0" : "=q" (__result) : "r" (0), "m" (*(&rfds)->fds_bits) : "cc"); __result; }))) break; } } Compile this with -O[23s] and it will ICE. -O[01] will not cause it to. >How-To-Repeat: Compile the self-contained testcase contained in the description. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-10-27 12:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-27 12:26 aaronl [this message] 2001-11-18 11:40 rodrigc 2001-11-18 12:11 rodrigc
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=20011027192403.20653.qmail@sourceware.cygnus.com \ --to=aaronl@vitelus.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).