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

On Tue, Oct 01, 2024 at 18:06:35 +0200, Richard Biener via Gcc wrote: > Analyze where the compile time is spent and where memory is spent. > Identify unfitting data structures and algorithms causing the issue. > Replace with better ones. That’s what I do for these kind of issues > in the middle en

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

> Am 01.10.2024 um 17:11 schrieb 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 di

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

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

GCC devroom at FOSDEM 2025?

Hi! FOSDEM have recently posted the "FOSDEM 2025 call for devrooms", . Given the great success of last year's GCC devroom: , I'd like to apply again, for a GCC devroom (and related toolchain parts)

Re: GCC devroom at FOSDEM 2025?

Hi Thomas. > FOSDEM have recently posted the "FOSDEM 2025 call for devrooms", > . > Given the great success of last year's GCC devroom: > , I'd like to apply again, > for a GCC devroom (and relate