http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49746
--- Comment #22 from dave.anglin at bell dot net 2011-07-16 13:13:45 UTC --- On 15-Jul-11, at 11:59 PM, h.m.brand at xs4all dot nl wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49746 > > --- Comment #20 from H.Merijn Brand <h.m.brand at xs4all dot nl> > 2011-07-16 03:59:31 UTC --- > On Fri, 15 Jul 2011 19:15:28 +0000, "dave.anglin at bell dot net" > <gcc-bugzi...@gcc.gnu.org> wrote: > >> I think the attached change will fix the bug. > > Apparently it did! Dave++ > > I guess this will be in 4.6.2 Yes. This is regression. I messed up fixing the handling of 64-bit add/sub conditions and incorrectly changed addi/subi. They don't have 64-bit conditions. This stemmed from a change to binutils that broke the handling of 64-bit conditions completely. > > For 64bit perl: > > Test Summary Report > ------------------- > re/reg_eval.t > (Wstat: 0 > Tests: 7 Failed: 3) > Failed tests: 4-6 > ../cpan/CGI/t/tmpdir.t > (Wstat: 0 > Tests: 9 Failed: 0) > TODO passed: 3-9 > ../dist/IO/t/io_multihomed.t > (Wstat: 7424 > Tests: 1 Failed: 0) > Non-zero exit status: 29 > Parse errors: Bad plan. You planned 8 tests but ran 1. > ../dist/IO/t/io_sock.t > (Wstat: 7424 > Tests: 1 Failed: 0) > Non-zero exit status: 29 > Parse errors: Bad plan. You planned 26 tests but ran 1. > ../dist/IO/t/io_udp.t > (Wstat: 9 > Tests: 0 Failed: 0) > Non-zero wait status: 9 > Parse errors: Bad plan. You planned 7 tests but ran 0. > ../dist/Net-Ping/t/450_service.t > (Wstat: 7424 > Tests: 3 Failed: 0) > Non-zero exit status: 29 > Parse errors: Bad plan. You planned 26 tests but ran 3. > ../dist/Net-Ping/t/510_ping_udp.t > (Wstat: 65280 > Tests: 1 Failed: 0) > Non-zero exit status: 255 > Parse errors: Bad plan. You planned 2 tests but ran 1. > ../ext/Socket/t/Socket.t > (Wstat: 7424 > Tests: 2 Failed: 0) > Non-zero exit status: 29 > Parse errors: Bad plan. You planned 26 tests but ran 2. > Files=2144, Tests=465226, 1241 wallclock secs (272.44 usr 30.32 sys > + 1799.09 > cusr 204.72 csys = 2306.57 CPU) > Result: FAIL > > So gcc-4 still fails the socket stuff Does aCC work in 64-bit mode? We need this narrowed to a C testcase if it's a GCC bug. I'm also seeing a socket test fail randomly in the Ada gnat testsuite with 32-bit hppa*-*-hpux*. Dave -- John David Anglin dave.ang...@bell.net
