[Bug ld/6590] Linker-generated TOC16_DS relocations are misplaced

2008-06-04 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2008-06-05 00:31 --- http://sourceware.org/ml/binutils-cvs/2008-06/msg00021.html -- What|Removed |Added

[Bug ld/6590] Linker-generated TOC16_DS relocations are misplaced

2008-06-04 Thread yaari at il dot ibm dot com
-- What|Removed |Added CC||amodra at bigpond dot net ||dot au, sjmunroe at us dot

[Bug ld/6590] New: Linker-generated TOC16_DS relocations are misplaced

2008-06-04 Thread yaari at il dot ibm dot com
Following a recent change for handling --emit-relocs switch the Linker started producing static relocations for code generated by the linker itself. When generating R_PPC64_TOC16_DS relocations, which affects the low-order 16-bit of the instruction, the linker places them instead on the instructio

[Bug ld/6019] [avr] avr-ld --relax requires --gc-sections

2008-06-04 Thread nickc at redhat dot com
--- Additional Comments From nickc at redhat dot com 2008-06-04 09:59 --- Hi Guys, Great - I have applied the patch along with the changelog entry below. Cheers Nick bfd/ChangeLog PR ld/6019 * elf32-avr.c (elf32_avr_relax_section): Handle the case where the

Re: ld should support --no-fatal-warnings

2008-06-04 Thread Nick Clifton
Hi Chris, This turns out to be convenient in cases where one's build system defaults to "ld --fatal-warning" but occasionally one would like to override it. It's also parallel to existing gcc conventions for setting and unsetting options. See attached diff to ld/lexsup.c; it's against 2.17

[Bug ld/6446] Handling of EF_FRV_PIC

2008-06-04 Thread nickc at redhat dot com
--- Additional Comments From nickc at redhat dot com 2008-06-04 09:28 --- Subject: Re: Handling of EF_FRV_PIC Hi Alex, Hi Daniel, > The patch does indeed appear to get the code to patch the spec (thanks, > Nick!), > but I'm concerned that, at this point, it might be wiser to change t

Re: [Bug ld/6446] Handling of EF_FRV_PIC

2008-06-04 Thread Nick Clifton
Hi Alex, Hi Daniel, The patch does indeed appear to get the code to patch the spec (thanks, Nick!), but I'm concerned that, at this point, it might be wiser to change the spec to match the code, for a couple of kernels and libcs might be relying on the current bug :-( Can we do that ? I would