public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: cgd@broadcom.com To: gcc-gnats@gcc.gnu.org Subject: optimization/9301: mips-linux gcc 3.2.1 SEGV in try_forward_edges Date: Mon, 13 Jan 2003 23:46:00 -0000 [thread overview] Message-ID: <20030113234224.26002.qmail@sources.redhat.com> (raw) >Number: 9301 >Category: optimization >Synopsis: mips-linux gcc 3.2.1 SEGV in try_forward_edges >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Mon Jan 13 15:46:01 PST 2003 >Closed-Date: >Last-Modified: >Originator: Chris Demetriou <cgd@broadcom.com> >Release: 3.2.1 >Organization: >Environment: mips-linux, kernel 2.4.x. >Description: mips-linux (native) gcc 3.2.1 ICEs on the following test case. gdb indicates a SEGV in try_forward_edges. gcc 3.2.1 from ftp://ftp.gnu.org/pub/gnu/gcc/gcc-3.2.1/gcc-core-3.2.1.tar.gz built on a mips linux system like: tar xvfz gcc-core-3.2.1.tar.gz mkdir obj inst cd obj ../gcc-3.2.1/configure --prefix=`pwd`/../inst gmake && gmake install test fails with -O2 or above, but not with -O1 or less. >How-To-Repeat: see above. More info on where it does/doesn't fail: tried 3.2.1 as a native compiler for x86-linux as well, no ICE there at up to -O3. 3.2.1 also seems to have the problem on embedded mips targets (e.g. mipsisa64sb1 8-), but I did not try that configuration with an unmodified compiler. a quick test of head-of-trunk with mipsisa32-elf indicates problem is _not_ present there, but I wouldn't call my testing comprehensive. 8-) >Fix: workaround is to use -O1 or less. Fix unknown. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="trimmed3.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="trimmed3.c" dm9pZCBiYXIodm9pZCk7Cgp2b2lkIGZvbyAoaW50IGEsIGludCBiLCBpbnQgYywgaW50IGQsIGlu dCBlKQp7CgogICAgaWYgKGEpCiAgICAgIGJhcigpOwogICAgaWYgKGIgJiYgYykKICAgICAgOwog ICAgaWYgKGQgJiYgZSkKICAgICAgOwp9Cg==
next reply other threads:[~2003-01-13 23:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-13 23:46 cgd [this message] 2003-01-13 23:56 cgd 2003-01-21 19:56 cgd
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=20030113234224.26002.qmail@sources.redhat.com \ --to=cgd@broadcom.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).