On Mon, Aug 7, 2023 at 9:48 AM Theo de Raadt wrote:
>
> enh wrote:
>
> > (fwiw, Android has someone working on adding this header to upstream
> > LLVM right now, so hopefully it should come "for free" in llvm 18.
> > what, if anything, to _do_ with it is another question though :-) )
>
> Will std
enh wrote:
> (fwiw, Android has someone working on adding this header to upstream
> LLVM right now, so hopefully it should come "for free" in llvm 18.
> what, if anything, to _do_ with it is another question though :-) )
Will stdckdint.h come into common usage before or after 32-bit time_t
wraps
Lucian Popescu wrote:
> I noticed that some parts of OpenBSD use awkward techniques to detect
> undefined behavior in arithmetic operations, for example:
...
> The snippet was taken from lib/libexpat/lib/xmlparse.c
libexpat is outside source, which we incorporate
We have no influence over what
(fwiw, Android has someone working on adding this header to upstream
LLVM right now, so hopefully it should come "for free" in llvm 18.
what, if anything, to _do_ with it is another question though :-) )
On Mon, Aug 7, 2023 at 9:09 AM Lucian Popescu
wrote:
>
> Hi,
>
> I noticed that some parts of
Hi,
I noticed that some parts of OpenBSD use awkward techniques to detect
undefined behavior in arithmetic operations, for example:
> static size_t
> poolBytesToAllocateFor(int blockSize) {
> /* Unprotected math would be:
> ** return offsetof(BLOCK, s) + blockSize * sizeof(XML_Char);
> **
>
