[Bug ld/4454] [regression] ld errors: no .eh_frame_hdr table will be created.

2007-05-02 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-05-03 07:55 --- If that is the only problem, it's easily fixed. cie->personality is only used when checking that two CIEs are equivalent. Since we are fairly late in the link process here, you could use a bfd_vma set to

[Bug ld/4454] [regression] ld errors: no .eh_frame_hdr table will be created.

2007-05-02 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2007-05-03 03:51 --- Subject: Re: [regression] ld errors: no .eh_frame_hdr table will be created. > I don't think anything more can be done at the gcc end. The most likely > problem is _bfd_elf_discard_section_eh_fram

[Bug ld/4454] [regression] ld errors: no .eh_frame_hdr table will be created.

2007-05-02 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2007-05-03 02:43 --- Subject: Re: [regression] ld errors: no .eh_frame_hdr table will be created. > --- Additional Comments From amodra at bigpond dot net dot au 2007-05-02 > 23:48 --- > The patch merely warn

[Bug ld/4454] [regression] ld errors: no .eh_frame_hdr table will be created.

2007-05-02 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-05-02 23:48 --- The patch merely warns about a problem that existed before. It's a real problem too. C++ exception handling will be slow for you if you have .eh_frame_hdr without the lookup table. -- http://sourcewa

[Bug ld/4454] [regression] ld errors: no .eh_frame_hdr table will be created.

2007-05-02 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2007-05-02 23:42 --- Subject: Re: New: [regression] ld errors: no .eh_frame_hdr table will be created. > > building the gcc-4.2.0 RC2 with binutils_20070426 on Debian unstable, some > > hundred testcases fail like:

[Bug ld/4454] [regression] ld errors: no .eh_frame_hdr table will be created.

2007-05-02 Thread doko at debian dot org
--- Additional Comments From doko at debian dot org 2007-05-02 22:36 --- checking with a 20070210 build, starting the build now; will have results tomorrow; I didn't build newer snapshots on hppa. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4454 --- You are receiving this

[Bug ld/4454] [regression] ld errors: no .eh_frame_hdr table will be created.

2007-05-02 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2007-05-02 22:32 --- Subject: Re: New: [regression] ld errors: no .eh_frame_hdr table will be created. > building the gcc-4.2.0 RC2 with binutils_20070426 on Debian unstable, some > hundred testcases fail like: 2.17

[Bug ld/4454] New: [regression] ld errors: no .eh_frame_hdr table will be created.

2007-05-02 Thread doko at debian dot org
building the gcc-4.2.0 RC2 with binutils_20070426 on Debian unstable, some hundred testcases fail like: PASS: g++.dg/other/classkey1.C (test for excess errors) Executing on host: /scratch/packages/gcc/4.2/gcc-4.2-4.2-20070502/build/gcc/testsuite/g++/../../g++ -B/s cratch/packages/gcc/4.2/gcc-4.2

[Bug binutils/4453] New: ar doesn't recognize ELF64 on mips

2007-05-02 Thread aurelien at aurel32 dot net
ar (and ranlib) do not correctly identify ELF64 files in an archive. It complains that the format is ambiguous. See the testcase below: [tesla:~]$ touch foo.c [tesla:~]$ gcc -mabi=64 -o foo.o -c foo.c [tesla:~]$ ar cq libfoo.a foo.o [tesla:~]$ ar t libfoo.a ar: libfoo.a: File format is ambiguous

[Bug gas/4448] overstrict check for powerpc lswi

2007-05-02 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-05-02 12:26 --- http://sourceware.org/ml/binutils-cvs/2007-04/msg00194.html -- What|Removed |Added

[Bug gas/4448] overstrict check for powerpc lswi

2007-05-02 Thread amodra at bigpond dot net dot au
-- What|Removed |Added Status|NEW |ASSIGNED Last reconfirmed|-00-00 00:00:00 |2007-05-02 12:26:48 date|

[Bug gas/4448] overstrict check for powerpc lswi

2007-05-02 Thread amodra at bigpond dot net dot au
-- What|Removed |Added AssignedTo|unassigned at sources dot |amodra at bigpond dot net |redhat dot com |dot au http://sourceware.org/bugzil

[Bug gas/4448] overstrict check for powerpc lswi

2007-05-02 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-05-02 12:13 --- Eep, I see. gcc/config/rs6000.c:expand_block_move masks the byte count to 5 bits. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4448 --- You are receiving this mail because: --- You are

[Bug gas/4448] overstrict check for powerpc lswi

2007-05-02 Thread doko at debian dot org
--- Additional Comments From doko at debian dot org 2007-05-02 11:35 --- seen in linux-2.6.21 build by a Debian maintainer: CC arch/powerpc/kernel/binfmt_elf32.o {standard input}: Assembler messages: {standard input}:988: Error: operand out of range (0 is not between 1 and 32) {s

[Bug gas/4448] overstrict check for powerpc lswi

2007-05-02 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-05-02 11:04 --- Hmm, I guess there isn't any harm in allowing a zero in the third arg to mean 32. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4448 --- You are receiving this mail because: --- You are o

[Bug gas/4448] overstrict check for powerpc lswi

2007-05-02 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-05-02 11:03 --- Did someone hit this in real code? I've always taken the description in the reference manual to mean the field rather than what is specified on the assembly line. Quite obviously, a value of 0 in the 5-b