Issue 55922 in oss-fuzz: binutils:fuzz_objcopy: Out-of-memory in fuzz_objcopy
Updates: Labels: -restrict-view-commit Comment #3 on issue 55922 by sheriffbot: binutils:fuzz_objcopy: Out-of-memory in fuzz_objcopy https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55922#c3 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #30 from cqwrteur --- (In reply to Nick Clifton from comment #24) > Created attachment 14656 [details] > Proposed patch > > Hi, > > Oops - I forgot about section names containing the $ character. > > Please could you try out this revised patch and let me know if it works > properly this time. > > Cheers > Nick Hello. Could you fix it? Since the bug makes it impossible to use gcc on windows. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/30120] x87: fucomp assembled as fucom
https://sourceware.org/bugzilla/show_bug.cgi?id=30120 --- Comment #5 from Michael Matz --- (In reply to Michael Matz from comment #4) > commit 25a0d393c72 (with a little addition to a testcase to check for at > least this problem) FWIW, I've also checked all patterns touched by the initial patch now and also don't see a further problem. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/30120] x87: fucomp assembled as fucom
https://sourceware.org/bugzilla/show_bug.cgi?id=30120 Michael Matz changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from Michael Matz --- commit 25a0d393c72 (with a little addition to a testcase to check for at least this problem) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/30120] x87: fucomp assembled as fucom
https://sourceware.org/bugzilla/show_bug.cgi?id=30120
Jan Beulich changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3 from Jan Beulich ---
(In reply to Michael Matz from comment #2)
> Came in with bd7828084 "x86: use ModR/M for FPU insns with operands".
>
> The proper Reg field of ModRM for the popping variant of fucom is '5' not
> '4'.
> So this:
>
> --- a/opcodes/i386-opc.tbl
> +++ b/opcodes/i386-opc.tbl
> @@ -651,7 +651,7 @@ fcompp, 0xded9, FP, NoSuf, {}
> fucom, 0xdd/4, i387, Modrm|NoSuf, { FloatReg }
> // alias for fucom %st(1)
> fucom, 0xdde1, i387, NoSuf, {}
> -fucomp, 0xdd/4, i387, Modrm|NoSuf, { FloatReg }
> +fucomp, 0xdd/5, i387, Modrm|NoSuf, { FloatReg }
> // alias for fucomp %st(1)
> fucomp, 0xdde9, i387, NoSuf, {}
> fucompp, 0xdae9, i387, NoSuf, {}
Would you mind simply committing your change?
> (didn't check the other insns touched by the patch)
I've just gone through using a pattern I didn't use when composing the change,
and I didn't find any other similar issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug gas/30120] x87: fucomp assembled as fucom
https://sourceware.org/bugzilla/show_bug.cgi?id=30120 Michael Matz changed: What|Removed |Added Assignee|unassigned at sourceware dot org |jbeulich at suse dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/30120] x87: fucomp assembled as fucom
https://sourceware.org/bugzilla/show_bug.cgi?id=30120
--- Comment #2 from Michael Matz ---
Came in with bd7828084 "x86: use ModR/M for FPU insns with operands".
The proper Reg field of ModRM for the popping variant of fucom is '5' not '4'.
So this:
--- a/opcodes/i386-opc.tbl
+++ b/opcodes/i386-opc.tbl
@@ -651,7 +651,7 @@ fcompp, 0xded9, FP, NoSuf, {}
fucom, 0xdd/4, i387, Modrm|NoSuf, { FloatReg }
// alias for fucom %st(1)
fucom, 0xdde1, i387, NoSuf, {}
-fucomp, 0xdd/4, i387, Modrm|NoSuf, { FloatReg }
+fucomp, 0xdd/5, i387, Modrm|NoSuf, { FloatReg }
// alias for fucomp %st(1)
fucomp, 0xdde9, i387, NoSuf, {}
fucompp, 0xdae9, i387, NoSuf, {}
(didn't check the other insns touched by the patch)
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug gas/30120] x87: fucomp assembled as fucom
https://sourceware.org/bugzilla/show_bug.cgi?id=30120 --- Comment #1 from Michael Matz --- The problem exists in current master. 2.39 and 2.40 seem to be okay. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/30120] New: x87: fucomp assembled as fucom
https://sourceware.org/bugzilla/show_bug.cgi?id=30120
Bug ID: 30120
Summary: x87: fucomp assembled as fucom
Product: binutils
Version: 2.41 (HEAD)
Status: NEW
Severity: normal
Priority: P2
Component: gas
Assignee: unassigned at sourceware dot org
Reporter: matz at suse dot de
Target Milestone: ---
% cat asm.s
fucomp %st(1)
% ./gas/as-new asm.s && objdump -d a.out
...
<.text>:
0: dd e1 fucom %st(1)
It should be 'dd e9fucomp %st(1)'. This results in the x87 sometimes not
be popped and wrong results. (GCC generates fucom{i,}p sometimes, of course).
Possibly some other mnemonics are affected as well, where there are popping (or
twice-popping) and non-popping variants, but this is one that effectively made
glibc miscompiled (in the sqrt implementation that uses 'isless').
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug ld/30079] Mingw ld : linking against an import lib causes ld to abort() at compare_section in ldlang.c
https://sourceware.org/bugzilla/show_bug.cgi?id=30079 --- Comment #8 from Christoph Reiter --- Thanks! https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b7eab2a9d4f4e92692daf14b09fc95ca11b72e30 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30079] Mingw ld : linking against an import lib causes ld to abort() at compare_section in ldlang.c
https://sourceware.org/bugzilla/show_bug.cgi?id=30079 Michael Matz changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Michael Matz --- (In reply to Christoph Reiter from comment #6) > (In reply to Christoph Reiter from comment #5) > > I did that in https://github.com/msys2/MINGW-packages/pull/15540 now which > > fixed it for this example. Once it's in the repo I can ask the affected > > users to try again. > > All affected downstream users reported that it's working again for them. Thanks. After pondering I think it's the right thing to do, the input is sane and it's (of course) fine that sections are only sorted by filename and not otherwise, so that case needs dealing with. I've committed a patch for this. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/30119] New: error: static assertion failed due to requirement
https://sourceware.org/bugzilla/show_bug.cgi?id=30119
Bug ID: 30119
Summary: error: static assertion failed due to requirement
Product: binutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gold
Assignee: ccoutant at gmail dot com
Reporter: arshia.aghaei at gmail dot com
CC: ian at airs dot com
Target Milestone: ---
Hi, following the guide in https://llvm.org/docs/GoldPlugin.html
My OS is Arch-Linux 64-bit
I get the following errors:
```cpp
In file included from ../../gold/stringpool.cc:23:
In file included from ../../gold/gold.h:35:
In file included from ../../gold/system.h:68:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/unordered_set:46:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable.h:35:
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable_policy.h:1697:4:
error: static assertion failed due to requirement 'std::__is_invocable::Stringpool_eq &, const
gold::Stringpool_template::Hashkey &, const
gold::Stringpool_template::Hashkey &>{}': key equality predicate must be
invocable with two arguments of key type
static_assert(
```
```cpp
In file included from ../../gold/stringpool.cc:23:
In file included from ../../gold/gold.h:35:
In file included from ../../gold/system.h:68:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/unordered_set:46:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable.h:35:
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable_policy.h:1697:4:
error: static assertion failed due to requirement 'std::__is_invocable::Stringpool_eq &, const
gold::Stringpool_template::Hashkey &, const
gold::Stringpool_template::Hashkey &>{}': key equality predicate
must be invocable with two arguments of key type
static_assert(
```
```cpp
In file included from ../../gold/stringpool.cc:23:
In file included from ../../gold/gold.h:35:
In file included from ../../gold/system.h:68:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/unordered_set:46:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable.h:35:
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable_policy.h:1685:2:
error: static assertion failed due to requirement 'std::__is_invocable::Stringpool_eq &, const
gold::Stringpool_template::Hashkey &, const
gold::Stringpool_template::Hashkey &>{}': key equality predicate must be
invocable with two arguments of key type
static_assert(__is_invocable{},
```
```cpp
In file included from ../../gold/stringpool.cc:23:
In file included from ../../gold/gold.h:35:
In file included from ../../gold/system.h:68:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/unordered_set:46:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable.h:35:
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable_policy.h:1697:4:
error: static assertion failed due to requirement 'std::__is_invocable::Stringpool_eq &, const
gold::Stringpool_template::Hashkey &, const
gold::Stringpool_template::Hashkey &>{}': key equality
predicate must be invocable with two arguments of key type
static_assert(
```
```cpp
In file included from ../../gold/stringpool.cc:23:
In file included from ../../gold/gold.h:35:
In file included from ../../gold/system.h:68:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/unordered_set:46:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable.h:35:
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable_policy.h:1685:2:
error: static assertion failed due to requirement 'std::__is_invocable::Stringpool_eq &, const
gold::Stringpool_template::Hashkey &, const
gold::Stringpool_template::Hashkey &>{}': key equality
predicate must be invocable with two arguments of key type
static_assert(__is_invocable{},
```
```cpp
In file included from ../../gold/stringpool.cc:23:
In file included from ../../gold/gold.h:35:
In file included from ../../gold/system.h:68:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/unordered_set:46:
In file included from
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable.h:35:
/usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.1/../../../../include/c++/12.2.1/bits/hashtable_policy.h:1697:4:
error: static assertion failed due to requirement 'std
[Bug gas/30117] internal error in parse_register at tc-i386.c:13060
https://sourceware.org/bugzilla/show_bug.cgi?id=30117 Jan Beulich changed: What|Removed |Added Status|NEW |ASSIGNED -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/30117] internal error in parse_register at tc-i386.c:13060
https://sourceware.org/bugzilla/show_bug.cgi?id=30117 Jan Beulich changed: What|Removed |Added Assignee|unassigned at sourceware dot org |jbeulich at suse dot com --- Comment #1 from Jan Beulich --- I'll look into that. -- You are receiving this mail because: You are on the CC list for the bug.
