Re: [PATCH] libstdc++: Allow adjacent __maybe_present_t to overlap

2024-04-02 Thread Pilar Latiesa
> > This is subjectively horrible and, more objectively, would create > > longer mangled names and additional RTTI. > Yeah, it's a neat trick but probably not appropriate to use within the > standard library. I understand. I was genuinely curious about whether this would do the trick. In fact, i

Re: [PATCH] libstdc++: Allow adjacent __maybe_present_t to overlap

2024-04-02 Thread Pilar Latiesa
Just out of curiosity: would this also work? template struct _Absent {}; template using __maybe_present_t = __conditional_t<_Present, _Tp, _Absent<_Tp, _Disc>>; That would avoid having to type 0, 1, ... manually.

Re: [PATCH] libstdc++: Make PSTL algorithms accept C++20 iterators [PR110512]

2024-01-13 Thread Pilar Latiesa
Hi Jonathan Thanks so much for implementing this. There are a couple of typos in the patch description: 's/C==17RandomAccessIterator/Cpp17RandomAccessIterator/' and 's/__or_/__and_/'. I've applied your patch localy and it works fine for all my use cases, which admitedly simply consist of using v

[PATCH] middle-end IFN_ASSUME support [PR106654]

2022-11-08 Thread Pilar Latiesa via Gcc-patches
On Mon, Oct 17, 2022 at 05:32:32AM +0200, Martin Uecker wrote: > Hm, that already seems to work with > > if (!std::isfinite(x)) > __builtin_unreachable(); > > https://godbolt.org/z/hj3WrEhjb Not anymore. Perhaps after making ranger the VRP default, because I get the mentioned outcome with --para