[Bug target/28701] [4.1/4.2 regression] ABI test failures building libstdc++ on a glibc-2.4 based system

2006-10-05 Thread debian-gcc at lists dot debian dot org
--- Comment #10 from debian-gcc at lists dot debian dot org 2006-10-05 15:13 --- are other patches than r111381 (trunk) required for a backport of long-double-128 to the 4.1 branch? Matthias -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28701

[Bug target/28701] [4.1/4.2 regression] ABI test failures building libstdc++ on a glibc-2.4 based system

2006-10-05 Thread pinskia at gcc dot gnu dot org
--- Comment #11 from pinskia at gcc dot gnu dot org 2006-10-05 15:40 --- This looks related to PR 26926. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/28701] [4.1/4.2 regression] ABI test failures building libstdc++ on a glibc-2.4 based system

2006-10-04 Thread debian-gcc at lists dot debian dot org
--- Comment #8 from debian-gcc at lists dot debian dot org 2006-10-04 17:36 --- configuring --with-long-double-128 works. could --with-long-double-128 become the default, if glibc-2.4 is detected? the situation reminds me at --enable-__cxa_atexit, which is not the default, but at

[Bug target/28701] [4.1/4.2 regression] ABI test failures building libstdc++ on a glibc-2.4 based system

2006-10-04 Thread jakub at gcc dot gnu dot org
--- Comment #9 from jakub at gcc dot gnu dot org 2006-10-04 22:03 --- --with-long-double-128 is the default on glibc 2.4+, but only in GCC 4.2. In vanilla GCC 4.1.x --with-long-double-128 isn't supported at all, those changes were added pretty late in the GCC 4.1 devel cycle and so do

[Bug target/28701] [4.1/4.2 regression] ABI test failures building libstdc++ on a glibc-2.4 based system

2006-09-04 Thread jakub at gcc dot gnu dot org
--- Comment #6 from jakub at gcc dot gnu dot org 2006-09-04 11:28 --- Can you readelf -Ws libstdc++.so.6 | egrep '[EMAIL PROTECTED]' | grep -v ' _Z' on both libraries (the 4.0 built one and 4.1.x --with-long-double-128 one)? The 4.0.x built one should contain the (DFmode) long double *l

[Bug target/28701] [4.1/4.2 regression] ABI test failures building libstdc++ on a glibc-2.4 based system

2006-09-04 Thread jakub at gcc dot gnu dot org
--- Comment #7 from jakub at gcc dot gnu dot org 2006-09-04 12:14 --- I have downloaded your tarball and it seems you are not building gcc to default to 128-bit long double on a glibc 2.4+ system. That's very bad idea, you either shouldn't have upgraded to glibc 2.4+, or should have

[Bug target/28701] [4.1/4.2 regression] ABI test failures building libstdc++ on a glibc-2.4 based system

2006-09-01 Thread mmitchel at gcc dot gnu dot org
--- Comment #5 from mmitchel at gcc dot gnu dot org 2006-09-01 21:51 --- This is a P1 because we need to understand if there is actually ABI breakage. If there isn't, or if we can't confirm that there is, we'll downgrade this. -- mmitchel at gcc dot gnu dot org changed:

[Bug target/28701] [4.1/4.2 regression] ABI test failures building libstdc++ on a glibc-2.4 based system

2006-08-23 Thread doko at ubuntu dot com
--- Comment #4 from doko at ubuntu dot com 2006-08-23 10:20 --- I see the problem with stlport 4.6.2: - stlport is built on a glibc-2.3 based system (using g++-4.0) - libstdc++/g++-4.1 is built on a glibc-2.4 based system - building the stlport regression tests using the installed

[Bug target/28701] [4.1/4.2 regression] ABI test failures building libstdc++ on a glibc-2.4 based system

2006-08-17 Thread jakub at gcc dot gnu dot org
--- Comment #3 from jakub at gcc dot gnu dot org 2006-08-17 12:38 --- The is just the libstdc++ ABI check not being able to understand tanl@@GLIBCXX_3.4 - [EMAIL PROTECTED] etc. changes (22 such symbols). Those are not ABI breakers, all that means is that newly linked programs won't

[Bug target/28701] [4.1/4.2 regression] ABI test failures building libstdc++ on a glibc-2.4 based system

2006-08-13 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity|normal |blocker Summary|[ 4.1 / 4.2 regression] ABI |[4.1/4.2