[Bug binutils/17615] aarch64: ld.bfd generates SHN_ABS instead of SHN_UNDEF
https://sourceware.org/bugzilla/show_bug.cgi?id=17615 --- Comment #1 from Marcus Shawcroft --- Please add a test case or reproducer. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/17615] aarch64: ld.bfd generates SHN_ABS instead of SHN_UNDEF
https://sourceware.org/bugzilla/show_bug.cgi?id=17615 Marcus Shawcroft changed: What|Removed |Added Target||aarch64-none-linux-gnu CC||marcus.shawcroft at gmail dot com Summary|arm64: ld.bfd generates |aarch64: ld.bfd generates |SHN_ABS instead of |SHN_ABS instead of |SHN_UNDEF |SHN_UNDEF -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/19188] [2.26 Regression] binutils assertion fail ../../bfd/elfnn-aarch64.c:4631
https://sourceware.org/bugzilla/show_bug.cgi?id=19188 Marcus Shawcroft changed: What|Removed |Added CC||marcus.shawcroft at gmail dot com --- Comment #4 from Marcus Shawcroft --- This regression is caused by: commit 3ebe65c0ff9f8f76c9971b1cc078273298f0c693 Author: Renlin Li Date: Fri Oct 2 17:48:31 2015 +0100 -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/14299] Allow output sections to be spread over multiple memory regions
https://sourceware.org/bugzilla/show_bug.cgi?id=14299 Marcus Shawcroft changed: What|Removed |Added CC||marcus.shawcroft at gmail dot com --- Comment #1 from Marcus Shawcroft --- Aside from performance enhancement aspect of this issue there is a more sinister correctness issue associated with this problem. In the case of the cortex-m4 an attempt to perform an unaligned access across the boundary will result in a memory fault. A common use case is to aggregate the two regions into a single RAM bank (ignoring any potental performance optimization that might be had), in this scenario there is no obvious way to write a link script that fills up both RAM regions but ensures that no object is placed straddling the boundary. mbed-os and several other platform software implementations address this issue by writing a linker script that partitions the RAM into the two output regions and then manually hardwire input sections to the two output sections. This solution is fragile and regularly fails with the first region overflowing, resulting in further tweaks to the linker script. zephyr-os also have this issue and currently have no workaround. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
