Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 25450 - emerge gcc crashes when -fsigned-char is in CFLAGS
Summary: emerge gcc crashes when -fsigned-char is in CFLAGS
Status: VERIFIED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: PPC Linux
: High normal (vote)
Assignee: Lars Weiler (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-28 12:19 UTC by tom
Modified: 2006-02-04 06:03 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
full output of emerge gcc 2> gcc_00.err (gcc_00.err,9.62 KB, text/plain)
2003-07-28 12:22 UTC, tom
Details
full output of emerge gcc 2> gcc_00.err (gcc_00.err,9.62 KB, text/plain)
2003-07-28 12:23 UTC, tom
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tom 2003-07-28 12:19:59 UTC
if -fsigned-char is in CFLAGS then when I try to emerge gcc it crashes everytime
at the same spot...
when encountering xregcomp and xregerror...


Reproducible: Always
Steps to Reproduce:
1.rm -rf /var/tmp/portage/*
2.emerge gcc 2> gcc.err
3.crash

Actual Results:  
/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/libiberty/regex.c:1422: warning:
t$/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/libiberty/regex.c:1424: warning:
t$/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/libiberty/regex.c:1425: warning:
t$/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/libiberty/regex.c:1427: warning:
t$/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/libiberty/regex.c: In function
`xr$/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/libiberty/regex.c:8099:
warning: s$/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/libiberty/regex.c: In
function
`xr$/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/libiberty/regex.c:8234:
warning: u$In file included from
/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/libiberty/pe$/usr/include/unistd.h:983:
Internal compiler error in layout_type, at stor-layo$Please submit a full bug
report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.
make[1]: *** [pexecute.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [all-libiberty] Error 2
                                                                                
!!! ERROR: sys-devel/gcc-3.2.3-r2 failed.
!!! Function src_compile, Line 361, Exitcode 2
!!! (no error message)
                                                                                


Expected Results:  
should compile

  GNU nano 1.2.1                File: emerge_info.txt
                                                                                
Portage 2.0.48-r7 (default-ppc-1.4, gcc-3.2.2, glibc-2.3.1-r2)
=================================================================
System uname: 2.4.21-ben2 ppc
GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo
http://gentoo.oregonst$CONFIG_PROTECT="/etc /var/qmail/control
/usr/kde/2/share/config /usr/kde/3/shar$CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="oss xv jpeg nls gif kde png truetype ppc foomaticdb gnome-libs gtkhtml
gdb$COMPILER="gcc3"
CHOST="powerpc-unknown-linux-gnu"
CFLAGS="-mcpu=750 -O2 -pipe -fsigned-char -mpowerpc-gfxopt"
CXXFLAGS="-mcpu=750 -O2 -pipe -fsigned-char -mpowerpc-gfxopt"
ACCEPT_KEYWORDS="ppc ~ppc"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="ccache"
Comment 1 tom 2003-07-28 12:22:05 UTC
Created attachment 15146 [details]
full output of emerge gcc 2> gcc_00.err

this is the full output of 
emerge gcc 2> gcc_00.err
Comment 2 tom 2003-07-28 12:23:03 UTC
Created attachment 15147 [details]
full output of emerge gcc 2> gcc_00.err

this is the full output of 
emerge gcc 2> gcc_00.err
Comment 3 tom 2003-07-28 12:25:05 UTC
if i do not include -fsigned-char in CFLAGS everything goes fine.... no crash
Comment 4 Pieter Van den Abeele (RETIRED) gentoo-dev 2003-07-31 06:04:43 UTC
as indicated by the gcc manpage, usage of -fsigned-char is not recommended. Also, in our portage latest /etc/make.conf -fsigned-char should no longer be listed as recommended CFLAGS for any cpu.

for G3 and gcc3 the ideal useflags are:

-mcpu=750 -O2 -pipe

-mpowerpc-gfxopts should be enabled by the -mcpu setting

-O3 should also be relatively stable on G3 machines, so feel free to s/O2/O3 :-)
 I know we have an application that given a computer, predicts the ideal CFLAGS - but I cannot remember the name. I'll ask Pylon to include a bit about CFLAGS in the ppc document or faq.
Comment 5 Lars Weiler (RETIRED) gentoo-dev 2003-07-31 07:09:39 UTC
I'll look what I can find out about this CFLAGS-generating-tool and furthermore update the Docs accordingly.  For the moment I still suggest -O2 instead of -O3.  There are some applications that still have problems with it.
Comment 6 Pieter Van den Abeele (RETIRED) gentoo-dev 2003-10-11 04:59:11 UTC
pylon, any news on this?
Comment 7 Alexander Gabert (RETIRED) gentoo-dev 2003-11-23 10:41:35 UTC
added azarah
Comment 8 Lars Weiler (RETIRED) gentoo-dev 2004-01-21 18:16:49 UTC
Is this still valid with gcc-3.2.3-r3?
Comment 9 Lars Weiler (RETIRED) gentoo-dev 2004-02-15 15:03:23 UTC
No answer.  Closing.