Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 45399 - gcc-3.3.x issue tracker for ppc32 and ppc64
Summary: gcc-3.3.x issue tracker for ppc32 and ppc64
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: PPC Linux
: High major (vote)
Assignee: PPC Porters
Depends on: 45404
Blocks: 39041 50783
  Show dependency tree
Reported: 2004-03-22 08:09 UTC by Luca Barbato
Modified: 2004-10-19 05:07 UTC (History)
0 users

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


Note You need to log in before you can comment on or make changes to this bug.
Description Luca Barbato gentoo-dev 2004-03-22 08:09:11 UTC
This bug will depend on every gcc-3.3.3 related bug on the ppc platform

Reproducible: Always
Steps to Reproduce:
Comment 1 Luca Barbato gentoo-dev 2004-03-22 08:13:20 UTC
making it blocking #39041 since tethereal needs gcc-3.3.3 to be functional
Comment 2 Luca Barbato gentoo-dev 2004-03-22 14:42:10 UTC
gcc-3.3.3 has problems with the altivec code, the fixes for that issue are in the gcc-3.3.3-hammer branch
Comment 3 Luca Barbato gentoo-dev 2004-03-23 05:33:11 UTC
I made another snapshot from the hammer branch, same issues with openssl.
Comment 4 Luca Barbato gentoo-dev 2004-03-24 17:07:06 UTC
found the problem
seems that -fstrict-aliasing may cause problems if the program (like openssl) uses  type punning in the wrong way.

appending -fno-strict-aliasing seems to solve the problem.
Comment 5 Pieter Van den Abeele (RETIRED) gentoo-dev 2004-03-24 17:56:53 UTC
Just to be sure; is fstrict-aliasing what broke I/O operations in combination with the type thing? So, does the 20040215 snapshot work ok too if you specify -fnostrict-aliasing as option?
Comment 6 Luca Barbato gentoo-dev 2004-03-24 18:15:50 UTC
We cannot be sure if we don't try it. 
A good way check is using -Werror -Wstrict-aliasing and probably you get gcc pointing at some code segments or just grep the warning for the type-pun.

I guess that this is the problem and I'm not sure if it will be solved by gcc or requires us to patch a _LOT_ of programs or to add -fno-strict-aliasing as default  flag.

Comment 7 Luca Barbato gentoo-dev 2004-03-24 18:57:44 UTC
Seems that our problem is a side effect of a feature...

Comment 8 Luca Barbato gentoo-dev 2004-05-06 08:19:18 UTC
the latest (0426 and 0505) snapshots have any sort of wierd problems, the 20040408-r1 should be the latest one stable enough to experimental use.
I'm about to apply the stack fix to the gcc-3.4.0-r1 and start some tests.
Comment 9 Pieter Van den Abeele (RETIRED) gentoo-dev 2004-06-02 13:28:25 UTC
I'll bump gcc-20040408-r1 to stable together with glibc-20040420-r1, unless somebody shouts.

don't forget -fno-strict-aliasing :-)
Comment 10 Tom Gall (RETIRED) gentoo-dev 2004-10-18 21:24:03 UTC
removing ppc64 from this bug as we're no longer 3.3 based at all. 
Comment 11 Luca Barbato gentoo-dev 2004-10-19 05:07:33 UTC
we can close it