Re: netbsd-11 gcc bug

--pgp-sign-Multipart_Sun_May_24_16:52:49_2026-1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

At Sun, 24 May 2026 11:38:59 -0400, Jason Thorpe <[email protected]> wrote:
Subject: Re: netbsd-11 gcc bug
>=20
> > On May 24, 2026, at 8:33 AM, Mouse <[email protected]>
> > wrote:
> >  Perhaps the gcc people are able-and-willing to do that.  But,
> > if not, I still maintain that it is thereby unsuitable for the
> > use case of building NetBSD.
>=20
> I mean, I also find  compiler people  annoying in this regard, but
> this doesn t render the compiler  unsuitable .  Just fix the code
> and be done with it.  I do wish the compiler at least emitted a
> warning, however, when a NULL-check is elided for this reason.

Indeed, especially for the warnings!  (Does UBSAN help?)

The ultimate fix may be to convince the C standards committee to
eliminate all cases of "undefined behaviour" from the standard.

Converting most cases to "implementation defined behaviour" should be
one option.  Some others may require whacking some sense into some
vendors of esoteric systems.

There are apparently some attempts afoot to do this (according to Robert
C. Seacord, the current convenor of the committee if I understand
correctly).


--=20
					Greg A. Woods <[email protected]>

Kelowna, BC     +1 250 762-7675           RoboHack <[email protected]>
Planix, Inc. <[email protected]>     Avoncote Farms <[email protected]>

--pgp-sign-Multipart_Sun_May_24_16:52:49_2026-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Description: OpenPGP Digital Signature

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRuK6dmwVAucmRxuh9mfXG3eL/0fwUCahOPVwAKCRBmfXG3eL/0
f0DgAJ9lkGpZeXf2tNq5ak7U6rqH6hs1OgCg9jeMVoGooai3j5GnWLSkgMi3Hko=
=BEvd
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Sun_May_24_16:52:49_2026-1--