Bug#554574: libstdc++6: apt segfaults on hppa
> test results for 4.4.2-1: >http://gcc.gnu.org/ml/gcc-testresults/2009-10/msg01919.html > for 4.4.2-2: >http://gcc.gnu.org/ml/gcc-testresults/2009-11/msg00351.html > > there are some differences, which are not seen in Dave's build: >http://gcc.gnu.org/ml/gcc-testresults/2009-11/msg00047.html For a release, I wouldn't use cloog/ppl. It seems to cause some loop optimization bugs. There's also an unresolved issue with pch on the 4.4 branch. I usually configure with --disable-libstdcxx-pch on the 4.4 branch. The problem seems to be fixed on head. > there are some parisc scpecific changes: > > 2009-10-23 John David Anglin > > Backport from mainline: > 2009-08-19 John David Anglin > > * pa.md (reload_inhi, reload_outhi, reload_inqi, reload_outqi): New > patterns. > * pa.c (emit_move_sequence): Check if address of operand1 is valid > for mode mode of operand0 when doing secondary reload for SAR. > > 2009-10-20 John David Anglin > > Backport from mainline: > 2009-10-15 John David Anglin > > PR target/41702 > * pa.md (casesi): Use sign extended index in call to > gen_casesi64p. > (casesi64p): Update pattern to reflect above. I doubt either of these is the problem. The latter is specific to hppa64. The former is to fix an ICE compiling recent linux kernels. Dave -- J. David Anglin dave.ang...@nrc-cnrc.gc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#554574: libstdc++6: apt segfaults on hppa
On 08.11.2009 21:38, John David Anglin wrote: test results for 4.4.2-1: http://gcc.gnu.org/ml/gcc-testresults/2009-10/msg01919.html for 4.4.2-2: http://gcc.gnu.org/ml/gcc-testresults/2009-11/msg00351.html there are some differences, which are not seen in Dave's build: http://gcc.gnu.org/ml/gcc-testresults/2009-11/msg00047.html For a release, I wouldn't use cloog/ppl. It seems to cause some loop optimization bugs. does this really hurt, unless the loop opts are used? There's also an unresolved issue with pch on the 4.4 branch. I usually configure with --disable-libstdcxx-pch on the 4.4 branch. The problem seems to be fixed on head. ok, I'll add this for hppa. Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#554574: libstdc++6: apt segfaults on hppa
> On 08.11.2009 21:38, John David Anglin wrote: > >> test results for 4.4.2-1: > >> http://gcc.gnu.org/ml/gcc-testresults/2009-10/msg01919.html > >> for 4.4.2-2: > >> http://gcc.gnu.org/ml/gcc-testresults/2009-11/msg00351.html > >> > >> there are some differences, which are not seen in Dave's build: > >> http://gcc.gnu.org/ml/gcc-testresults/2009-11/msg00047.html > > > > For a release, I wouldn't use cloog/ppl. It seems to cause some > > loop optimization bugs. > > does this really hurt, unless the loop opts are used? The testsuite fails that seem related to this are: FAIL: libgomp.c/omp-loop03.c execution test FAIL: libgomp.c++/loop-3.C -O execution test FAIL: 29_atomics/atomic_flag/clear/1.c execution test FAIL: 29_atomics/atomic_flag/test_and_set/explicit.c execution test FAIL: tr1/8_c_compatibility/complex/overloads_float.cc (test for excess errors) FAIL: tr1/8_c_compatibility/complex/overloads_int.cc (test for excess errors) and possibly FAIL: abi_check > > There's also an unresolved issue with > > pch on the 4.4 branch. I usually configure with --disable-libstdcxx-pch > > on the 4.4 branch. The problem seems to be fixed on head. > > ok, I'll add this for hppa. The testsuite fails related to the pch bug are: FAIL: 26_numerics/complex/13450.cc (test for excess errors) FAIL: 26_numerics/complex/pow.cc (test for excess errors) Dave -- J. David Anglin dave.ang...@nrc-cnrc.gc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
