https://sourceware.org/bugzilla/show_bug.cgi?id=27671
Markus Böck changed:
What|Removed |Added
CC||markus.boeck02 at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=27456
--- Comment #5 from Markus Böck ---
That's less than optimal to say the least. Is it possible to tell it which ar
to test? ar.exe exists in /binutils along the other files but
instead of ar.exe it tries to invoke just ar. I tried setting AR to
https://sourceware.org/bugzilla/show_bug.cgi?id=27456
--- Comment #3 from Markus Böck ---
Applying the patch successfully compiled and linked. I then ran make check and
compiled a rather large project of mine that worked without issues.
The failures in the test seem to largely be unrecognized co
https://sourceware.org/bugzilla/show_bug.cgi?id=27456
--- Comment #2 from Markus Böck ---
Created attachment 13256
--> https://sourceware.org/bugzilla/attachment.cgi?id=13256&action=edit
Test results
--
You are receiving this mail because:
You are on the CC list for the bug.
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: markus.boeck02 at gmail dot com
Target Milestone: ---
Created attachment 13247
--> https://sourceware.org/bugzilla/attachment.cgi?id=13247&action=edit
config
https://sourceware.org/bugzilla/show_bug.cgi?id=27113
--- Comment #2 from Markus Böck ---
I don't think so. That PR and commit is concerned with versioning applied to
shared libraries. Here in this case the import library of libdep.dll, commonly
called libdep.dll.a, is installed as well. It's a f
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: markus.boeck02 at gmail dot com
Target Milestone: ---
Recent versions introduced libdep which on Windows is installed in
root/bfd-plugins/libdep.dll. Problem is that along with it libdep.dll.a is also
installed
https://sourceware.org/bugzilla/show_bug.cgi?id=26554
Markus Böck changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
: ld
Assignee: unassigned at sourceware dot org
Reporter: markus.boeck02 at gmail dot com
Target Milestone: ---
Current HEAD of the repository (42afa120eb180bce52c692939cd179e3c02160d9)
causes a segmentation fault when --out-implib is specified on the command line.
The simplest
https://sourceware.org/bugzilla/show_bug.cgi?id=26198
Markus Böck changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://sourceware.org/bugzilla/show_bug.cgi?id=26198
--- Comment #2 from Markus Böck ---
I posted a patch on the mailing list that should resolve this issue. The
problem was how comdat between a native object and a LTO object was handled.
When the LTO object was linked first and had a symbol in
: UNCONFIRMED
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: markus.boeck02 at gmail dot com
Target Milestone: ---
Given following C++ source code:
test.cpp:
#include
https://sourceware.org/bugzilla/show_bug.cgi?id=26103
--- Comment #12 from Markus Böck ---
Can confirm that the bug is fixed!
Thank you very much
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=26103
--- Comment #7 from Markus Böck ---
This sadly was more complicated than I thought as WSL 1 doesn't support
watchpoints but docker did the job.
I set the watchpoint on h->type for the weak symbol and it only gets set to
bfd_link_hash_undefine
https://sourceware.org/bugzilla/show_bug.cgi?id=26103
--- Comment #6 from Markus Böck ---
This sadly was more complicated than I thought as WSL 1 doesn't support
watchpoints but docker did the job.
I set the watchpoint on h->type for the weak symbol and it only gets set to
bfd_link_hash_undefine
https://sourceware.org/bugzilla/show_bug.cgi?id=26103
--- Comment #4 from Markus Böck ---
Using git bisect I managed to figure out which commit of GCC 9 has started
causing the issue. I am confused as to how or why it would do so however.
The first commit that causes this bug is: "PR libstdc++/86
https://sourceware.org/bugzilla/show_bug.cgi?id=26103
--- Comment #3 from Markus Böck ---
Created attachment 12620
--> https://sourceware.org/bugzilla/attachment.cgi?id=12620&action=edit
Symbols in ios.o of the compiler causing the assert in ld
--
You are receiving this mail because:
You are
https://sourceware.org/bugzilla/show_bug.cgi?id=26103
--- Comment #2 from Markus Böck ---
Created attachment 12619
--> https://sourceware.org/bugzilla/attachment.cgi?id=12619&action=edit
Symbols in ios.o of the working compiler
--
You are receiving this mail because:
You are on the CC list fo
: binutils
Assignee: unassigned at sourceware dot org
Reporter: markus.boeck02 at gmail dot com
Target Milestone: ---
When trying to compile gdb using the --enable-targets=all option I have
encountered following compilation failure inside of bfd:
/bin/bash ./libtool --tag=CC
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: markus.boeck02 at gmail dot com
Target Milestone: ---
Since a patch that has been included in GCC 9 using LTO with target
x86_64-mingw32 has been causing an assertion
20 matches
Mail list logo
