[Bug ld/31133] [riscv64] -z now breaks glibc testsuite

2023-12-11 Thread aurelien at aurel32 dot net
https://sourceware.org/bugzilla/show_bug.cgi?id=31133

Aurelien Jarno  changed:

   What|Removed |Added

 CC||aurelien at aurel32 dot net,
   ||sch...@linux-m68k.org

--- Comment #2 from Aurelien Jarno  ---
A bisect pointed me to the following commit:

7345d05aafde53a48d5a587a6d9c1778db78e0f3 is the first bad commit
commit 7345d05aafde53a48d5a587a6d9c1778db78e0f3
Author: Andreas Schwab 
Date:   Thu Sep 21 16:49:41 2023 +0200

RISC-V: Protect .got with relro

Move .got before .data so that it can be protected with -zrelro.  Also
separate .got.plt from .got if -znow is not in effect; the first two words
of .got.plt are placed within the relro region.

ld:
PR ld/30877
* emulparams/elf32lriscv-defs.sh (DATA_GOT, SEPARATE_GOTPLT):
Define.
* emulparams/elf64lriscv-defs.sh (SEPARATE_GOTPLT): Define.
* testsuite/ld-elf/binutils.exp (binutils_test): Remove riscv*-*-*
from relro_got expression.

 ld/emulparams/elf32lriscv-defs.sh | 4 
 ld/emulparams/elf64lriscv-defs.sh | 1 +
 ld/testsuite/ld-elf/binutils.exp  | 1 -
 3 files changed, 5 insertions(+), 1 deletion(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/31120] ld-scripts/fill2 fails when bfd_vma is 32 bits

2023-12-11 Thread danglin at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=31120

John David Anglin  changed:

   What|Removed |Added

 CC||danglin at gcc dot gnu.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Issue 62986 in oss-fuzz: binutils:fuzz_nm: Heap-buffer-overflow in bfd_getl16

2023-12-11 Thread sheriffbot via monorail
Updates:
Labels: -restrict-view-commit

Comment #3 on issue 62986 by sheriffbot: binutils:fuzz_nm: Heap-buffer-overflow 
in bfd_getl16
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62986#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 gas/31115] [ARM] The minimalistic DWARF DIE for function has wrong address in Thumb mode

2023-12-11 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31115

--- Comment #5 from Nick Clifton  ---
(In reply to Thiago Jung Bauermann from comment #4)
Hi Thiago,

> $ gcc -g -o pr25124 ~/src/binutils-gdb/gdb/testsuite/gdb.arch/pr25124.S
> $ gdb pr25124
> Reading symbols from pr25124...
> (gdb) x/i main
>0x103e5 :  bx  pc
> (gdb) x/i main+8
>0x103ed :vrhadd.u16  d14, d14, d31
> (gdb) quit
> 
> Interestingly, as can be seen above "x/i main" actually works fine.

Except that the address is displayed with the bottom bit set, which
might be confusing the readers.  Maybe.

> it's "x/i main+8" that breaks. This is a detail that I just noticed.
> 
> There's another thing I just discovered : I can reproduce GDB's bad
> behavior on an ELF executable (produced by GCC from the .S file), but
> not on a .o file produced directly by gas:

Or one that is produced by using gcc to invoke just gas.  ie compiling with
"-c".

> $ as -g -o pr25124.o ~/src/binutils-gdb/gdb/testsuite/gdb.arch/pr25124.S
> $ gdb pr25124.o
> Reading symbols from pr25124.o...
> (gdb) x/i main
>0x0 :  bx  pc
> (gdb) x/i main+8
>0x8 :bx  lr
> (gdb) quit

Interestingly my patch makes things even worse for the fully linked executable:

  $ gdb pr25124.with-nicks-patch 
  GNU gdb (GDB) Fedora Linux 13.2-6.fc38
  [...]
  (gdb) x/i main
 0x8243 <_start+158>:   movsr0, r0
  (gdb) x/i main+8
 0x824b :   b.n 0x898e

So please consider it withdrawn.


> Both the executable and the .o file have the LSB bit set in main's
> DW_AT_low_pc:

> So for some reason GDB is fine with an object file containing the wrong
> DW_AT_low_pc in main's DIE, but not when it's with a "full blown"
> executable.

My guess - totally unproven - is that GDB has special code to mask thumb
addresses for object files, but for some reason this code is not applied
to linked executables.

I do wonder if this is something that GDB has already partially fixed, and
maybe this fix needs to be extended...

Anyway I am investigating gas some more...

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/31134] 2.41: build fails with --disable-warn-execstack

2023-12-11 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31134

Nick Clifton  changed:

   What|Removed |Added

 CC||nickc at redhat dot com

--- Comment #3 from Nick Clifton  ---
Hi Kloczek,

  Sorry - I am unable to reproduce this problem.  Can you show the entire
configure command line that you used ?

Cheers
  Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.