Re: [PATCH] asan: Handle poly-int sizes in ASAN_MARK [PR97696]

2024-03-05 Thread Jakub Jelinek
On Tue, Mar 05, 2024 at 07:49:21PM +, Richard Sandiford wrote: > Jakub Jelinek writes: > > On Tue, Mar 05, 2024 at 06:30:40PM +, Richard Sandiford wrote: > >> (1) Keep the test where it is, taking advantage of the current SVE > >> handling in aarch64-sve.exp, and add: > >> > >>

Re: [PATCH] asan: Handle poly-int sizes in ASAN_MARK [PR97696]

2024-03-05 Thread Richard Sandiford
Jakub Jelinek writes: > On Tue, Mar 05, 2024 at 06:30:40PM +, Richard Sandiford wrote: >> (1) Keep the test where it is, taking advantage of the current SVE >> handling in aarch64-sve.exp, and add: >> >> /* { dg-skip-if "" { no_fsanitize_address } } */ > > I'd go with this. asan/ d

Re: [PATCH] asan: Handle poly-int sizes in ASAN_MARK [PR97696]

2024-03-05 Thread Jakub Jelinek
On Tue, Mar 05, 2024 at 06:30:40PM +, Richard Sandiford wrote: > (1) Keep the test where it is, taking advantage of the current SVE > handling in aarch64-sve.exp, and add: > > /* { dg-skip-if "" { no_fsanitize_address } } */ I'd go with this. asan/ directory for test would be neede

Re: [PATCH] asan: Handle poly-int sizes in ASAN_MARK [PR97696]

2024-03-05 Thread Richard Sandiford
Jakub Jelinek writes: > On Tue, Mar 05, 2024 at 06:03:41PM +, Richard Sandiford wrote: >> This patch makes the expansion of IFN_ASAN_MARK let through >> poly-int-sized objects. The expansion itself was already generic >> enough, but the tests for the fast path were too strict. >> >> Bootstra

Re: [PATCH] asan: Handle poly-int sizes in ASAN_MARK [PR97696]

2024-03-05 Thread Jakub Jelinek
On Tue, Mar 05, 2024 at 06:03:41PM +, Richard Sandiford wrote: > This patch makes the expansion of IFN_ASAN_MARK let through > poly-int-sized objects. The expansion itself was already generic > enough, but the tests for the fast path were too strict. > > Bootstrapped & regression tested on aa

[PATCH] asan: Handle poly-int sizes in ASAN_MARK [PR97696]

2024-03-05 Thread Richard Sandiford
This patch makes the expansion of IFN_ASAN_MARK let through poly-int-sized objects. The expansion itself was already generic enough, but the tests for the fast path were too strict. Bootstrapped & regression tested on aarch64-linux-gnu. Is this OK for trunk now, or should it wait for GCC 15? I'