Re: [libc-coord] Re: Expose 'array_length()' macro in or

2020-09-21 Thread enh via Gcc
Why would C++ programmers need this given https://en.cppreference.com/w/cpp/iterator/size ? On Mon, Sep 21, 2020, 05:54 Alejandro Colomar wrote: > [[ CC += libc-coord at lists.openwall.com ]] > > On 2020-09-21 12:33, Florian Weimer wrote: > > * Alejandro Colomar: > > > >> [[ > >> CC += libc-coor

Re: [libc-coord] Add new ABI '__memcmpeq()' to libc

2021-09-16 Thread enh via Gcc
(Android libc maintainer.) should __memcmpeq be in compiler-rt rather than libc? On Thu, Sep 16, 2021 at 1:35 PM Joseph Myers wrote: > On Thu, 16 Sep 2021, Chris Kennelly wrote: > > > In terms of relying on the feature: If __memcmpeq is ever exposed as an > a > > simple alias for memcmp (since

Re: [libc-coord] Add new ABI '__memcmpeq()' to libc

2021-09-16 Thread enh via Gcc
plus testing for _equality_ can (as mentioned earlier) have slightly different properties from the three-way comparator behavior of bcmp()/memcmp(). On Thu, Sep 16, 2021 at 2:43 PM Joseph Myers wrote: > On Thu, 16 Sep 2021, James Y Knight wrote: > > > Wouldn't it be far simpler to just un-deprec

Re: _Nullable and _Nonnull in GCC's analyzer (was: [PATCH v5] libio: Add nonnull attribute for most FILE * arguments in stdio.h)

2023-08-08 Thread enh via Gcc
(bionic maintainer here, mostly by accident...) yeah, we tried the GCC attributes once before with _disastrous_ results (because GCC saw it as an excuse to delete explicit null checks, it broke all kinds of things). the clang attributes are "better" in that they don't confuse two entirely separate

Re: _Nullable and _Nonnull in GCC's analyzer (was: [PATCH v5] libio: Add nonnull attribute for most FILE * arguments in stdio.h)

2023-08-11 Thread enh via Gcc
On Wed, Aug 9, 2023 at 12:26 AM Martin Uecker wrote: > > Am Dienstag, dem 08.08.2023 um 17:14 -0700 schrieb enh: > > (bionic maintainer here, mostly by accident...) > > > > yeah, we tried the GCC attributes once before with _disastrous_ > > results (because GCC saw it as an excuse to delete explic

Re: On pull request workflows for the GNU toolchain

2024-09-23 Thread enh via Gcc
it doesn't make the patch _management_ problem better ("now i have two problems"), but https://github.com/landley/toybox takes the "why not both?" approach --- you can use pull requests if you grew up with/adapted to git/github, or you can use the mailing list otherwise ... taking into account that