[Bug gas/23412] New: .intel_syntax noprefix vs -msyntax=intel -mnaked-reg segment override inconsistency

2018-07-13 Thread jesse at eclypsium dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23412 Bug ID: 23412 Summary: .intel_syntax noprefix vs -msyntax=intel -mnaked-reg segment override inconsistency Product: binutils Version: 2.30 Status: UNCONFIRMED

[Bug binutils/22887] null pointer dereference in aout_32_swap_std_reloc_out

2018-07-13 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22887 Alan Modra changed: What|Removed |Added CC||zhanggen12 at hotmail dot com ---

[Bug binutils/23405] Some inputs may cause objcopy to crash, without being detected by error checking or assertions

2018-07-13 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23405 Alan Modra changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug gold/23411] New: Different behavior when linking common symbol statically or to shared object

2018-07-13 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23411 Bug ID: 23411 Summary: Different behavior when linking common symbol statically or to shared object Product: binutils Version: 2.32 (HEAD) Status: NEW

[Bug gold/23258] Linker cored dump at process_one_opcode

2018-07-13 Thread ccoutant at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23258 --- Comment #8 from Cary Coutant --- I was just using g++ as the linker driver, not to compile the objects. I linked with the objects you provided, which had been compiled by clang. Linking just those objects by themselves produces no

Re: [Bug gold/23258] Linker cored dump at process_one_opcode

2018-07-13 Thread Cary Coutant
I was just using g++ as the linker driver, not to compile the objects. I linked with the objects you provided, which had been compiled by clang. Linking just those objects by themselves produces no warnings at all, since the "tempnam" warning comes from libc. On Fri, Jul 13, 2018 at 12:05 PM,

[Bug gold/23258] Linker cored dump at process_one_opcode

2018-07-13 Thread lpham54321 at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23258 --- Comment #7 from Lan --- It's the loader that trapped, but it was clang6 that was generating the object file. Can you try just invoking the loader directly against the static archive libSTdb2gse.a to see if you can repro the trap?

[Bug gold/23258] Linker cored dump at process_one_opcode

2018-07-13 Thread ccoutant at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23258 --- Comment #3 from Cary Coutant --- I can't extract anything from the .tar file you provided -- tar tv and tar xv just hang indefinitely. -- You are receiving this mail because: You are on the CC list for the bug.

Re: [Bug gold/23258] Linker cored dump at process_one_opcode

2018-07-13 Thread Cary Coutant
Got it now -- sorry, problem on my end. On Fri, Jul 13, 2018 at 11:14 AM, lpham54321 at gmail dot com wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=23258 > > --- Comment #4 from Lan --- > hmm ... worked just fine for me. > > lans-mbp:downloads lanpham$ tar -xvf bug_23258.tar > x

[Bug gold/23258] Linker cored dump at process_one_opcode

2018-07-13 Thread ccoutant at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23258 --- Comment #5 from Cary Coutant --- Got it now -- sorry, problem on my end. On Fri, Jul 13, 2018 at 11:14 AM, lpham54321 at gmail dot com wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=23258 > > --- Comment #4 from Lan --- > hmm

[Bug gold/23411] Different behavior when linking common symbol statically or to shared object

2018-07-13 Thread amonakov at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23411 Alexander Monakov changed: What|Removed |Added CC||amonakov at gmail dot com ---

[Bug gold/22755] gold test suite failures (gentoo, 2.31)

2018-07-13 Thread ccoutant at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22755 --- Comment #4 from Cary Coutant --- Well, that didn't help -- nothing in config.log helps me reproduce these failures. I'll need some more of your help. Let's start with the first one; with luck, there's just one thing going on that's

[Bug gold/23258] Linker cored dump at process_one_opcode

2018-07-13 Thread lpham54321 at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23258 --- Comment #4 from Lan --- hmm ... worked just fine for me. lans-mbp:downloads lanpham$ tar -xvf bug_23258.tar x bug_23258/libSTdb2gse.a x bug_23258/lnk.sh lans-mbp:downloads lanpham$ -- You are receiving this mail because: You are on the

[Bug gold/23258] Linker cored dump at process_one_opcode

2018-07-13 Thread ccoutant at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23258 --- Comment #6 from Cary Coutant --- I don't have clang installed, but when I use g++ instead, I get the following: GseAdEnableDB.o: In function `GseAdmTempFile(char*, char const*, char const*, GseError&)':

[Bug gold/23258] Linker cored dump at process_one_opcode

2018-07-13 Thread lpham54321 at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23258 --- Comment #9 from Lan --- ok. I assume that you want me to try addressing the warning to see if it is indeed related to the core dump. I will try this and let you know how it's go. -- You are receiving this mail because: You are on the CC

[Bug gold/23411] Different behavior when linking common symbol statically or to shared object

2018-07-13 Thread ccoutant at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23411 Cary Coutant changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug gold/23411] Different behavior when linking common symbol statically or to shared object

2018-07-13 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23411 --- Comment #3 from H.J. Lu --- We can agree to disagree. I believe the new rule should be enforced by compiler not to generate COMMON symbol, not by linker. -- You are receiving this mail because: You are on the CC list for the bug.