[Bug binutils/29532] /usr/lib/debug/usr/lib/crti.o.debug: file format not recognized
https://sourceware.org/bugzilla/show_bug.cgi?id=29532 Nick Clifton changed: What|Removed |Added Resolution|--- |INVALID CC||nickc at redhat dot com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Nick Clifton --- Hi Alex, Unfortunately the crti.o.debug file is corrupt. This is why objdump is reporting that the file format is not recognized. The issue is that the .text.__x86.get_pc_thunk.bx section has the GROUP section flag set, but the .group section does not contain any information about it. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/29494] Trailing jump table leads to "Error: unaligned opcodes detected in executable segment" on ARM thumb
https://sourceware.org/bugzilla/show_bug.cgi?id=29494 --- Comment #9 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6f4eb56ec7d986030ea4f81f3d9f05180964bbc1 commit 6f4eb56ec7d986030ea4f81f3d9f05180964bbc1 Author: Nick Clifton Date: Tue Aug 30 13:46:11 2022 +0100 Add a testcase for PR 29494. PR 29494 * testsuite/gas/arm/pr29494.s: New test source file. * testsuite/gas/arm/pr29494.d: New test driver. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/29494] Trailing jump table leads to "Error: unaligned opcodes detected in executable segment" on ARM thumb
https://sourceware.org/bugzilla/show_bug.cgi?id=29494 Nick Clifton changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Nick Clifton --- Test case added. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang
https://sourceware.org/bugzilla/show_bug.cgi?id=29529 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #2 from Nick Clifton --- Created attachment 14304 --> https://sourceware.org/bugzilla/attachment.cgi?id=14304&action=edit Proposed Patch -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang
https://sourceware.org/bugzilla/show_bug.cgi?id=29529 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=37833b966576c5d25e797ea3b6c33d0459a71892 commit 37833b966576c5d25e797ea3b6c33d0459a71892 Author: Nick Clifton Date: Tue Aug 30 16:01:20 2022 +0100 BFD library: Use entry 0 in directory and filename tables of DWARF-5 debug info. PR 29529 * dwarf2.c (struct line_info_table): Add new field: use_dir_and_file_0. (concat_filename): Use new field to help select the correct table slot. (read_formatted_entries): Do not skip entry 0. (decode_line_info): Set new field depending upon the version of DWARF being parsed. Initialise filename based upon the setting of the new field. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang
https://sourceware.org/bugzilla/show_bug.cgi?id=29529 Nick Clifton changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Nick Clifton --- Hi Nick, Thanks for reporting this problem. You are correct - there was an implicit assumption in the DWARF decoding logic in the BFD library that dir0 and file0 were unused. I have now checked in a patch to correct this. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29529] [objdump] -l flag can't parse -gdwarf-5 file name info from clang
https://sourceware.org/bugzilla/show_bug.cgi?id=29529 --- Comment #5 from Nick Desaulniers --- Thank you Nick and David! -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/29540] New: ld ppc64: unneeded R_PPC64_NONE in .rela.dyn when linking Linux vdso
https://sourceware.org/bugzilla/show_bug.cgi?id=29540 Bug ID: 29540 Summary: ld ppc64: unneeded R_PPC64_NONE in .rela.dyn when linking Linux vdso Product: binutils Version: unspecified Status: NEW Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: i at maskray dot me Target Milestone: --- This should be reproducible with many Linux versions, but I have just checked some recent commits, e.g. dcf8e5633e2e69ad60b730ab5905608b756a032f today % git remote -v | grep origin origin https://github.com/torvalds/linux (fetch) origin https://github.com/torvalds/linux (push) % make O=/tmp/linux/ppc64le ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- -j60 defconfig all % readelf -Wr /tmp/linux/ppc64le/arch/powerpc/kernel/vdso/vdso64.so.dbg Relocation section '.rela.dyn' at offset 0x14f0 contains 4 entries: Offset Info Type Symbol's Value Symbol's Name + Addend R_PPC64_NONE 0 R_PPC64_NONE 0 R_PPC64_NONE 0 R_PPC64_NONE 0 The linker script is innocent. I don't reproduce the problem with other ports (though I know that the riscv port produces R_RISCV_NONE in certain scenarios) make O=/tmp/linux/x86_64 -j60 defconfig all && readelf -Wr /tmp/linux/x86_64/arch/x86/entry/vdso/vdso64.so make O=/tmp/linux/aarch64 ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- LLVM=1 -j60 all && readelf -Wr /tmp/linux/aarch64/arch/arm64/kernel/vdso/vdso.so make O=/tmp/linux/riscv64 ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- -j60 defconfig all && readelf -Wr /tmp/linux/riscv64/arch/riscv/kernel/vdso/vdso.so make O=/tmp/linux/s390x ARCH=s390 CROSS_COMPILE=s390x-linux-gnu- -j60 defconfig all && readelf -Wr /tmp/linux/s390x/arch/s390/kernel/vdso64/vdso64.so -- You are receiving this mail because: You are on the CC list for the bug.
