public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fche at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/16573] New: compiler crash while building groff with -fmudflap
Date: Thu, 15 Jul 2004 18:59:00 -0000 [thread overview]
Message-ID: <20040715185932.16573.fche@redhat.com> (raw)
Building groff/src/libs/libgroff/font.cpp recently started to die when
compiled with -fmudflap with a mainline CVS compiler. I attach various
versions of test cases, and show the transcript here.
int text_file::next()
{
if (buf == 0) {
buf = 0;
}
for (;;) {
int c;
if
#if COMPILER_SEGV
(0)
#else /* DOMINANCE_ABORT */
(invalid_input_char(c))
#endif
error("invalid input character code `%1'", int(c));
}
return 0;
}
with COMPILER_SEGV defined, one gets
/notnfs/fche/BUILD-gcc-mudflap/INST/libexec/gcc/i686-pc-linux-gnu/3.5.0/cc1plus
-fpreprocessed font2.ii -quiet -dumpbase font2.cpp -mtune=pentiumpro -auxbase
font2 -g -O2 -version -fmudflap -fno-builtin -fno-merge-constants -o font2.s
GNU C++ version 3.5.0 20040715 (experimental) (i686-pc-linux-gnu)
compiled by GNU C version 3.5.0 20040713 (experimental).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
font2.cpp: In member function `int text_file::next()':
font2.cpp:52: internal compiler error: Segmentation fault
without COMPILER_SEGV, one gets
/notnfs/fche/BUILD-gcc-mudflap/INST/libexec/gcc/i686-pc-linux-gnu/3.5.0/cc1plus
-fpreprocessed font2.ii -quiet -dumpbase font2.cpp -mtune=pentiumpro -auxbase
font2 -g -O2 -version -fmudflap -fno-builtin -fno-merge-constants -o font2.s
GNU C++ version 3.5.0 20040715 (experimental) (i686-pc-linux-gnu)
compiled by GNU C version 3.5.0 20040713 (experimental).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
font2.cpp: In member function `int text_file::next()':
font2.cpp:52: error: dominator of 10 should be 11, not 0
font2.cpp:52: internal compiler error: in verify_dominators, at dominance.c:828
Please submit a full bug report,
--
Summary: compiler crash while building groff with -fmudflap
Product: gcc
Version: 3.5.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P2
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: fche at redhat dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16573
next reply other threads:[~2004-07-15 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 18:59 fche at redhat dot com [this message]
2004-07-15 19:00 ` [Bug tree-optimization/16573] " fche at redhat dot com
2004-07-15 19:01 ` fche at redhat dot com
2004-07-15 19:19 ` fche at redhat dot com
2004-10-14 1:48 ` pinskia at gcc dot gnu dot org
2004-10-15 15:21 ` fche at redhat dot com
2004-10-15 17:13 ` pinskia at gcc dot gnu dot org
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=20040715185932.16573.fche@redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).