[Bug gas/10777] Macro processing altercation

2010-01-12 Thread konrad dot schwarz at siemens dot com
--- Additional Comments From konrad dot schwarz at siemens dot com 2010-01-12 09:52 --- (In reply to comment #1) You can easily add m4 processing to gas yourself by writing a tiny wrapper script. I see no need to add yet another feature to gas. Well, like I wrote: This option is

[Bug binutils/10773] Malformed archive created when adding several files at once

2010-01-12 Thread konrad dot schwarz at siemens dot com
--- Additional Comments From konrad dot schwarz at siemens dot com 2010-01-12 09:52 --- (In reply to comment #5) Likely a filesystem bug Actually, the bug went away went I stopped mixing 32 and 64 bit x86 ELF object files in a single archive. I am almost 100% sure this is the actual

[Bug binutils/10773] Malformed archive created when adding several files at once

2010-01-12 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-01-12 13:47 --- As I said I could not reproduce this bug with many different versions of FSF binutils. Have you built a version of FSF binutils that exhibits this bug? If so, I'd like to know which version and the arguments you

[Bug gold/11153] missing symbols in libgomp when linked with gold

2010-01-12 Thread doko at debian dot org
--- Additional Comments From doko at debian dot org 2010-01-12 14:10 --- don't see this anymore with today's binutils trunk building the gcc trunk. -- http://sourceware.org/bugzilla/show_bug.cgi?id=11153 --- You are receiving this mail because: --- You are on the CC list

[Bug binutils/10773] Malformed archive created when adding several files at once

2010-01-12 Thread konrad dot schwarz at siemens dot com
--- Additional Comments From konrad dot schwarz at siemens dot com 2010-01-12 15:37 --- (In reply to comment #7) As I said I could not reproduce this bug with many different versions of FSF binutils. Have you built a version of FSF binutils that exhibits this bug? If so, I'd like

[Bug binutils/10447] Binutils fail to build on cygwin

2010-01-12 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-01-13 00:51 --- Fixed mainline and 2.20 -- What|Removed |Added Status|NEW

[Bug ld/10406] ld terminated with signal 11 [segmentation fault]

2010-01-12 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-01-13 00:59 --- Have you managed to build one of the more recent snapshots to test whether this bug is fixed? -- What|Removed |Added

[Bug ld/10406] ld terminated with signal 11 [segmentation fault]

2010-01-12 Thread olof at baah dot se
--- Additional Comments From olof at baah dot se 2010-01-13 01:29 --- Subject: Re: ld terminated with signal 11 [segmentation fault] No, I'm sorry, but I can't. I no longer have access to the sourcecode which crashed because I've changed employment. 2010/1/13 amodra at gmail dot com

[Bug ld/10406] ld terminated with signal 11 [segmentation fault]

2010-01-12 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-01-13 02:46 --- In that case, I'm going to assume that the patch I applied 2009-09-18 fixed the problem. -- What|Removed |Added

[Bug ld/10409] Load address generated correctly, but applied incorrectly.

2010-01-12 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-01-13 03:09 --- I wonder why .ncdata has size zero in your map? I would have expected .ncdata 0x11e96ed80x8 load address 0x01e96ed8 0x11e96ee0. = ALIGN (0x10) *fill*

[Bug ld/10409] Load address generated correctly, but applied incorrectly.

2010-01-12 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-01-13 04:33 --- Created an attachment (id=4510) -- (http://sourceware.org/bugzilla/attachment.cgi?id=4510action=view) possible fix I reckon this could be the same problem as one I fixed for ppc64 in

[Bug ld/10409] Load address generated correctly, but applied incorrectly.

2010-01-12 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-01-13 04:35 --- Please try out the fix against your sources. I don't have arm compilers readily available to test this out myself -- http://sourceware.org/bugzilla/show_bug.cgi?id=10409 --- You are receiving this mail

[Bug ld/11164] New: [avr] EEPROM location wrong for XMEGA

2010-01-12 Thread eric dot weddington at atmel dot com
From SourceForge bug #2886068 (WinAVR project]: To use EEPROM memory mapping on XMEGA, the address of EEPROM variables must start at offset 0x1000 instead of 0. This should be done by changing all the XMEGA linker scripts so the .eeprom section starts at 0x811000 instead of 0x81. There appear

[Bug ld/11164] [avr] EEPROM location wrong for XMEGA

2010-01-12 Thread eric dot weddington at atmel dot com
--- Additional Comments From eric dot weddington at atmel dot com 2010-01-13 04:51 --- This enhancement is referring to xmega devices for the avr target, which involves an additional patch which is forthcoming. -- http://sourceware.org/bugzilla/show_bug.cgi?id=11164 --- You are

[Bug binutils/10316] pei-i386 --all-headers Segfault

2010-01-12 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-01-13 05:24 --- Appears to be fixed in 2.20 -- What|Removed |Added Status|NEW

[Bug ld/10259] ld generates bad long branch stubs

2010-01-12 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-01-13 05:27 --- I wonder if this bug might be fixed by the patch I attached to http://sourceware.org/bugzilla/show_bug.cgi?id=10409 -- http://sourceware.org/bugzilla/show_bug.cgi?id=10259 --- You are receiving this mail

[Bug ld/10356] Segfault in ld with --eh-frame-header for Thumb2

2010-01-12 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-01-13 06:24 --- Is this problem present in current binutils? There have been fixes to the A8 erratum handling code since your report. Also, you might like to see whether my proposed fix for