On Tue, Nov 21, 2023 at 12:12:18AM +, Joseph Myers wrote:
> On Mon, 20 Nov 2023, Jakub Jelinek wrote:
>
> > and be done with that. If there is an agreement we should do that
> > for all 14 rather than just those 3 + the 2 ugly hacks (__builtin_c{l,t}zg
> > with
> > 0ULL second argument and _
(corrected address)
> On Mon, 20 Nov 2023, Jakub Jelinek wrote:
>
> > On Mon, Nov 20, 2023 at 08:37:55AM +, Richard Biener wrote:
> > > > I'm not sure about that, it would be nice for them to be usable there,
> > >
> > > Btw, I think that {( .. )} should be made usable in sizeof () and
>
On Mon, 20 Nov 2023, Jakub Jelinek wrote:
> and be done with that. If there is an agreement we should do that
> for all 14 rather than just those 3 + the 2 ugly hacks (__builtin_c{l,t}zg
> with
> 0ULL second argument and __builtin_bit_complement), I can change the
I tend to agree with the "ugly
On Mon, 20 Nov 2023, Jakub Jelinek wrote:
> On Mon, Nov 20, 2023 at 08:37:55AM +, Richard Biener wrote:
> > > I'm not sure about that, it would be nice for them to be usable there,
> >
> > Btw, I think that {( .. )} should be made usable in sizeof () and
> > possibly even in at least C++ cons
On Mon, Nov 20, 2023 at 08:37:55AM +, Richard Biener wrote:
> > I'm not sure about that, it would be nice for them to be usable there,
>
> Btw, I think that {( .. )} should be made usable in sizeof () and
> possibly even in at least C++ constant expressions (not sure about C).
I believe the p
On Mon, 20 Nov 2023, Jakub Jelinek wrote:
> On Mon, Nov 20, 2023 at 09:18:57AM +0100, Florian Weimer wrote:
> > * Richard Biener:
> >
> > > Ugh. First of all I don't like that the exception is applied during
> > > folding. As for the problem of multi evaluation can't consumers use
> > > stmt ex
On Mon, Nov 20, 2023 at 09:18:57AM +0100, Florian Weimer wrote:
> * Richard Biener:
>
> > Ugh. First of all I don't like that the exception is applied during
> > folding. As for the problem of multi evaluation can't consumers use
> > stmt expressions for this, say
> >
> > {( auto __tem = value;
On Mon, Nov 20, 2023 at 07:49:40AM +, Richard Biener wrote:
> Of course the other obvious alternative would be to parse
> stdc_leading_zeros and friends directly, and not go through macros
> and builtins.
The stdc_* names are not keywords and without including stdbit.h I'm
not sure it is ok to
* Richard Biener:
> Ugh. First of all I don't like that the exception is applied during
> folding. As for the problem of multi evaluation can't consumers use
> stmt expressions for this, say
>
> {( auto __tem = value; __builtin_xyz (__tem, __typeof (__tem)); ... )}
>
> ? Thus use 'auto' to avoi
On Mon, Nov 20, 2023 at 07:44:18AM +, Richard Biener wrote:
> > In https://sourceware.org/pipermail/libc-alpha/2023-November/152819.html
> > Florian Weimer raised concern that the type-generic stdbit.h macros
> > currently being considered suffer from similar problem as old tgmath.h
> > impleme
On Mon, 20 Nov 2023, Richard Biener wrote:
> On Sat, 18 Nov 2023, Jakub Jelinek wrote:
>
> > Hi!
> >
> > In https://sourceware.org/pipermail/libc-alpha/2023-November/152819.html
> > Florian Weimer raised concern that the type-generic stdbit.h macros
> > currently being considered suffer from sim
On Sat, 18 Nov 2023, Jakub Jelinek wrote:
> Hi!
>
> In https://sourceware.org/pipermail/libc-alpha/2023-November/152819.html
> Florian Weimer raised concern that the type-generic stdbit.h macros
> currently being considered suffer from similar problem as old tgmath.h
> implementation, in particul
Hi!
In https://sourceware.org/pipermail/libc-alpha/2023-November/152819.html
Florian Weimer raised concern that the type-generic stdbit.h macros
currently being considered suffer from similar problem as old tgmath.h
implementation, in particular that the macros expand during preprocessing
their ar
13 matches
Mail list logo
