public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* bootstrap/4681: segmentation fault during bootstrap  (x-gcc)
@ 2001-10-25 16:27 bp1
  0 siblings, 0 replies; 3+ messages in thread
From: bp1 @ 2001-10-25 16:27 UTC (permalink / raw)
  To: gcc-gnats

>Number:         4681
>Category:       bootstrap
>Synopsis:       segmentation fault during bootstrap  (x-gcc)
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Oct 25 16:26:22 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     bp1@cn.stir.ac.uk
>Release:        gcc 3.0.1
>Organization:
>Environment:
SETENV CFLAGS "-O2 -march=k6"
roulade /home/bp1> gcc -v
Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.0/specs
Configured with: ../configure --enable-threads=posix --enable-shared --enable-long-long --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java --enable-nls --with-slibdir=/lib i486-suse-linux
Thread model: posix
Athlon Processor, SuSe Linux 7.3
gcc version 3.0 20010510 (prerelease)
roulade /home/bp1>
>Description:
/home/bp1/gcc-3.0.1/gcc/xgcc -B/home/bp1/gcc-3.0.1/gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem
/usr/i686-pc-linux-gnu/include -O2   -DIN_GCC    -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -fPIC -g1
-DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I. -I.
-I./. -I./config -I./../include  -DL_muldi3 -c ./libgcc2.c -o
libgcc/./_muldi3.o
libgcc2.c: In function `__muldi3':
libgcc2.c:368: Internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
>How-To-Repeat:
With the k6 compiler option. Without this option there is an error later
in the output:
ln: `./slist': File exists
ln: `./hash_map': File exists
ln: `./hash_set': File exists
ln: `./stl_hashtable.h': File exists
ln: `./stl_hash_fun.h': File exists
sed -e '/^#/s/\([ABCDEFGHIJKLMNOPQRSTUVWXYZ_][ABCDEFGHIJKLMNOPQRSTUVWXYZ_]*\)/_GLIBCPP_\1/g' \
    -e 's,^#include "\(.*\)",#include <bits/\1>,g' \
    < /home/bp1/gcc-3.0.1/i686-pc-linux-gnu/libstdc++-v3/../gcc/gthr.h > i686-pc-linux-gnu/bits/gthr.h
/bin/sh: /home/bp1/gcc-3.0.1/i686-pc-linux-gnu/libstdc++-v3/../gcc/gthr.h: No such file or directory
make[3]: *** [i686-pc-linux-gnu/bits/gthr.h] Error 1
make[3]: Leaving directory `/home/bp1/gcc-3.0.1/i686-pc-linux-gnu/libstdc++-v3/include'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/bp1/gcc-3.0.1/i686-pc-linux-gnu/libstdc++-v3'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/home/bp1/gcc-3.0.1/i686-pc-linux-gnu/libstdc++-v3'
make: *** [all-target-libstdc++-v3] Error 2
roulade bp1/gcc-3.0.1>
The last error doesn't occur with the gcc-3.0.0. There the compilation goes through.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: bootstrap/4681: segmentation fault during bootstrap  (x-gcc)
@ 2002-04-04  3:38 rth
  0 siblings, 0 replies; 3+ messages in thread
From: rth @ 2002-04-04  3:38 UTC (permalink / raw)
  To: bp1, gcc-bugs, gcc-prs, nobody

Synopsis: segmentation fault during bootstrap  (x-gcc)

State-Changed-From-To: open->closed
State-Changed-By: rth
State-Changed-When: Thu Apr  4 03:38:13 2002
State-Changed-Why:
    Fixed in gcc 3.1.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4681


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: bootstrap/4681: segmentation fault during bootstrap  (x-gcc)
@ 2001-10-26  5:56 Bernd Porr
  0 siblings, 0 replies; 3+ messages in thread
From: Bernd Porr @ 2001-10-26  5:56 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR bootstrap/4681; it has been noted by GNATS.

From: Bernd Porr <bp1@cn.stir.ac.uk>
To: <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: bootstrap/4681: segmentation fault during bootstrap  (x-gcc)
Date: Fri, 26 Oct 2001 13:47:31 +0100 (BST)

 Dear Developers,
 
 the bug I repored was in gcc-3.0.0 but it's in gcc-3.0.2 as well:
 
 /usr/src/gcc-3.0.2/gcc/xgcc -B/usr/src/gcc-3.0.2/gcc/
 -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem
 /usr/i686-pc-linux-gnu/include -O2   -DIN_GCC    -W -Wall -Wwrite-strings
 -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -fPIC -g1
 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I. -I.
 -I./. -I./config -I./../include  -DL_muldi3 -c ./libgcc2.c -o
 libgcc/./_muldi3.o
 libgcc2.c: In function `__muldi3':
 libgcc2.c:368: Internal error: Segmentation fault
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
 make[2]: *** [libgcc/./_muldi3.o] Error 1
 make[2]: Leaving directory `/usr/src/gcc-3.0.2/gcc'
 make[1]: *** [libgcc.a] Error 2
 make[1]: Leaving directory `/usr/src/gcc-3.0.2/gcc'
 make: *** [all-gcc] Error 2
 roulade src/gcc-3.0.2#
 
 
 
 On 25 Oct 2001 gcc-gnats@gcc.gnu.org wrote:
 
 > Thank you very much for your problem report.
 > It has the internal identification `bootstrap/4681'.
 > The individual assigned to look at your
 > report is: unassigned.
 >
 > >Category:       bootstrap
 > >Responsible:    unassigned
 > >Synopsis:       segmentation fault during bootstrap  (x-gcc)
 > >Arrival-Date:   Thu Oct 25 16:26:22 PDT 2001
 >
 
 -----------------------------------------------------------------------
 http://www.cn.stir.ac.uk/~bp1
 


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-04-04 11:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-25 16:27 bootstrap/4681: segmentation fault during bootstrap (x-gcc) bp1
2001-10-26  5:56 Bernd Porr
2002-04-04  3:38 rth

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).