How to debug/improve excessive compiler memory usage and compile times

2024-10-01 Thread Matthias Kretz via Gcc
Hi, the unit tests are my long-standing pain point of excessive compiler memory usage and compile times. I've always worked around the memory usage problem by splitting the test matrix into multiple translations (with different -D flags) of the same source file. I.e. pay with a huge number of

Re: IFNDR on UB? [was: Straw poll on shifts with out of range operands]

2024-07-01 Thread Matthias Kretz via Gcc
On Sunday, 30 June 2024 08:33:35 GMT+2 Martin Uecker wrote: > Am Sonntag, dem 30.06.2024 um 05:03 +0200 schrieb Matthias Kretz: > > On Saturday, 29 June 2024 16:20:55 GMT+2 Martin Uecker wrote: > > > Am Samstag, dem 29.06.2024 um 08:50 -0500 schrieb Matthias Kretz via Gcc: &g

Re: IFNDR on UB? [was: Straw poll on shifts with out of range operands]

2024-06-29 Thread Matthias Kretz via Gcc
On Saturday, 29 June 2024 16:20:55 GMT+2 Martin Uecker wrote: > Am Samstag, dem 29.06.2024 um 08:50 -0500 schrieb Matthias Kretz via Gcc: > > I.e. once UB becomes IFNDR, the dreaded time-travel optimizations can't > > happen anymore. Instead precondition checks bubble up becau

IFNDR on UB? [was: Straw poll on shifts with out of range operands]

2024-06-29 Thread Matthias Kretz via Gcc
On Tuesday, 25 June 2024 21:44:15 CDT Andrew Pinski via Gcc wrote: > I am in the middle of improving the isolation path pass for shifts > with out of range operands. > There are 3 options we could do really: > 1) isolate the path to __builtin_unreachable > 2) isolate the path to __builtin_trap >