Summary: | emerge gcc crashes when -fsigned-char is in CFLAGS | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tom <whozoe> |
Component: | Current packages | Assignee: | Lars Weiler (RETIRED) <pylon> |
Status: | VERIFIED NEEDINFO | ||
Severity: | normal | CC: | azarah, gcc-porting |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
full output of emerge gcc 2> gcc_00.err
full output of emerge gcc 2> gcc_00.err |
Description
tom
2003-07-28 12:19:59 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
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
if i do not include -fsigned-char in CFLAGS everything goes fine.... no crash 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. 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. pylon, any news on this? added azarah Is this still valid with gcc-3.2.3-r3? No answer. Closing. |