> Wednesday, October 23, 2024 > Richard Sandiford <richard.sandif...@arm.com> wrote: > >> Or, even if that does work, it isn't clear to me why patching >> ASM_OUTPUT_ALIGNED_LOCAL is a complete solution to the problem. > > This patch reproduces the same code as it was done without declaring > ASM_OUTPUT_ALIGNED_LOCAL. > ASM_OUTPUT_ALIGNED_LOCAL is needed to get the alignment value and handle it > when it is bigger than BIGGEST_ALIGNMENT. > In all other cases, the code is the same. > > https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/varasm.cc;h=c2540055421641caed08113d92dbeff7ffc09f49;hb=refs/heads/master#l2137 > https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/varasm.cc;h=c2540055421641caed08113d92dbeff7ffc09f49;hb=refs/heads/master#l2233
Does this information provide more clarity on ASM_OUTPUT_ALIGNED_LOCAL usage? If not, this patch will be dropped as a low priority, and FFmpeg, which requires this change, will be patched to avoid using alignment higher than 16 bytes on AArch64. Regards, Evgeny
