[Bug gas/26513] 629310abec8811510177101f3c7992dfd4be24dd breaks assembling PowerPC Linux kernels

2020-08-21 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26513

Alan Modra  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
   Last reconfirmed||2020-08-21

--- Comment #1 from Alan Modra  ---
Confirmed.  str_hash_insert replaces existing entries, the old hash_insert did
not.  That's a problem when there are multiple entries for an instruction in
the powerpc_opcodes table.  For example, the proper power4 dcbt is added to the
hash table but -many results in it being replaced with the ppc dcbt.

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


[Bug binutils/26518] New: [2.35 regression] error: could not find variable specification

2020-08-21 Thread xantares09 at hotmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26518

Bug ID: 26518
   Summary: [2.35 regression] error: could not find variable
specification
   Product: binutils
   Version: 2.35
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: xantares09 at hotmail dot com
  Target Milestone: ---

I have a problem compiling mesa using with binutils 2.35 in archlinux
for mingw i686 target with LLVM enabled + LTO:


if I disable LTO (meson -Db_lto=false) or use binutils 2.34 the problem goes
away
if I use the x86_64 target the problem goes away
I tried today's binutils master: the bug is still there

I found a somewhat similar report at debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965247


Here is the error:


[947/947] Linking target src/gallium/targets/libgl-gdi/opengl32.dll
FAILED: src/gallium/targets/libgl-gdi/opengl32.dll 
i686-w64-mingw32-g++  -o src/gallium/targets/libgl-gdi/opengl32.dll
src/gallium/targets/libgl-gdi/opengl32.dll.p/libgl_gdi.c.obj -flto
-Wl,--allow-shlib-undefined -Wl,-O1 -shared
../src/gallium/targets/libgl-gdi/../../state_trackers/wgl/opengl32.mingw.def
-Wl,--start-group -Wl,--out-implib=src/gallium/targets/libgl-gdi/opengl32.dll.a
-Wl,--whole-archive src/gallium/state_trackers/wgl/libwgl.a
-Wl,--no-whole-archive -Wl,--nxcompat -Wl,--dynamicbase -static-libgcc
-static-libstdc++ -Wl,-O1,--sort-common,--as-needed -fstack-protector
src/gallium/auxiliary/libgallium.a src/compiler/nir/libnir.a
src/compiler/libcompiler.a src/util/libmesa_util.a
src/util/format/libmesa_format.a src/compiler/glsl/libglsl.a
src/compiler/glsl/glcpp/libglcpp.a src/mesa/libmesa_gallium.a
src/mesa/libmesa_common.a src/mesa/libmesa_sse41.a
src/gallium/winsys/sw/gdi/libwsgdi.a src/mapi/glapi/libglapi_static.a
src/gallium/drivers/llvmpipe/libllvmpipe.a
src/gallium/drivers/softpipe/libsoftpipe.a -lws2_32
/usr/i686-w64-mingw32/lib/libz.dll.a -pthread -lm
/usr/i686-w64-mingw32/lib/libLLVMAggressiveInstCombine.dll.a
/usr/i686-w64-mingw32/lib/libLLVMAnalysis.dll.a
/usr/i686-w64-mingw32/lib/libLLVMAsmParser.dll.a
/usr/i686-w64-mingw32/lib/libLLVMAsmPrinter.dll.a
/usr/i686-w64-mingw32/lib/libLLVMBinaryFormat.dll.a
/usr/i686-w64-mingw32/lib/libLLVMBitReader.dll.a
/usr/i686-w64-mingw32/lib/libLLVMBitWriter.dll.a
/usr/i686-w64-mingw32/lib/libLLVMBitstreamReader.dll.a
/usr/i686-w64-mingw32/lib/libLLVMCFGuard.dll.a
/usr/i686-w64-mingw32/lib/libLLVMCodeGen.dll.a
/usr/i686-w64-mingw32/lib/libLLVMCore.dll.a
/usr/i686-w64-mingw32/lib/libLLVMCoroutines.dll.a
/usr/i686-w64-mingw32/lib/libLLVMDebugInfoCodeView.dll.a
/usr/i686-w64-mingw32/lib/libLLVMDebugInfoDWARF.dll.a
/usr/i686-w64-mingw32/lib/libLLVMDebugInfoMSF.dll.a
/usr/i686-w64-mingw32/lib/libLLVMDemangle.dll.a
/usr/i686-w64-mingw32/lib/libLLVMExecutionEngine.dll.a
/usr/i686-w64-mingw32/lib/libLLVMGlobalISel.dll.a
/usr/i686-w64-mingw32/lib/libLLVMIRReader.dll.a
/usr/i686-w64-mingw32/lib/libLLVMInstCombine.dll.a
/usr/i686-w64-mingw32/lib/libLLVMInstrumentation.dll.a
/usr/i686-w64-mingw32/lib/libLLVMLinker.dll.a
/usr/i686-w64-mingw32/lib/libLLVMMC.dll.a
/usr/i686-w64-mingw32/lib/libLLVMMCDisassembler.dll.a
/usr/i686-w64-mingw32/lib/libLLVMMCJIT.dll.a
/usr/i686-w64-mingw32/lib/libLLVMMCParser.dll.a
/usr/i686-w64-mingw32/lib/libLLVMObject.dll.a
/usr/i686-w64-mingw32/lib/libLLVMProfileData.dll.a
/usr/i686-w64-mingw32/lib/libLLVMRemarks.dll.a
/usr/i686-w64-mingw32/lib/libLLVMRuntimeDyld.dll.a
/usr/i686-w64-mingw32/lib/libLLVMScalarOpts.dll.a
/usr/i686-w64-mingw32/lib/libLLVMSelectionDAG.dll.a
/usr/i686-w64-mingw32/lib/libLLVMSupport.dll.a
/usr/i686-w64-mingw32/lib/libLLVMTarget.dll.a
/usr/i686-w64-mingw32/lib/libLLVMTextAPI.dll.a
/usr/i686-w64-mingw32/lib/libLLVMTransformUtils.dll.a
/usr/i686-w64-mingw32/lib/libLLVMVectorize.dll.a
/usr/i686-w64-mingw32/lib/libLLVMX86AsmParser.dll.a
/usr/i686-w64-mingw32/lib/libLLVMX86CodeGen.dll.a
/usr/i686-w64-mingw32/lib/libLLVMX86Desc.dll.a
/usr/i686-w64-mingw32/lib/libLLVMX86Disassembler.dll.a
/usr/i686-w64-mingw32/lib/libLLVMX86Info.dll.a
/usr/i686-w64-mingw32/lib/libLLVMX86Utils.dll.a
/usr/i686-w64-mingw32/lib/libLLVMipo.dll.a -ldl -lkernel32 -luser32 -lgdi32
-lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32
-Wl,--end-group
/usr/lib/gcc/i686-w64-mingw32/10.2.0/../../../../i686-w64-mingw32/bin/ld:
/usr/lib/gcc/i686-w64-mingw32/10.2.0/../../../../i686-w64-mingw32/bin/ld: DWARF
error: could not find variable specification at offset 377
/usr/lib/gcc/i686-w64-mingw32/10.2.0/../../../../i686-w64-mingw32/lib/../lib/libstdc++.a(string-inst.o):
in function
`ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag':
/build/mingw-w64-gcc/src/build-i686-w64-mingw32/i686-w64-mingw32/libstdc++-v3/include/bits/basic_string.tcc:206:
multiple definition of `void std::__cxx11::basic_string, std::allocator >::_M_

[Bug binutils/26414] ASAN error: in get_sym_code_type opcodes/aarch64-dis.c:3333

2020-08-21 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26414

Nick Clifton  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||nickc at redhat dot com
 Resolution|--- |FIXED

--- Comment #1 from Nick Clifton  ---
Hi Martin,

  This should be fixed by commit ccf61261eb.

Cheers
  Nick

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


[Bug binutils/26413] UBSAN error: elfnn-aarch64.c:3928:7:

2020-08-21 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26413

Nick Clifton  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||nickc at redhat dot com
 Resolution|--- |FIXED

--- Comment #1 from Nick Clifton  ---
Hi Martin,

  This should be fixed by commit ccf61261eb.

Cheers
  Nick

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


[Bug binutils/26520] New: "objdump: DWARF error: could not find variable specification at offset ..." when generating assembly listing of .elf file containing symbols from libstdc++.a

2020-08-21 Thread freddie_chopin at op dot pl
https://sourceware.org/bugzilla/show_bug.cgi?id=26520

Bug ID: 26520
   Summary: "objdump: DWARF error: could not find variable
specification at offset ..." when generating assembly
listing of .elf file containing symbols from
libstdc++.a
   Product: binutils
   Version: 2.35
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: freddie_chopin at op dot pl
  Target Milestone: ---

Created attachment 12787
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12787&action=edit
Problematic .elf file

I have multiple embedded C++ projects that - as part of the compilation process
- produce also assembly listing with command similar to this one:

$ arm-none-eabi-objdump -S --demangle distortosTest.elf > distortosTest.lss

This worked flawlessly up to (and including) previous release of binutils. In
2.35 something changed. The assembly listing is still generated and it seems to
be correct (I did not check it very thoroughly), the command ends with no fatal
errors (it returns "0" to the shell), however I see multiple errors like these:

arm-none-eabi-objdump: DWARF error: could not find variable specification at
offset 2f9
arm-none-eabi-objdump: DWARF error: could not find variable specification at
offset 305
arm-none-eabi-objdump: DWARF error: could not find variable specification at
offset 311
...

If I take the .elf file produced by the "new" toolchain (it also includes GCC
10.2) and do the command above but with objdump from the "old" toolchain
(binutils 2.34), then there is no error. In a reversed scenario (.elf produced
by "old" toolchain, passed to "new" objdump) I see 10x more errors like the
ones above.

I attach the problematic .elf file for ARM Cortex-M4 which produces such
errors.

After further inspection it turns out that none of "my" .o object files or .a
archives produce such error. When examining toolchain libraries, such errors
are produced by only ONE library there - libstdc++.a.

arm-none-eabi-objdump -S --demangle libstdc++.a > libstdc++.lss
arm-none-eabi-objdump: DWARF error: could not find variable specification at
offset 76c
arm-none-eabi-objdump: DWARF error: could not find variable specification at
offset 1733
arm-none-eabi-objdump: DWARF error: could not find variable specification at
offset 1740
...
(a lot...)

No other toolchain libraries or toolchain object files produce such error, only
libstdc++.a.

At this moment I cannot confirm whether or not this is arm-none-eabi specific
or not, as Arch Linux still has binutils 2.34 in the repos.

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


[Bug binutils/26520] "objdump: DWARF error: could not find variable specification at offset ..." when generating assembly listing of .elf file containing symbols from libstdc++.a

2020-08-21 Thread freddie_chopin at op dot pl
https://sourceware.org/bugzilla/show_bug.cgi?id=26520

--- Comment #1 from Freddie Chopin  ---
Created attachment 12788
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12788&action=edit
Problematic libstdc++.a file

I also attach the .a archive which generates such errors (to be specific:
arm-none-eabi/lib/thumb/v7e-m/nofp/libstdc++.a, however every libstdc++.a
variant from the toolchain produces these errors).

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


[Bug binutils/26193] compile and link error on macos

2020-08-21 Thread noloader at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26193

Jeffrey Walton  changed:

   What|Removed |Added

 CC||noloader at gmail dot com

--- Comment #2 from Jeffrey Walton  ---
Also see https://sourceware.org/bugzilla/show_bug.cgi?id=26191.

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


[Bug ld/26391] Question regarding duplicate symbols

2020-08-21 Thread kaccardi at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26391

--- Comment #2 from Kristen Carlson Accardi  ---
This works for me! Thanks!

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


[Bug binutils/26521] New: A Floating point exception in elf.c:12840:31

2020-08-21 Thread seviezhou at 163 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26521

Bug ID: 26521
   Summary: A Floating point exception in elf.c:12840:31
   Product: binutils
   Version: 2.36 (HEAD)
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: seviezhou at 163 dot com
  Target Milestone: ---

Created attachment 12789
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12789&action=edit
FPE-_bfd_elf_write_secondary_reloc_section-elf-12840

## System info

Ubuntu x86_64, clang 6.0, binutils (2.36
d1ce973eb377f19240005665258ce1d89bd064b5)

## Configure

CFLAGS="-g -fsanitize=address" LDFLAGS="-fsanitize=address" ./configure

## Command line

./binutils/strip-new -s -g -S -d -w -x -X -v -o /dev/null @@

## AddressSanitizer output

```
AddressSanitizer:DEADLYSIGNAL
=
==14746==ERROR: AddressSanitizer: FPE on unknown address 0x0069c05c (pc
0x0069c05c bp 0x7ffde12578d0 sp 0x7ffde1257720 T0)
#0 0x69c05b in _bfd_elf_write_secondary_reloc_section
/home/seviezhou/binutils/bfd/elf.c:12840:31
#1 0x642b07 in bfd_elf64_write_relocs
/home/seviezhou/binutils/bfd/./elfcode.h:1002:8
#2 0x5d7bbc in bfd_map_over_sections
/home/seviezhou/binutils/bfd/section.c:1379:5
#3 0x6847f0 in _bfd_elf_write_object_contents
/home/seviezhou/binutils/bfd/elf.c:6657:3
#4 0x5cf909 in bfd_close /home/seviezhou/binutils/bfd/opncls.c:775:13
#5 0x51e9d4 in copy_file
/home/seviezhou/binutils/binutils/objcopy.c:3846:51
#6 0x5143d8 in strip_main
/home/seviezhou/binutils/binutils/objcopy.c:4826:7
#7 0x5143d8 in main /home/seviezhou/binutils/binutils/objcopy.c:6024
#8 0x7fa7b3be6b96 in __libc_start_main
/build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310
#9 0x41ac99 in _start
(/home/seviezhou/binutils/binutils/strip-new+0x41ac99)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: FPE /home/seviezhou/binutils/bfd/elf.c:12840:31 in
_bfd_elf_write_secondary_reloc_section
==14746==ABORTING
```

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