On Wed, Jan 15, 2025 at 08:58:50PM +, Jonathan Wakely wrote:
> It looks like there are only 24 uses of __int24 in the testsuite, so
> maybe just adding __extension__ to those places is the best solution.
Ah, ok.
Still, there should be one new test with -pedantic and without __extension__
to ve
On Wed, 15 Jan 2025 at 20:36, Georg-Johann Lay wrote:
>
>
>
> Am 15.01.25 um 20:41 schrieb Jonathan Wakely:
> > On Wed, 15 Jan 2025 at 17:17, Georg-Johann Lay via Gcc
> > wrote:
> >>
> >> What's the recommended way to built-in define types like __uint24 ?
> >>
> >> Since v4.8, the avr backend ha
On Wed, 15 Jan 2025 at 20:57, Jakub Jelinek wrote:
>
> On Wed, Jan 15, 2025 at 09:36:51PM +0100, Georg-Johann Lay via Gcc wrote:
> > > This pedwarn is correct, so I'm not sure why it's a problem. If you
> > > don't want warnings about non-standard extensions, don't use
> > > -pedantic-errors.
> >
On Wed, Jan 15, 2025 at 09:36:51PM +0100, Georg-Johann Lay via Gcc wrote:
> > This pedwarn is correct, so I'm not sure why it's a problem. If you
> > don't want warnings about non-standard extensions, don't use
> > -pedantic-errors.
>
> The point is that I don't pedwarn explicitly, that's how the
Am 15.01.25 um 20:41 schrieb Jonathan Wakely:
On Wed, 15 Jan 2025 at 17:17, Georg-Johann Lay via Gcc wrote:
What's the recommended way to built-in define types like __uint24 ?
Since v4.8, the avr backend has:
avr-modes.def:
FRACTIONAL_INT_MODE (PSI, 24, 3);
avr.cc:
tree int24_typ
On Wed, 15 Jan 2025 at 17:17, Georg-Johann Lay via Gcc wrote:
>
> What's the recommended way to built-in define types like __uint24 ?
>
> Since v4.8, the avr backend has:
>
> avr-modes.def:
>FRACTIONAL_INT_MODE (PSI, 24, 3);
>
> avr.cc:
>tree int24_type = make_signed_type (GET_MODE_BITSIZ
What's the recommended way to built-in define types like __uint24 ?
Since v4.8, the avr backend has:
avr-modes.def:
FRACTIONAL_INT_MODE (PSI, 24, 3);
avr.cc:
tree int24_type = make_signed_type (GET_MODE_BITSIZE (PSImode));
tree uint24_type = make_unsigned_type (GET_MODE_BITSIZE (PSImode)
> On 15 Jan 2025, at 08:38, Richard Biener wrote:
>
> External email: Use caution opening links or attachments
>
>
> On Tue, Jan 14, 2025 at 4:35 PM Jennifer Schmitz via Gcc
> wrote:
>>
>> We are working on improving codegen for the following test cases (for all
>> integer types T):
>>
>>
