https://sourceware.org/bugzilla/show_bug.cgi?id=25665
--- Comment #6 from rrorden at ptc dot com --- I understand now. Thanks for the explanation. For now I have found a workaround for my problem with a large aot-compiled object by custom-naming the ELF sections and using a linker script to order those sections first in the output. But I think this will only work until the object gets big enough that calls to external functions are over 128k away. If I implement the equivalent of -ffunction-sections, would this cause the image expansion problem for A53 erratum you mentioned? Is it possible to keep track of the accumulated size of the input sections and emit a shared veneer sub-section only when it is about to exceed 128k? Then you only have to align to a 4K boundary every 128k. -- You are receiving this mail because: You are on the CC list for the bug.
