[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

2011-12-21 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39852 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

2010-02-01 Thread mikpe at it dot uu dot se
--- Comment #8 from mikpe at it dot uu dot se 2010-02-01 11:13 --- There are known aliasing bugs in older glibc releases that result in broken code when compiled with gcc-4.4. The fix is to update glibc or to patch it. See . -- http:/

[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

2010-02-01 Thread thunderwolf66102 at yahoo dot com
--- Comment #7 from thunderwolf66102 at yahoo dot com 2010-02-01 08:49 --- Under Gentoo, GCC x86_64-pc-linux-gnu-4.4.2 appears to also build a broken glibc 2.9. I have tried many times over the past several days to build and install gentoo's 2.9_p20081201-r3 to replace a previous 2.9_p

[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

2009-04-23 Thread sega01 at go-beyond dot org
--- Comment #6 from sega01 at go-beyond dot org 2009-04-23 20:59 --- (In reply to comment #5) > GCC 4.4.0 compiled glibc 2.10 works just fine for me on x86_64, i586, i686, > powerpc and powerpc64. > > Anyway, if you say GCC 4.3.3 compiled glibc 2.8 works and 4.4.0 compiled > doesn't, th

[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

2009-04-22 Thread jakub at gcc dot gnu dot org
--- Comment #5 from jakub at gcc dot gnu dot org 2009-04-23 06:03 --- GCC 4.4.0 compiled glibc 2.10 works just fine for me on x86_64, i586, i686, powerpc and powerpc64. Anyway, if you say GCC 4.3.3 compiled glibc 2.8 works and 4.4.0 compiled doesn't, then please do a binary search betwe

[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

2009-04-22 Thread sega01 at go-beyond dot org
--- Comment #4 from sega01 at go-beyond dot org 2009-04-23 01:10 --- (In reply to comment #3) > It might be better if you use gdb instead of using ltrace because those two > programs don't give enough information on what is going on. This could be > still a bug in Lua or even in glibc i

[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

2009-04-22 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2009-04-23 00:57 --- It might be better if you use gdb instead of using ltrace because those two programs don't give enough information on what is going on. This could be still a bug in Lua or even in glibc itself but without a testcase

[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

2009-04-22 Thread sega01 at go-beyond dot org
--- Comment #2 from sega01 at go-beyond dot org 2009-04-23 00:55 --- (In reply to comment #1) > There is not enough information here. Do you have a source to a program which > fails with the new glibc compiled with 4.4? > Thank you for the quick response. The sources for the applicat

[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

2009-04-22 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2009-04-23 00:09 --- There is not enough information here. Do you have a source to a program which fails with the new glibc compiled with 4.4? -- pinskia at gcc dot gnu dot org changed: What|Removed