Re: [PATCH] gcc/configure: Fix check for assembler section merging support on Arm

2025-01-09 Thread Richard Earnshaw (lists)
On 08/01/2025 21:47, Thiago Jung Bauermann wrote: > "Richard Earnshaw (lists)" writes: > >> On 27/12/2024 21:47, Thiago Jung Bauermann wrote: >>> In 32-bit Arm assembly, the @ character is the start of a comment so >>> the section type needs to use the % character instead. >>> >>> configure.ac at

Re: [PATCH] gcc/configure: Fix check for assembler section merging support on Arm

2025-01-08 Thread Thiago Jung Bauermann
"Richard Earnshaw (lists)" writes: > On 27/12/2024 21:47, Thiago Jung Bauermann wrote: >> In 32-bit Arm assembly, the @ character is the start of a comment so >> the section type needs to use the % character instead. >> >> configure.ac attempts to account for this difference by doing a second >>

Re: [PATCH] gcc/configure: Fix check for assembler section merging support on Arm

2025-01-08 Thread Richard Earnshaw (lists)
On 27/12/2024 21:47, Thiago Jung Bauermann wrote: > In 32-bit Arm assembly, the @ character is the start of a comment so > the section type needs to use the % character instead. > > configure.ac attempts to account for this difference by doing a second > try when checking the assembler for section

Re: [PATCH] gcc/configure: Fix check for assembler section merging support on Arm

2025-01-02 Thread Thiago Jung Bauermann
Hello, Thiago Jung Bauermann writes: > This problem was noticed because the recent binutils commit > d5cbf916be4a ("gas/ELF: also reject merge entity size being zero") caused > gas to be stricter about mergeable sections without an entity size: > > configure:27013: checking assembler for section

[PATCH] gcc/configure: Fix check for assembler section merging support on Arm

2024-12-27 Thread Thiago Jung Bauermann
In 32-bit Arm assembly, the @ character is the start of a comment so the section type needs to use the % character instead. configure.ac attempts to account for this difference by doing a second try when checking the assembler for section merging support. Unfortunately there is a bug: because the