Date: Wed, 30 Dec 2020 10:13:28 -0800 From: Ryan Libby <rlibby@freebsd.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Kyle Evans <kevans@freebsd.org>, src-committers <src-committers@freebsd.org>, dev-commits-src-all@freebsd.org, dev-commits-src-branches@freebsd.org Subject: Re: git: 269b7d8ac1e5 - stable/12 - tftpd: tests: raise targeted cstd to c11 Message-ID: <CAHgpiFyu7agrS3J%2B5iJRSBMJ-C6FHXt55S31NB5Q7EdDv2Ny1w@mail.gmail.com> In-Reply-To: <X%2Bxll6dRq38%2BlxnN@kib.kiev.ua> References: <202012292306.0BTN6ivw093358@gitrepo.freebsd.org> <CACNAnaEoyoU4Caht1ZceUtSS3CAr-UG7O8amuEu_XpnzKQ8VBA@mail.gmail.com> <CAHgpiFyQrDcNYV-5C6UB0wR6r_bpww4PobMBv_Hq15FT_kfN9Q@mail.gmail.com> <CACNAnaEUCUB7A4AtsCefRpHNjSwkmsiTYvMWsEsYt8XBg3J10w@mail.gmail.com> <CACNAnaEL7cKHD=dFexAuDRomQ6zXKH-Sgb2v3t6Ja6NSnE35%2BQ@mail.gmail.com> <CAHgpiFyJyHrSTfXTvZhkg5uUzbY0Yx_yCY3aL3Fc_Zphj=a%2BbQ@mail.gmail.com> <CACNAnaEJpoSyXOi%2B06ooyEZ6zyQX7tsMUEe%2BeoCkokheNNM6LQ@mail.gmail.com> <CAHgpiFxd67vNzdqt%2BQWz7q2SwsDvJ4PSBMY=2Lpn-3fycggXhQ@mail.gmail.com> <X%2Bxll6dRq38%2BlxnN@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 30, 2020 at 3:33 AM Konstantin Belousov <kostikbel@gmail.com> wrote: > > On Tue, Dec 29, 2020 at 07:10:02PM -0800, Ryan Libby wrote: > > I checked amd64 and it failed due to pkru. I don't think we care to fix > > that either, but we technically could of course. For amd64 the external > > toolchain with gcc 6.4 is broken at the moment but will be fixed after a > > few more MFCs. > > Could you be more specific, please? > > What is broken with PKRU, the gcc 6.4 build? For kernel, or libc? > Does it work with not-so-ancient gcc? Sorry, I wasn't clear. gcc 6.4 from the external toolchain is fine with pkru. Separately, there are just a few remaining MFCs to make gcc 6.4 work out of the box with no WERROR suppression. gcc 4.2.1 for amd64 is broken, most immediately because of pkru in libc (because of new instructions and because of a use of the ifunc attribute). This is what I meant to say was technically fixable, but that we didn't care. (For those reading along who haven't checked, pkru(3) is x86-only, at least so far.) Ryan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHgpiFyu7agrS3J%2B5iJRSBMJ-C6FHXt55S31NB5Q7EdDv2Ny1w>