[Bug binutils/21281] ASAN detects memory leak in sysinfo.c
https://sourceware.org/bugzilla/show_bug.cgi?id=21281 Thuan Pham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Thuan Pham --- Hi Nick, Thank you. Your suggestion resolves the reported issue. Cheers, Thuan -- 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
[Bug binutils/21233] Internal error, /usr/bin/ld: BFD (GNU Binutils for Debian) 2.28 assertion fail ../../bfd/elfxx-mips.c:3861
https://sourceware.org/bugzilla/show_bug.cgi?id=21233 --- Comment #10 from Gianfranco --- The fix is confirmed, after two days ghc finally is finishing the build! (the part where the link was failing is succeeding now, and the build is ending in a few hours). So, confirming that now it works. -- 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
[Bug binutils/21233] Internal error, /usr/bin/ld: BFD (GNU Binutils for Debian) 2.28 assertion fail ../../bfd/elfxx-mips.c:3861
https://sourceware.org/bugzilla/show_bug.cgi?id=21233 --- Comment #11 from Gianfranco --- thanks you all! -- 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
[Bug gold/21285] New: R_386_GOT32 for baseless case looks implemented incorrectly.
https://sourceware.org/bugzilla/show_bug.cgi?id=21285 Bug ID: 21285 Summary: R_386_GOT32 for baseless case looks implemented incorrectly. Product: binutils Version: 2.29 (HEAD) Status: UNCONFIRMED 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: --- Created attachment 9926 --> https://sourceware.org/bugzilla/attachment.cgi?id=9926&action=edit got32-i386.s.tmp.o According to ABI, R_386_GOT32 (https://github.com/hjl-tools/x86-psABI/wiki/intel386-psABI-draft.pdf) can be calculated as G + A without base register when position-independent code is disabled. Imagine next asm code: .text .globl bar .type bar, @function bar: .globl foo .type foo, @function foo: _start: movl bar@GOT, %eax movl foo@GOT, %ebx movl bar@GOT(%eax), %eax movl foo@GOT(%ebx), %eax I used llvm-mc -relax-relocations=false to compile it into got32-i386.s.tmp.o (attached), its disassembly is: Disassembly of section .text: : 0: a1 00 00 00 00 mov0x0,%eax 5: 8b 1d 00 00 00 00 mov0x0,%ebx b: 8b 80 00 00 00 00 mov0x0(%eax),%eax 11: 8b 83 00 00 00 00 mov0x0(%ebx),%eax Relocation section '.rel.text' at offset 0x8c contains 4 entries: Offset InfoTypeSym.Value Sym. Name 0001 0203 R_386_GOT32 bar 0007 0303 R_386_GOT32 foo 000d 0203 R_386_GOT32 bar 0013 0303 R_386_GOT32 foo Notice that "mov 0x0,%eax" case is encoded using a1 and not 8b xx. Gold implementation determines baseless case using following check: baseless = (view[-1] & 0xc7) == 0x5; (https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gold/i386.cc;h=0b447ef0d68f3ea8965091502d5a1302d69d1b32;hb=HEAD#l2895) That works incorrectly with "a1 00 00 00 00", gold uses 0xa1 opcode in this check, assuming it is ModRM byte, when it is not. And result calculation seems to be broken: 08048094 : 8048094: a1 fc ff ff ff mov0xfffc,%eax 8048099: 8d 1d 94 80 04 08 lea0x8048094,%ebx 804809f: 8d 80 a0 e0 ff ff lea-0x1f60(%eax),%eax 80480a5: 8d 83 a0 e0 ff ff lea-0x1f60(%ebx),%eax 0xfffc is offset in GOT, calculated using "G + A - GOT", when it should be value calculated using "G + A" I think. -- 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
[Bug gas/21287] New: Inconsistent section type for .init_array and .init_array.42
https://sourceware.org/bugzilla/show_bug.cgi?id=21287
Bug ID: 21287
Summary: Inconsistent section type for .init_array and
.init_array.42
Product: binutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gas
Assignee: unassigned at sourceware dot org
Reporter: rafael.espindola at gmail dot com
Target Milestone: ---
Given
.section.init_array.00999,"aw"
.section.init_array,"aw"
gas produces
[ 6] .init_array.00999 PROGBITS 58 08 00 WA
0 0 8
[ 8] .init_array INIT_ARRAY 60 08 00 WA
0 0 8
They should probably both be INIT_ARRAY. This shows up from C since given
struct X {
X();
};
X x __attribute__((init_priority(999)));
X y;
gcc produces the above assembly.
--
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
[Bug binutils/21290] New: nm should distinguish TLS variables
https://sourceware.org/bugzilla/show_bug.cgi?id=21290 Bug ID: 21290 Summary: nm should distinguish TLS variables Product: binutils Version: unspecified Status: NEW Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- When I run nm on a .o, a TLS global shows up like: pokyo. nm ./js/src/Unified_cpp_js_src34.o | grep Tls B _ZN2js10TlsContextE It would be handy if these could be distinguished from ordinary BSS symbols in the nm output. -- 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
[Bug binutils/21290] nm should distinguish TLS variables
https://sourceware.org/bugzilla/show_bug.cgi?id=21290 --- Comment #1 from Tom Tromey --- Mark pointed out that -f sysv does print this info. I still think it would be nice to have by default, but I'd understand if you'd prefer to close this bug. -- 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
