This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
c++/2380: Compiling the Crypto++ "bench.cpp" Causes g++ to Segfault
- To: gcc-gnats at gcc dot gnu dot org
- Subject: c++/2380: Compiling the Crypto++ "bench.cpp" Causes g++ to Segfault
- From: dew at cs dot stanford dot edu
- Date: 25 Mar 2001 09:56:40 -0000
- Reply-To: dew at cs dot stanford dot edu
>Number: 2380
>Category: c++
>Synopsis: Compiling the Crypto++ "bench.cpp" Causes g++ to Segfault
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Mar 25 02:06:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: David Weekly
>Release: 2.96
>Organization:
>Environment:
RedHat 7.0, Athlon Thunderbird 900, 256Mb RAM, Linux 2.4.0-test11
>Description:
When compiling Crypto++ (from http://www.eskimo.com/~weidai/cryptlib.html) the final portion, "g++ -O2 -w -pipe -c bench.cpp" took about five minutes and then failed with the following:
bench.cpp: In function `void BenchMarkAll (double)':
bench.cpp:671: Internal error: Segmentation fault.
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make: *** [bench.o] Error 1
>How-To-Repeat:
When ran a second time, g++ did not crash again, but it did take around ten minutes, which is a pretty good chunk of time to wait on a single file for an Athlon 900. I can't help but think there's some sort of profoundly odd condition that this code is causing.
>Fix:
?
>Release-Note:
>Audit-Trail:
>Unformatted: