Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!shlump.nac.dec.com!hiatus.dec.com!vmsdev.dec.com!ballou
From: ballou@vmsdev.dec.com (Kenneth R. Ballou)
Newsgroups: gnu.gcc.bug
Subject: Bug in GCC 1.35 compiler driver with -pipe option
Message-ID: <1444@hiatus.dec.com>
Date: 6 Sep 89 22:42:12 GMT
Sender: news@hiatus.dec.com
Organization: Digital Equipment Corporation
Lines: 15

I did a completely "vanilla" build of GCC 1.35 under ULTRIX 3.1 (that
is, I didn't change the Makefile, and I followed exactly the directions
to make stage1, stage2, and "post stage2", followed by "install").

When I try to use the -pipe option, GCC dumps core after the first
actions are done.  For example, the command line "gcc -v -pipe -c foo.c
bar.c" causes foo.c to be compiled and then gcc to dump core.  Also,
"gcc -pipe foo.c" causes foo.c to be compiled to foo.o, and then gcc
will dump core before invoking the linker.
The core dump shows gcc is in malloc() at the time of the dump.  Also,
using the GNU malloc causes a core dump in malloc with SIGILL.

However, everything works fine if I use the -B flag with a valid
pathname.  For example, if I'm in the directory in which I built gcc and
I do "gcc -pipe -c -Bstage2/ foo.c bar.c", both foo.c and bar.c are compiled.