https://sourceware.org/bugzilla/show_bug.cgi?id=30006
--- Comment #16 from Vladimir Mezentsev
---
The build is OK when I configure with -fuse-ld=bfd.
Is it a known problem with ld.gold ?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30006
Alan Modra changed:
What|Removed |Added
Summary|Failure to build|Failure to build
|binu
https://sourceware.org/bugzilla/show_bug.cgi?id=30006
--- Comment #15 from Alan Modra ---
(In reply to Vladimir Mezentsev from comment #14)
> % gcc -m32 test.c -Wl,--version-script -Wl,map.txt
> /usr/local/bin/ld: warning: using 'GLIBC_2.0' as version for 'dlopen' which
> is also named in version
https://sourceware.org/bugzilla/show_bug.cgi?id=30006
--- Comment #14 from Vladimir Mezentsev
---
I installed Ubuntu and reproduced this problem in Docker.
This small test demonstrates the build problem:
% cat test.c
void *dlopen (const char *pathname, int mode)
{ return (void *) 0; }
__att
Updates:
Labels: -restrict-view-commit
Comment #3 on issue 55045 by sheriffbot: binutils:fuzz_as: Heap-use-after-free
in subseg_set_rest
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55045#c3
This bug has been fixed. It has been opened to the public.
- Your friendly Sheriffbot
Updates:
Labels: -restrict-view-commit
Comment #3 on issue 55491 by sheriffbot: binutils:fuzz_as: Stack-overflow in
as_abort
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55491#c3
This bug has been fixed. It has been opened to the public.
- Your friendly Sheriffbot
--
You rece
With assembly .S files or inline, the following syntax quietly produces the
wrong instruction
VLD1.16 {d2[]-d3[]}, [r3]!
assembles to:
vld1.16 {d2-d3}, [r3]!
The work around is to use , not -
VLD1.16 {d2[],d3[]}, [r3]!
The error is subtle, since the code will build and run and the
https://sourceware.org/bugzilla/show_bug.cgi?id=30069
Nick Clifton changed:
What|Removed |Added
CC||nickc at redhat dot com
--- Comment #1
https://sourceware.org/bugzilla/show_bug.cgi?id=30043
--- Comment #7 from Martin Liska ---
Thank you for the fix, looks fine now.
--
You are receiving this mail because:
You are on the CC list for the bug.
