at gmail dot com |hjl.tools at gmail dot
com
Severity|normal |enhancement
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https
at gmail dot com |hjl.tools at gmail dot
com
Severity|normal |enhancement
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https
https://sourceware.org/bugzilla/show_bug.cgi?id=18327
Cary Coutant changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from Cary Cout
at gmail dot com |shenhan at google dot
com
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
at gmail dot com |shenhan at google dot
com
--- Comment #1 from Cary Coutant ---
Did this only recently start failing?
Han, can you take a look, please?
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug
https://sourceware.org/bugzilla/show_bug.cgi?id=17819
--- Comment #4 from Cary Coutant ---
> I have encountered this problem, too.
> Is a patch coming soon, or should I pursue a workaround?
I've been working on fixing this, but it's going to take some time.
Workarounds are to use a different --
https://sourceware.org/bugzilla/show_bug.cgi?id=17819
Cary Coutant changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=15370
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18378
--- Comment #5 from Cary Coutant ---
Who should I assign this to?
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
htt
https://sourceware.org/bugzilla/show_bug.cgi?id=18430
Cary Coutant changed:
What|Removed |Added
Assignee|ccoutant at gmail dot com |shenhan at google dot
com
https://sourceware.org/bugzilla/show_bug.cgi?id=18307
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18288
Cary Coutant changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #16 from Cary Cout
https://sourceware.org/bugzilla/show_bug.cgi?id=18308
Cary Coutant changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #5 from Cary Couta
https://sourceware.org/bugzilla/show_bug.cgi?id=17498
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=17498
--- Comment #5 from Cary Coutant ---
Testcase, please.
I'm not sure what you're asking for here, though. You want to make -X the
default?
--
You are receiving this mail because:
You are on the CC list for the bug.
_
https://sourceware.org/bugzilla/show_bug.cgi?id=17498
--- Comment #7 from Cary Coutant ---
> $ cat test.cpp
> void g(const char* x);
> void f() {
> g("aoeuaoeuaoeuao");
> }
> $ gcc -shared -fPIC test.cpp -o test.so -fuse-ld=bfd -O2 && nm test.so |
> grep ' r '
> 0728 r __FRAME_END_
https://sourceware.org/bugzilla/show_bug.cgi?id=17498
Cary Coutant changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18200
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=11182
Cary Coutant changed:
What|Removed |Added
CC||ccoutant at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=18288
Cary Coutant changed:
What|Removed |Added
Status|WAITING |ASSIGNED
Summary|linker -s
https://sourceware.org/bugzilla/show_bug.cgi?id=18288
--- Comment #21 from Cary Coutant ---
*** Bug 18308 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mai
https://sourceware.org/bugzilla/show_bug.cgi?id=18308
Cary Coutant changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18288
Cary Coutant changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=17731
--- Comment #8 from Cary Coutant ---
(In reply to Markus Trippelsdorf from comment #5)
> Indeed with the following kernel patch "fixes" the issue for me:
>
> diff --git a/include/asm-generic/vmlinux.lds.h
> b/include/asm-generic/vmlinux.lds.h
https://sourceware.org/bugzilla/show_bug.cgi?id=16341
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=11182
Cary Coutant changed:
What|Removed |Added
CC||gideon at accursoft dot com
--- Commen
https://sourceware.org/bugzilla/show_bug.cgi?id=17731
Cary Coutant changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18614
Cary Coutant changed:
What|Removed |Added
Priority|P2 |P3
--- Comment #1 from Cary Coutant -
||ccoutant at gmail dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
https://sourceware.org/bugzilla/show_bug.cgi?id=18614
Cary Coutant changed:
What|Removed |Added
Status|NEW |ASSIGNED
--
You are receiving this ma
https://sourceware.org/bugzilla/show_bug.cgi?id=18609
Cary Coutant changed:
What|Removed |Added
Assignee|ccoutant at gmail dot com |hjl.tools at gmail dot
com
https://sourceware.org/bugzilla/show_bug.cgi?id=18596
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=15574
Cary Coutant changed:
What|Removed |Added
CC||danalbert at google dot com
--- Commen
https://sourceware.org/bugzilla/show_bug.cgi?id=15574
Cary Coutant changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18698
Cary Coutant changed:
What|Removed |Added
CC||ccoutant at gmail dot com
--- Comment
https://sourceware.org/bugzilla/show_bug.cgi?id=18698
Cary Coutant changed:
What|Removed |Added
Assignee|andrew.n.senkevich at gmail dot co |ccoutant at gmail dot
com
https://sourceware.org/bugzilla/show_bug.cgi?id=18698
Cary Coutant changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18548
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
--- Comment #1 from Cary Coutant ---
You're looking at the linker symbol table with nm. (And nm does not show
versioning information from the .gnu.version* sections.)
When I build this with gold, readelf -Vs shows:
Symbol table '.dynsym' con
mment #2 from Sriraman Tallam ---
> On Tue, Jul 21, 2015 at 11:03 AM, ccoutant at gmail dot com
> wrote:
>> https://sourceware.org/bugzilla/show_bug.cgi?id=18703
>>
>> --- Comment #1 from Cary Coutant ---
>> You're looking at the linker symbol table with nm. (And
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
--- Comment #6 from Cary Coutant ---
>Another usage of the '.symver' directive is:
> .symver NAME, NAME2@@NODENAME
>In this case, the symbol NAME must exist and be defined within the
> file being assembled. It is similar to NAME2
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
--- Comment #10 from Cary Coutant ---
>> T foo
>> T foo@VERS_1.1
>>
>> With the version script, gold sees the first of those (plain "foo")
>> and makes it the default version (as, I think, it should). The seco
https://sourceware.org/bugzilla/show_bug.cgi?id=18521
Cary Coutant changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment
https://sourceware.org/bugzilla/show_bug.cgi?id=18628
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18663
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18521
--- Comment #3 from Cary Coutant ---
*** Bug 18663 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mail
https://sourceware.org/bugzilla/show_bug.cgi?id=18521
--- Comment #5 from Cary Coutant ---
Sigh. This bug isn't really a duplicate of PR 18628 (it's really 18268 that
duplicates a subset of this one). Let's consider this bug split into PR 18628
(for the IFUNC failures) and PR 18863 (for the scrip
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
--- Comment #12 from Cary Coutant ---
> The documentation can have some improvements. But ld.bfd behavior is
> well-defined as shown by testcases in ld/testsuite/ld-elfvers.
If you're going to maintain that ".symver foo,foo@VER" is valid, th
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
--- Comment #18 from Cary Coutant ---
Another change you can make is to remove "foo" from the version script
entirely. If foo.map is just this:
VERS_1.1 {
};
then both linkers will put "foo@VERS_1.1" into the dynamic symbol
table (no default
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
--- Comment #19 from Cary Coutant ---
> FAIL: vers1
This is because gold does not handle "sym@" properly. Working on it.
> FAIL: vers2
> FAIL: vers3
> FAIL: vers6
> FAIL: vers8
These look like the same root problem.
> ERROR: tcl error sour
https://sourceware.org/bugzilla/show_bug.cgi?id=18720
Cary Coutant changed:
What|Removed |Added
CC||ccoutant at gmail dot com
--- Comment
https://sourceware.org/bugzilla/show_bug.cgi?id=18834
Cary Coutant changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from Cary Cout
https://sourceware.org/bugzilla/show_bug.cgi?id=18836
Cary Coutant changed:
What|Removed |Added
CC||ccoutant at gmail dot com
--- Comment
https://sourceware.org/bugzilla/show_bug.cgi?id=18837
Cary Coutant changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from Cary Cout
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18847
Cary Coutant changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from Cary Cout
https://sourceware.org/bugzilla/show_bug.cgi?id=18845
Cary Coutant changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from Cary Cout
https://sourceware.org/bugzilla/show_bug.cgi?id=18837
--- Comment #4 from Cary Coutant ---
> I see. So I'm trying (same input):
>
> SECTIONS {
> .debug_info 0 : { *(.gnu.lto_.debug_info*) }
> .debug_abbrev 0 : { *(.gnu.lto_.debug_abbrev*) }
> .debug_str 0 : { *(.gnu.lto_.debug_str*) }
>
https://sourceware.org/bugzilla/show_bug.cgi?id=18859
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18855
--- Comment #1 from Cary Coutant ---
Sorry, I don't have a SPARC development environment, so to investigate this,
I'm going to need all the .o files (real .o files, not LTO intermediates).
Does it still fail without -flto?
Can you add -Wl,--
https://sourceware.org/bugzilla/show_bug.cgi?id=14746
--- Comment #8 from Cary Coutant ---
> What I had to do to reproduce it was to add a symbol in my linker script
> that pointed to the address of .eh_frame. It's the same assert but I'm not
> sure that it's the same problem.
>
> Repo:
> test.c
airs dot com|ccoutant at gmail dot
com
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
https://sourceware.org/bugzilla/show_bug.cgi?id=18859
Cary Coutant changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
||ccoutant at gmail dot com
Resolution|--- |FIXED
--- Comment #2 from Cary Coutant ---
Fixed on trunk.
These patches fixed 843419:
https://sourceware.org/ml/binutils-cvs/2015-04/msg00152.html
https://sourceware.org/ml/binutils-cvs/2015-04
||ccoutant at gmail dot com
--- Comment #3 from Cary Coutant ---
Waiting for more data from the reporter.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
at gmail dot com |tmsriram at google dot
com
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
https://sourceware.org/bugzilla/show_bug.cgi?id=18866
--- Comment #3 from Cary Coutant ---
I have absolutely no idea what to do with that attachment. HJ, what is it? It
downloads as "lto.bc", and contains random garbage.
--
You are receiving this mail because:
You are on the CC list for the bug
https://sourceware.org/bugzilla/show_bug.cgi?id=18866
--- Comment #4 from Cary Coutant ---
> I have absolutely no idea what to do with that attachment. HJ, what is it?
> It downloads as "lto.bc", and contains random garbage.
Oh, I see it's a bitcode file. I need .o files, please.
--
You are re
https://sourceware.org/bugzilla/show_bug.cgi?id=14187
--- Comment #3 from Cary Coutant ---
We've discussed fixing this before, but we now have legacy scripts that invoke
gold with decimal values, and changing it would break them. We could certainly
peek at the number and treat it as hex if it has
https://sourceware.org/bugzilla/show_bug.cgi?id=18866
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18859
Cary Coutant changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18847
Cary Coutant changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
airs dot com|ccoutant at gmail dot
com
--- Comment #11 from Cary Coutant ---
Created attachment 8557
--> https://sourceware.org/bugzilla/attachment.cgi?id=8557&action=edit
Patch to fix gold to parse -Ttext, etc., options as hex numbers
The attached patch changes gold to pa
https://sourceware.org/bugzilla/show_bug.cgi?id=14187
--- Comment #12 from Cary Coutant ---
> sure, it was first released in binutils-2.19 which was ~Oct 2008 (3 years
> before the grub report), but i don't think people generally started using it
> until later: it required distros to update, and
dot com|ccoutant at gmail dot
com
--- Comment #6 from Cary Coutant ---
Have you tried this with a gold built from HEAD?
I think that the patches for PR 18703 also fix this bug.
Referenced Bugs:
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
[Bug 18703] Symbol version
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
Cary Coutant changed:
What|Removed |Added
Blocks||13521
Referenced Bugs:
https://sourc
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
Cary Coutant changed:
What|Removed |Added
Blocks||12261
Referenced Bugs:
https://sourc
||ccoutant at gmail dot com
Depends on||18703
Assignee|ian at airs dot com|ccoutant at gmail dot
com
--- Comment #10 from Cary Coutant ---
Fixed by PR 18703. Gold will accept the base version definition, but the
at gmail dot com |hjl.tools at gmail dot
com
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
https://sourceware.org/bugzilla/show_bug.cgi?id=18930
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=13521
--- Comment #8 from Cary Coutant ---
> Dynamic linking is OK - but the symtab from gold doesn't have any symbol
> versions even on glibc symbols, so it is a different thing.
>
> I think this bug can be closed, thanks
That's correct -- gold do
https://sourceware.org/bugzilla/show_bug.cgi?id=18703
Cary Coutant changed:
What|Removed |Added
CC||jrnieder at gmail dot com
--- Comment
https://sourceware.org/bugzilla/show_bug.cgi?id=13521
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18959
--- Comment #2 from Cary Coutant ---
> How about this patch? Seems to fix the issue on s390. However, the empty
> string
> seems to have been special-cased on purpose and I'm afraid it could mess
> something up.
I don't really know why the e
https://sourceware.org/bugzilla/show_bug.cgi?id=18935
--- Comment #2 from Cary Coutant ---
> Seems a bit unclear what the expected behavior is.
>
> .init_stack (NOLOAD) :
> {
>. = . + 0x200;
> } :ph_load
> With this ld.bfd creates a NOBITS SHF_ALLOC section(just like .bss).
>
> When a new
https://sourceware.org/bugzilla/show_bug.cgi?id=14187
--- Comment #14 from Cary Coutant ---
(In reply to Stas Sergeev from comment #13)
> (In reply to Cary Coutant from comment #11)
> > Created attachment 8557 [details]
> > Patch to fix gold to parse -Ttext, etc., options as hex numbers
> > The a
https://sourceware.org/bugzilla/show_bug.cgi?id=18935
--- Comment #4 from Cary Coutant ---
> This script looks like it's trying to create an unloadable section,
> then allocate it to a loadable segment. If all the script is trying to
> do is create a loadable NOBITS section, the NOLOAD attribute
https://sourceware.org/bugzilla/show_bug.cgi?id=18975
--- Comment #1 from Cary Coutant ---
The way to fill holes in a section when using scripts is to specify a fill
pattern; e.g.:
SECTIONS {
.text : { *(.text) } = 0x90909090
}
or
SECTIONS {
.text : { FILL(0x90909090) *(.text)
at gmail dot com |shenhan at google dot
com
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
at gmail dot com |shenhan at google dot
com
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
https://sourceware.org/bugzilla/show_bug.cgi?id=19019
Cary Coutant changed:
What|Removed |Added
CC||davem at davemloft dot net
--- Comment
https://sourceware.org/bugzilla/show_bug.cgi?id=18855
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=18855
--- Comment #8 from Cary Coutant ---
> I made a automatic test case for it (see attachment). I think the ltrans.*.s
> file in my archive are my own gcc invocation on sparc64, but the files from
> attachment 8619 [details] should do as well. Ju
at gmail dot com |hjl.tools at gmail dot
com
Severity|normal |enhancement
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https
https://sourceware.org/bugzilla/show_bug.cgi?id=19019
--- Comment #18 from Cary Coutant ---
Yes, I'm working on it. I think it's going to need some additional
work in non-target-specific code to support this feature.
-cary
On Mon, Oct 12, 2015 at 3:10 AM, jose.marchesi at oracle dot com
wrote
https://sourceware.org/bugzilla/show_bug.cgi?id=19119
--- Comment #2 from Cary Coutant ---
Yes, gold uses the target of the first object file; only if there are
no object files does it use the -m option (note that the option is
marked "obsolete").
-cary
On Wed, Oct 14, 2015 at 7:39 AM, hjl.too
https://sourceware.org/bugzilla/show_bug.cgi?id=19140
Cary Coutant changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=19140
--- Comment #3 from Cary Coutant ---
(In reply to Rafael Ávila de Espíndola from comment #1)
> The issue in gold can be avoided by making the declaration hidden:
>
> .section bar, "a"
> .hidden __start_bar
> .quad __st
https://sourceware.org/bugzilla/show_bug.cgi?id=19140
--- Comment #4 from Cary Coutant ---
(In reply to Cary Coutant from comment #3)
> (In reply to Rafael Ávila de Espíndola from comment #1)
> > The issue in gold can be avoided by making the declaration hidden:
> >
> > .section bar, "a"
https://sourceware.org/bugzilla/show_bug.cgi?id=19140
--- Comment #6 from Cary Coutant ---
>> I should qualify that by saying it "works" in the sense that I see an
>> absolute R_X86_64_64 relocation instead of RELATIVE, but it ought to have
>> the same effect.
>
> That would still be a problem if
1 - 100 of 410 matches
Mail list logo
