[Bug binutils/26405] [objdump, readelf] - PT_OPENBSD_* segments are not recognised.

2020-08-27 Thread georgerim at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26405 --- Comment #3 from georgerim at gmail dot com --- Thanks, Nick! -- You are receiving this mail because: You are on the CC list for the bug.

[Bug binutils/26405] New: [objdump, readelf] - PT_OPENBSD_* segments are not recognised.

2020-08-19 Thread georgerim at gmail dot com
: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: georgerim at gmail dot com Target Milestone: --- Created attachment 12779 --> https://sourceware.org/bugzilla/attachment.cgi?id=12779&action=edit sample test

[Bug gold/22868] Gold does not select proper symbol visibility when used with LLVM gold-plugin

2018-03-26 Thread georgerim at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22868 --- Comment #10 from georgerim at gmail dot com --- Created attachment 10916 --> https://sourceware.org/bugzilla/attachment.cgi?id=10916&action=edit Requested record file And here is mine record file for this bug. -- You are re

[Bug gold/22868] Gold does not select proper symbol visibility when used with LLVM gold-plugin

2018-03-23 Thread georgerim at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22868 --- Comment #7 from georgerim at gmail dot com --- For above case, a.o and b.o objects have symbols f1 with different visibility. -- You are receiving this mail because: You are on the CC list for the bug

[Bug gold/22868] Gold does not select proper symbol visibility when used with LLVM gold-plugin

2018-03-23 Thread georgerim at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22868 --- Comment #6 from georgerim at gmail dot com --- (In reply to Cary Coutant from comment #5) > I'm not able to reproduce this problem in my test framework. Whether or not > we override the symbol when scanning the IR, we still

[Bug gold/22868] New: Gold does not select proper symbol visibility when used with LLVM gold-plugin

2018-02-20 Thread georgerim at gmail dot com
Severity: normal Priority: P2 Component: gold Assignee: ccoutant at gmail dot com Reporter: georgerim at gmail dot com CC: ian at airs dot com Target Milestone: --- Issue is following. If we have 2 IR files, where the same weak symbol has

[Bug gold/22268] ld.gold accepts "foo = ~0xFF" in linker script while ld.bfd - not.

2017-10-09 Thread georgerim at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22268 georgerim at gmail dot com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug ld/22267] ld.bfd does not accept "foo = ~0xFF" in linker script but accepts "foo = ~ 0xFF"

2017-10-07 Thread georgerim at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22267 --- Comment #3 from georgerim at gmail dot com --- Thanks ! I can confirm this patch works, ld.bfd does not report issue anymore and produces correct symbol 'foo' for me, so output is consistent with ld.gold. Can we expect this

[Bug ld/22267] ld.bfd does not accept "foo = ~0xFF" in linker script but accepts "foo = ~ 0xFF"

2017-10-06 Thread georgerim at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22267 --- Comment #1 from georgerim at gmail dot com --- Bug for ld.gold posted here: https://sourceware.org/bugzilla/show_bug.cgi?id=22268 -- You are receiving this mail because: You are on the CC list for the bug

[Bug gold/22268] New: ld.gold accepts "foo = ~0xFF" in linker script while ld.bfd - not.

2017-10-06 Thread georgerim at gmail dot com
NCONFIRMED Severity: normal Priority: P2 Component: gold Assignee: ccoutant at gmail dot com Reporter: georgerim at gmail dot com CC: ian at airs dot com Target Milestone: --- I am using latest ld.gold built from sources: GNU gold (GN

[Bug ld/22267] New: ld.bfd does not accept "foo = ~0xFF" in linker script but accepts "foo = ~ 0xFF"

2017-10-06 Thread georgerim at gmail dot com
Status: UNCONFIRMED Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: georgerim at gmail dot com Target Milestone: --- Following linkerscript triggers an error when using "GNU ld (GNU Binutils) 2.2

[Bug gold/21285] R_386_GOT32 for baseless case looks implemented incorrectly.

2017-03-23 Thread georgerim at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21285 --- Comment #1 from georgerim at gmail dot com --- So gold implementation assumes that movl bar@GOT, %eax is always encoded using 0x8b, what is wrong, I think. Because ABI says: (https://github.com/hjl-tools/x86-psABI/wiki/intel386-psABI-1.1

[Bug gold/21285] New: R_386_GOT32 for baseless case looks implemented incorrectly.

2017-03-22 Thread georgerim at gmail dot com
: normal Priority: P2 Component: gold Assignee: ccoutant at gmail dot com Reporter: georgerim at gmail dot com CC: ian at airs dot com Target Milestone: --- Created attachment 9926 --> https://sourceware.org/bugzilla/attachment.cgi?id=9

[Bug gas/21167] gas v2.28.51 does not include .rel[a] sections to groups

2017-02-15 Thread georgerim at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21167 georgerim at gmail dot com changed: What|Removed |Added CC||georgerim at gmail dot

[Bug gas/21167] New: gas v2.28.51 does not include .rel[a] sections to groups

2017-02-15 Thread georgerim at gmail dot com
Priority: P2 Component: gas Assignee: unassigned at sourceware dot org Reporter: georgerim at gmail dot com Target Milestone: --- Assume next code (1.s): .section .text,"axG",@progbits,foo,comdat .quad bar ./as-new 1.s -o out readelf -a out