public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, maddinp@yahoo.de,
nobody@gcc.gnu.org
Subject: Re: optimization/9357: [3.2/3.3/3.4 regression] SegFault with -fssa -funroll-loops -fprofile-arcs
Date: Fri, 17 Jan 2003 20:42:00 -0000 [thread overview]
Message-ID: <20030117204239.26689.qmail@sources.redhat.com> (raw)
Old Synopsis: gcc-3.2.1 optimization-crash
New Synopsis: [3.2/3.3/3.4 regression] SegFault with -fssa -funroll-loops -fprofile-arcs
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Fri Jan 17 12:42:37 2003
State-Changed-Why:
Confirmed. Here's a smaller testcase:
---------------------
void foo() {
typedef void (*fun_ptr)();
fun_ptr *array;
int i;
bar(array);
for (i=0; i<=0x100; i++)
array[i] = &foo;
}
----------------------------
This crashes every compiler since 3.2:
g/a> /home/bangerth/bin/gcc-3.4-pre/bin/gcc -O -c c64mem.c -fssa -funroll-loops -fprofile-arcs
c64mem.c: In function `foo':
c64mem.c:8: internal compiler error: Speicherzugriffsfehler
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
It used to work with 3.0.4, so it's a regression.
W.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9357
next reply other threads:[~2003-01-17 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 20:42 bangerth [this message]
2003-02-24 16:36 Janis Johnson
2003-02-24 16:56 Andreas Jaeger
2003-05-10 5:46 Dara Hazeghi
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=20030117204239.26689.qmail@sources.redhat.com \
--to=bangerth@dealii.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=maddinp@yahoo.de \
--cc=nobody@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).