[Bug ld/22929] x86_64 linker seg-faults when creating a shared object from an input containg relocations against note section without SHF_ALLOC

2018-03-31 Thread jeremip11 at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22929 Jeremi changed: What|Removed |Added CC||jeremip11 at gmail dot com -- You are

[Bug ld/22929] x86_64 linker seg-faults when creating a shared object from an input containg relocations against note section without SHF_ALLOC

2018-03-09 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=22929 --- Comment #11 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f657f8c4a1dc0ac69b16b1dc6eacbf5286f1f0a0 commit

[Bug ld/22929] x86_64 linker seg-faults when creating a shared object from an input containg relocations against note section without SHF_ALLOC

2018-03-08 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22929 H.J. Lu changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug ld/22929] x86_64 linker seg-faults when creating a shared object from an input containg relocations against note section without SHF_ALLOC

2018-03-08 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=22929 --- Comment #9 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by H.J. Lu : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=347a87745eab23d8427349787bde4a938a1e8c3e commit

[Bug ld/22929] x86_64 linker seg-faults when creating a shared object from an input containg relocations against note section without SHF_ALLOC

2018-03-07 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22929 H.J. Lu changed: What|Removed |Added Status|WAITING |NEW --- Comment #8 from H.J. Lu --- A

[Bug ld/22929] x86_64 linker seg-faults when creating a shared object from an input containg relocations against note section without SHF_ALLOC

2018-03-06 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22929 --- Comment #7 from H.J. Lu --- (In reply to Nick Clifton from comment #5) > Hi H.J. > > > The value will be wrong. Linker can only resolve PC relative relocations> > > against local definition. > But can't the linker assume that the

[Bug ld/22929] x86_64 linker seg-faults when creating a shared object from an input containg relocations against note section without SHF_ALLOC

2018-03-06 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22929 --- Comment #6 from Nick Clifton --- Created attachment 10873 --> https://sourceware.org/bugzilla/attachment.cgi?id=10873=edit Assembler source for the object file Hi H.J. Here is the assembler source. Cheers Nick -- You are

[Bug ld/22929] x86_64 linker seg-faults when creating a shared object from an input containg relocations against note section without SHF_ALLOC

2018-03-06 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22929 --- Comment #5 from Nick Clifton --- Hi H.J. > The value will be wrong. Linker can only resolve PC relative relocations> > against local definition. But can't the linker assume that the object is located at address 0 and resolve the

Re: [Bug ld/22929] x86_64 linker seg-faults when creating a shared object from an input containg relocations against note section without SHF_ALLOC

2018-03-06 Thread Nick Clifton
Hi H.J. > The value will be wrong. Linker can only resolve PC relative relocations> > against local definition. But can't the linker assume that the object is located at address 0 and resolve the relocations using that ? It does not matter that this address will not match the run-time address

[Bug ld/22929] x86_64 linker seg-faults when creating a shared object from an input containg relocations against note section without SHF_ALLOC

2018-03-06 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22929 --- Comment #3 from H.J. Lu --- (In reply to Nick Clifton from comment #2) > Hi H.J. > > > Since these relocations > > are in non-allocatable sections, should linker treat them as in > > debug section? > > Ideally not. If I understand the