This has been fixed as part of PR ld/3191 by Daniel Jacobowitz (on
2008/09/19)
Christophe.
On 30.09.2008 00:06, geir at cray dot com wrote:
Using ld version 2.18 when linking a PGI 7.2-5 compiled program, I see the
following dwarf error:
$ cat datatypes.module.f90
module datatypes
integer,
--- Additional Comments From christophe dot lyon at st dot com 2008-09-30
07:50 ---
Subject: Re: New: ld does not understand DWARF version 3 when
trying to get a source line number
This has been fixed as part of PR ld/3191 by Daniel Jacobowitz (on
2008/09/19)
Christophe.
On
Hi Terpstra,
The attached patch compares the desired BFS_{GLOBAL,LOCAL,WEAK} state
against the classification of the native symbol. If these differ, it
overwrites the sclass in the same way a new symbol would have been
created.
Is this the right place to send a binutils patch?
Yes it is.
On Tue, Sep 30, 2008 at 12:47 PM, Nick Clifton [EMAIL PROTECTED] wrote:
Do you have an FSF binutils copyright assignment in place ?
No. As you pointed out though, the patch was small, more like a
targeted bug report really.
Anyway I have checked over your patch - it is good although there are
--
What|Removed |Added
CC||geir at cray dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=3191
--- You are receiving this mail
The CRIS port has const char line_separator_chars[] = @;
Apparently this causes a conflict with the \@ macro invocation number counter,
as evident by building and checking for cris-axis-linux-gnu:
Running x/src/ld/testsuite/ld-elf/elf.exp ...
FAIL: ld-elf/multibss1
with ld.log saying:
--- Additional Comments From hp at sourceware dot org 2008-10-01 00:04
---
(In reply to comment #0)
...haven't tested if there's a similar
FAIL for ARM where comment_chars contains @.
Nope, the test passes there.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6926
---
