On Wed, Oct 2, 2024 at 9:54 AM Richard Biener
wrote:
>
> On Wed, Oct 2, 2024 at 9:13 AM Richard Biener
> wrote:
> >
> > On Tue, Oct 1, 2024 at 6:06 PM Richard Biener
> > wrote:
> > >
> > >
> > >
> > > > Am 01.10.2024 um 17:11 schrieb Matthias Kretz via Gcc :
> > > >
> > > > Hi,
> > > >
> > > >
On Wed, Oct 2, 2024 at 9:54 AM Richard Biener
wrote:
>
> On Wed, Oct 2, 2024 at 9:13 AM Richard Biener
> wrote:
> >
> > On Tue, Oct 1, 2024 at 6:06 PM Richard Biener
> > wrote:
> > >
> > >
> > >
> > > > Am 01.10.2024 um 17:11 schrieb Matthias Kretz via Gcc :
> > > >
> > > > Hi,
> > > >
> > > >
On Wed, Oct 2, 2024 at 9:13 AM Richard Biener
wrote:
>
> On Tue, Oct 1, 2024 at 6:06 PM Richard Biener
> wrote:
> >
> >
> >
> > > 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
Ben Boeckel via Gcc writes:
> 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 thes
On Tue, Oct 1, 2024 at 6:06 PM Richard Biener
wrote:
>
>
>
> > 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 probl
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
> 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
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
