[Bug binutils/27916] New: RISC-V: Porting ARM/AARCH64 mapping symbols to riscv.
https://sourceware.org/bugzilla/show_bug.cgi?id=27916 Bug ID: 27916 Summary: RISC-V: Porting ARM/AARCH64 mapping symbols to riscv. Product: binutils Version: unspecified Status: NEW Severity: enhancement Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: nelsonc1225 at sourceware dot org Target Milestone: --- -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/27916] RISC-V: Porting ARM/AARCH64 mapping symbols to riscv.
https://sourceware.org/bugzilla/show_bug.cgi?id=27916 Nelson Chu changed: What|Removed |Added Assignee|unassigned at sourceware dot org |nelsonc1225 at sourceware dot org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/27916] RISC-V: Porting ARM/AARCH64 mapping symbols to riscv.
https://sourceware.org/bugzilla/show_bug.cgi?id=27916 Nelson Chu changed: What|Removed |Added Target||riscv*-*-* -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/27906] doc for x86 incorrectly says that movsb is an alias for movsbq
https://sourceware.org/bugzilla/show_bug.cgi?id=27906 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by H.J. Lu : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3f335b75d8219d213f225d98b8879c303fdd73a3 commit 3f335b75d8219d213f225d98b8879c303fdd73a3 Author: Sebastien Villemot Date: Wed May 26 05:53:23 2021 -0700 i386: Replace movsb with movsxb PR gas/27906 * doc/c-i386.texi: Replace movsb with movsxb as an alias for movsbq. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/27906] doc for x86 incorrectly says that movsb is an alias for movsbq
https://sourceware.org/bugzilla/show_bug.cgi?id=27906 H.J. Lu changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Target Milestone|--- |2.37 --- Comment #2 from H.J. Lu --- Fixed. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/27833] ld-plugin/pr24406-1.c fails with GCC cross-toolchain for arm-none-eabi
https://sourceware.org/bugzilla/show_bug.cgi?id=27833 --- Comment #5 from Dimitar Dimitrov --- Yes, same problem occurs for all 3 newlib targets. As far as I'm aware, they all support LTO. Unfortunately I don't have setup to cross-compile for glibs, since it requires either a virtual machine or native ARM computer. I suspect that this is somehow related to PR 26358 . Perhaps the non-lto "read" from libc and lto "__wrap_read", coupled with different views for "undefined symbol" is causing this issue. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/27905] qemu: ./src/hw/megasas.c:168:(.text.megasas_process_op+0x3d): relocation
https://sourceware.org/bugzilla/show_bug.cgi?id=27905 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by H.J. Lu : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=50c95a739c91ae70cf8481936611aa1f5397a384 commit 50c95a739c91ae70cf8481936611aa1f5397a384 Author: H.J. Lu Date: Wed May 26 12:13:13 2021 -0700 x86: Propery check PC16 reloc overflow in 16-bit mode instructions commit a7664973b24a242cd9ea17deb5eaf503065fc0bd Author: Jan Beulich Date: Mon Apr 26 10:41:35 2021 +0200 x86: correct overflow checking for 16-bit PC-relative relocs caused linker failure when building 16-bit program in a 32-bit ELF container. Update GNU_PROPERTY_X86_FEATURE_2_USED with #define GNU_PROPERTY_X86_FEATURE_2_CODE16 (1U << 12) to indicate that 16-bit mode instructions are used in the input object: https://groups.google.com/g/x86-64-abi/c/UvvXWeHIGMA to indicate that 16-bit mode instructions are used in the object to allow linker to properly perform relocation overflow check for 16-bit PC-relative relocations in 16-bit mode instructions. 1. Update x86 assembler to always generate the GNU property note with GNU_PROPERTY_X86_FEATURE_2_CODE16 for .code16 in ELF object. 2. Update i386 and x86-64 linkers to use 16-bit PC16 relocations if input object is marked with GNU_PROPERTY_X86_FEATURE_2_CODE16. bfd/ PR ld/27905 * elf32-i386.c: Include "libiberty.h". (elf_howto_table): Add 16-bit R_386_PC16 entry. (elf_i386_rtype_to_howto): Add a BFD argument. Use 16-bit R_386_PC16 if input has 16-bit mode instructions. (elf_i386_info_to_howto_rel): Update elf_i386_rtype_to_howto call. (elf_i386_tls_transition): Likewise. (elf_i386_relocate_section): Likewise. * elf64-x86-64.c (x86_64_elf_howto_table): Add 16-bit R_X86_64_PC16 entry. (elf_x86_64_rtype_to_howto): Use 16-bit R_X86_64_PC16 if input has 16-bit mode instructions. * elfxx-x86.c (_bfd_x86_elf_parse_gnu_properties): Set elf_x86_has_code16 if relocatable input is marked with GNU_PROPERTY_X86_FEATURE_2_CODE16. * elfxx-x86.h (elf_x86_obj_tdata): Add has_code16. (elf_x86_has_code16): New. binutils/ PR ld/27905 * readelf.c (decode_x86_feature_2): Support GNU_PROPERTY_X86_FEATURE_2_CODE16. gas/ PR ld/27905 * config/tc-i386.c (set_code_flag): Update x86_feature_2_used with GNU_PROPERTY_X86_FEATURE_2_CODE16 for .code16 in ELF object. (set_16bit_gcc_code_flag): Likewise. (x86_cleanup): Always generate the GNU property note if x86_feature_2_used isn't 0. * testsuite/gas/i386/code16-2.d: New file. * testsuite/gas/i386/code16-2.s: Likewise. * testsuite/gas/i386/x86-64-code16-2.d: Likewise. * testsuite/gas/i386/i386.exp: Run code16-2 and x86-64-code16-2. include/ PR ld/27905 * elf/common.h (GNU_PROPERTY_X86_FEATURE_2_CODE16): New. ld/ PR ld/27905 * testsuite/ld-i386/code16.d: New file. * testsuite/ld-i386/code16.t: Likewise. * testsuite/ld-x86-64/code16.d: Likewise. * testsuite/ld-x86-64/code16.t: Likewise. * testsuite/ld-i386/i386.exp: Run code16. * testsuite/ld-x86-64/x86-64.exp: Likewise. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/27905] qemu: ./src/hw/megasas.c:168:(.text.megasas_process_op+0x3d): relocation
https://sourceware.org/bugzilla/show_bug.cgi?id=27905 H.J. Lu changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Target Milestone|--- |2.37 --- Comment #7 from H.J. Lu --- Fixed for 2.37. -- You are receiving this mail because: You are on the CC list for the bug.
