Re: gcc issue building -current
Jan-Benedict Glaw <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.vax |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 2024-01-10 19:07:58 +0100, Martin Husemann <[email protected]> wrote: > On Wed, Jan 10, 2024 at 06:00:30PM +0100, Martin Husemann wrote: > > The build cluster has not run into this yet, so I suppose a recentish lint > > change in -current triggers this. > > I verified that it only happens with today's usr.bin/xlint sources, the > version from yesterday builds fine. > > Nevertheless, it is a gcc issue, not a lint one - though we probably want > to back out that change untill gcc is fixed. You added a HACKS note that this is likely be fixed in GCC 11. Looking at the bug report, it seems that was worked on only in Alpha-specific code, so I don't guess VAX will take any profit here. MfG, JBG --
signature.asc
(application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCZaOiswAKCRAdvV51g5nh u2ROAJoCpYbNrOMtEu8OppYJfYplqiwvqQCgh5h2HDL8rrPz6QNs4OCnMey2yOw= =sx5p -----END PGP SIGNATURE-----