Bug 17421 - gcc SEGV while compiling plotutils-2.4.1
Summary: gcc SEGV while compiling plotutils-2.4.1
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gcc
Version: 7.0
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-09-12 12:44 UTC by Need Real Name
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-10-09 15:46:24 UTC
Embargoed:


Attachments (Terms of Use)
g_range.i obtained with -save-temps (261.58 KB, text/plain)
2000-09-12 13:18 UTC, Need Real Name
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2000:132 0 normal SHIPPED_LIVE Bug fixing update of GCC 2.96 2000-12-19 05:00:00 UTC

Description Need Real Name 2000-09-12 12:44:44 UTC
i'm using a fresh pinstripe install. While compiling the GNU
plotutils-2.4.1, gcc crashes with:
> cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include -I./../include -O2
-c g_range.c -fPIC -DPIC -o .libs/g_range.lo
gcc: Internal error: Segmentation fault (program cc1)

(in plotutil-2.4.1/libplot)

if i change the optimisation option to -O, it doesn't crash. It also
doesn't crash if i remove -fPIC -DPIC.

Comment 1 Jakub Jelinek 2000-09-12 13:00:28 UTC
Can you please run
cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include -I./../include -O2 -c g_range.c -fPIC -DPIC -o .libs/g_range.lo -save-temps
and send me g_range.i? It is well possible it got fixed in the meantime, but
I'd like to be sure.
Thanks.

Comment 2 Need Real Name 2000-09-12 13:18:15 UTC
Created attachment 3380 [details]
g_range.i obtained with -save-temps

Comment 3 Jakub Jelinek 2000-10-09 15:46:21 UTC
Fix mailed to gcc-patches for pier review. If it is accepted, it will
appear in the next gcc erratas.

Comment 4 Jakub Jelinek 2000-10-24 08:20:41 UTC
Should be fixed in gcc-2.96-60 in rawhide.


Note You need to log in before you can comment on or make changes to this bug.