https://sourceware.org/bugzilla/show_bug.cgi?id=30447
Bug ID: 30447
Summary: [2.41 Regression] failing binutils and ld tests on
linux
Product: binutils
Version: 2.41 (HEAD)
Status: NEW
Severity: normal
https://sourceware.org/bugzilla/show_bug.cgi?id=29861
Alan Modra changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=30444
--- Comment #8 from Sven ---
(In reply to Jose E. Marchesi from comment #7)
> While implementing this in GNU poke [1] I noticed that the base64 value
> encoded in ASCII after the // is mutilated, since in order to fit in six
> characters it is
https://sourceware.org/bugzilla/show_bug.cgi?id=30448
Bug ID: 30448
Summary: ld fails to make a valid DLL when used with gnatdll
Product: binutils
Version: 2.34
Status: UNCONFIRMED
Severity: normal
Priority: P2
C
https://sourceware.org/bugzilla/show_bug.cgi?id=30448
Nick Clifton changed:
What|Removed |Added
CC||nickc at redhat dot com
--- Comment #1
https://sourceware.org/bugzilla/show_bug.cgi?id=30448
--- Comment #2 from Tom Kacvinsky ---
Yes, --disable-reloc-section is a viable workaround. And it can be added to
the gnatdll option -largs (which is the option that allows you to specify
options to the linker).
I would have to check to see
https://sourceware.org/bugzilla/show_bug.cgi?id=29961
--- Comment #15 from Alan Modra ---
Created attachment 14881
--> https://sourceware.org/bugzilla/attachment.cgi?id=14881&action=edit
A more elegant patch
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=29961
Alan Modra changed:
What|Removed |Added
Last reconfirmed||2023-05-15
Ever confirmed|0
https://sourceware.org/bugzilla/show_bug.cgi?id=29983
--- Comment #4 from Alan Modra ---
Can this bug be closed as fixed?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30421
--- Comment #5 from Luca Bacci ---
Ah, true! I have now sent an email:
https://sourceware.org/pipermail/binutils/2023-May/127440.html
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30448
--- Comment #3 from Tom Kacvinsky ---
Have a different take on this issue now. I was able to get 2.34 working. I
had to modify pep.em to get it to build on MSYS2 + MinGW-w64.
The commit that was partially reverted was 1ff6de031241. In that
https://sourceware.org/bugzilla/show_bug.cgi?id=30448
--- Comment #4 from Tom Kacvinsky ---
Created attachment 14882
--> https://sourceware.org/bugzilla/attachment.cgi?id=14882&action=edit
pep.em patch
Attached is the patch for pep.em that fixed the problem in binutils 2.34
--
You are receiv
https://sourceware.org/bugzilla/show_bug.cgi?id=30444
--- Comment #9 from Jose E. Marchesi ---
Sven, could you please provide:
1) A test.S compiled from test.c. I have a x86_64-w64-mingw binutils built but
not a suitable cross GCC. I will then derive testcases for binutils starting
from that f
https://sourceware.org/bugzilla/show_bug.cgi?id=29822
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=29822
--- Comment #2 from Jan Engelhardt ---
But only on x86_64 and only specific CPU models, is it not? This is a i386
object file.
--
You are receiving this mail because:
You are on the CC list for the bug.
Updates:
Labels: Deadline-Approaching
Comment #2 on issue 56154 by sheriffbot: binutils:fuzz_objcopy: Timeout in
fuzz_objcopy
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56154#c2
This bug is approaching its deadline for being fixed, and will be automatically
derestricted withi
Updates:
Labels: -deadline-approaching -restrict-view-commit Deadline-Exceeded
Comment #3 on issue 55955 by sheriffbot: binutils:fuzz_strings: Out-of-memory
in fuzz_strings
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55955#c3
This bug has exceeded our disclosure deadline. It ha
https://sourceware.org/bugzilla/show_bug.cgi?id=30444
--- Comment #10 from Sven ---
Created attachment 14883
--> https://sourceware.org/bugzilla/attachment.cgi?id=14883&action=edit
assembly file generated from test.c with x86_64-w64-mingw32-gcc
(In reply to Jose E. Marchesi from comment #9)
>
https://sourceware.org/bugzilla/show_bug.cgi?id=29822
--- Comment #3 from H.J. Lu ---
(In reply to Jan Engelhardt from comment #2)
> But only on x86_64 and only specific CPU models, is it not? This is a i386
> object file.
It is for both 32-bit and 64-bit.
--
You are receiving this mail becaus
https://sourceware.org/bugzilla/show_bug.cgi?id=30444
--- Comment #11 from Jose E. Marchesi ---
Oh sorry, I overlooked llvm-test.o and test.o. Yes these are in the 7z
archive. Thanks.
Thanks for the .s file. I believe I have now everything I need.
--
You are receiving this mail because:
You
https://sourceware.org/bugzilla/show_bug.cgi?id=30409
--- Comment #5 from Alan Modra ---
(In reply to Daniel Starke from comment #4)
> If you mean running the ar command on the console rather than letting
> makefile perform this task: yes, same result.
Yes, that was what I meant.
> Regarding th
https://sourceware.org/bugzilla/show_bug.cgi?id=30448
--- Comment #5 from Tom Kacvinsky ---
I've conflated things. The issues of building binutils 2.34 and 2.35 on
MinGW-w64 is a separate issue (perhaps an issue the MInGW-w64 folks know about
and could help solve my build problems without hacks)
https://sourceware.org/bugzilla/show_bug.cgi?id=30449
Bug ID: 30449
Summary: gas riscv: support pseudo-instruction "lga"
Product: binutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component:
https://sourceware.org/bugzilla/show_bug.cgi?id=30449
Fangrui Song changed:
What|Removed |Added
Target||riscv*-*-*
--
You are receiving this
24 matches
Mail list logo
