n3369 New _Lengthof operator (v4)

2024-10-02 Thread Alejandro Colomar via Gcc
On Wed, Oct 02, 2024 at 08:21:54PM +0200, Alejandro Colomar wrote: > > Hi Daniel, > > Here's a revised version of the WG14 paper, with all issues addressed. I had a topy in the paper number. Here's the paper with the number fixed. Cheers, Alex > > Have a lovely day! > Alex > > On Wed, Oct 0

n3365 New _Lengthof operator (v4)

2024-10-02 Thread Alejandro Colomar via Gcc
Hi Daniel, Here's a revised version of the WG14 paper, with all issues addressed. Have a lovely day! Alex On Wed, Oct 02, 2024 at 11:41:20AM +0200, Alejandro Colomar wrote: > Hi! > > This operator is as voted in a WG14 meeting yesterday, with the only > difference that we name it __lengthof__

RE: Understanding bogus? gcc.dg/signbit-6.c

2024-10-02 Thread Tamar Christina via Gcc
> -Original Message- > From: Georg-Johann Lay > Sent: Wednesday, October 2, 2024 3:06 PM > To: GCC Development ; Tamar Christina > > Subject: Re: Understanding bogus? gcc.dg/signbit-6.c > > Am 02.10.24 um 15:55 schrieb Georg-Johann Lay: > > I am having problems understanding test case gc

Re: Understanding bogus? gcc.dg/signbit-6.c

2024-10-02 Thread Georg-Johann Lay
Am 02.10.24 um 15:55 schrieb Georg-Johann Lay: I am having problems understanding test case gcc.dg/signbit-6.c which fails on a 16-bit platform (avr). https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/testsuite/gcc.dg/signbit-6.c;h=da186624cfa057dfc3780c8af4f6b1335ba07e7e;hb=HEAD The relevant par

RE: Understanding bogus? gcc.dg/signbit-6.c

2024-10-02 Thread Tamar Christina via Gcc
> -Original Message- > From: Georg-Johann Lay > Sent: Wednesday, October 2, 2024 2:55 PM > To: GCC Development ; Tamar Christina > > Subject: Understanding bogus? gcc.dg/signbit-6.c > > I am having problems understanding test case gcc.dg/signbit-6.c > which fails on a 16-bit platform (av

Understanding bogus? gcc.dg/signbit-6.c

2024-10-02 Thread Georg-Johann Lay
I am having problems understanding test case gcc.dg/signbit-6.c which fails on a 16-bit platform (avr). https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/testsuite/gcc.dg/signbit-6.c;h=da186624cfa057dfc3780c8af4f6b1335ba07e7e;hb=HEAD The relevant part of the code is: int main () { TYPE a[N];

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

2024-10-02 Thread Richard Biener via Gcc
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, > > > > > > > >

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

2024-10-02 Thread Richard Biener via Gcc
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, > > > > > > > >

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

2024-10-02 Thread Richard Biener via Gcc
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

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

2024-10-02 Thread Andi Kleen via Gcc
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

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

2024-10-02 Thread Richard Biener via Gcc
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