public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: p.van-hoof@qub.ac.uk To: gcc-gnats@gcc.gnu.org Cc: p.van-hoof@qub.ac.uk Subject: optimization/10157: internal compiler error: in extract_insn, at recog.c:2188 Date: Thu, 20 Mar 2003 00:36:00 -0000 [thread overview] Message-ID: <200303200030.h2K0UxNp007656@scooby.star.fleet> (raw) >Number: 10157 >Category: optimization >Synopsis: internal compiler error: in extract_insn, at recog.c:2188 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Thu Mar 20 00:36:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Peter van Hoof >Release: 3.4 20030315 (experimental) >Organization: Queen's University of Belfast >Environment: System: SunOS scooby 5.9 Generic_112233-04 sun4u sparc SUNW,Sun-Blade-100 Architecture: sun4 host: sparc-sun-solaris2.9 build: sparc-sun-solaris2.9 target: sparc-sun-solaris2.9 configured with: /scratch/temp/cvs/gcc/configure --prefix=/opt/local/gcc340 --enable-languages=c,c++,f77 >Description: Compiler generates ICE when optimizing the attached code. >How-To-Repeat: scooby> gcc -v -c -O3 -ffast-math h2.c Reading specs from /opt/local/gcc340/lib/gcc-lib/sparc-sun-solaris2.9/3.4/specs Configured with: /scratch/temp/cvs/gcc/configure --prefix=/opt/local/gcc340 --enable-languages=c,c++,f77 Thread model: posix gcc version 3.4 20030315 (experimental) /opt/local/gcc340/lib/gcc-lib/sparc-sun-solaris2.9/3.4/cc1 -quiet -v -Dsparc -D__sparc__ -D__sparc -D__GCC_NEW_VARARGS__ -Acpu=sparc -Amachine=sparc h2.c -quiet -dumpbase h2.c -auxbase h2 -O3 -version -ffast-math -o /var/tmp//ccUWwD2c.s ignoring nonexistent directory "/opt/local/gcc340/sparc-sun-solaris2.9/include" #include "..." search starts here: #include <...> search starts here: /usr/local/include /opt/local/gcc340/include /opt/local/gcc340/lib/gcc-lib/sparc-sun-solaris2.9/3.4/include /usr/include End of search list. GNU C version 3.4 20030315 (experimental) (sparc-sun-solaris2.9) compiled by GNU C version 3.4 20030315 (experimental). GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 h2.c: In function `g': h2.c:15: error: unrecognizable insn: (insn:HI 134 133 8 0 0 (set (reg:CCFPE 127) (compare:CCFPE (reg/v:DF 109 [ p ]) (reg:DF 111))) -1 (insn_list 133 (nil)) (expr_list:REG_DEAD (reg/v:DF 109 [ p ]) (expr_list:REG_DEAD (reg:DF 111) (expr_list:REG_EQUAL (compare:CCFPE (reg/v:DF 109 [ p ]) (const_double:DF 1.0e+0 [0x0.8p+1])) (nil))))) h2.c:15: internal compiler error: in extract_insn, at recog.c:2188 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. scooby> cat h2.c void h() { int i,n; double p,r; for( i=0; i < n; i++ ) if( p > 1. ) for( i=0; i < n; i++ ) r += 2.; return; } void g() { while( 1 ) h(); return; } >Fix: Workaround: use lower level of optimization or omit -ffast-math >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-20 0:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-20 0:36 p.van-hoof [this message] 2003-03-20 0:46 Peter van Hoof 2003-03-20 2:56 Peter van Hoof
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=200303200030.h2K0UxNp007656@scooby.star.fleet \ --to=p.van-hoof@qub.ac.uk \ --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).