On Friday, 18 May 2018 at 11:28:30 UTC, Mike Franklin wrote:
On Friday, 18 May 2018 at 10:28:37 UTC, Thomas Mader wrote:
On Friday, 11 May 2018 at 04:27:20 UTC, Thomas Mader wrote:
My suspicion about the switch to glibc 2.27 being the problem
was wrong.
I did a very timeconsuming bisection and found the problem
commit to be the one which bumped binutils to 2.30.
Can somebody help me to answer the question from
https://sourceware.org/bugzilla/show_bug.cgi?id=23199#c4
please.
The object is created by the dmd backend but where in the code
is binutils used?
I'm not sure I understand. Does binutils need to be used to
generated an object file? My understanding is the DMD creates
the object file without the help of binutils.
As far as I know, that's correct. GCC-based compilers emit ASM
code only and leave assembling of the objects files to the
'binutils as' assembler. That's probably the reason they assumed
it's a binutils bug. For DMD, binutils is not involved when
creating object files. So this is likely a DMD bug.
-- Johannes
