• [gentoo-dev] GCC 14 unleashed

    From Sam James@21:1/5 to All on Sun May 19 16:40:01 2024
    Hi,

    As we discussed a bunch in #gentoo-toolchain over the last few weeks,
    GCC 14 is now in ~arch. We've spent the last > 2 years working on this
    and fixing lots of packages, but kind of reached the limit of how much a handful of people can do.

    This is kind of the analogue of the Clang post I made a while ago [0].

    It makes a lot of dangerous, broken C constructs errors by default. We
    have a writeup at https://wiki.gentoo.org/wiki/Modern_C_porting. See
    also https://gcc.gnu.org/gcc-14/porting_to.html.

    Advice:
    * Please ask us in #gentoo-toolchain if you need help understanding how
    to fix a bug. You may have users submitting patches, but please ask if
    you're unsure if they're correct.
    * Please only add casts if you're sure they're right. Otherwise, they're
    just suppressing it.
    * Report upstream immediately if you see an issue, even if you don't yet
    have time to try fix it yourself. This means upstream can work on it in
    the background and other distros and folks may end up sharing their
    patches.
    * Similarly, it's paramount that patches get submitted upstream so they
    can be reviewed and other distros can benefit. We have benefitted a lot
    from others doing that, and vice-versa.
    * The code was broken before (badly) and this just surfaces
    that. -Wno-error=* and friends are not an option. The wiki page covers
    that but I can explain it more if needed.

    The tracker bugs are:
    * https://bugs.gentoo.org/870412 (c99-porting)
    * https://bugs.gentoo.org/906027 (implicit-in-configure)
    * https://bugs.gentoo.org/914580 (gcc-14, general; only use for other issues)

    The implicit-in-configure issues are more important than c99-porting because of the risk
    of a misconfigured build.

    [0] https://public-inbox.gentoo.org/gentoo-dev/87tu4c8z49.fsf@mop.mail-host-address-is-not-set/

    thanks,
    sam

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

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

    iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZkoOWl8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZAKcAD+MyZ9tF190UQ6OsjIKFhSSKq6O47ctheMfbFB sJtPU6gA/idQL8NgOE260VHYROylFHsjiqaI3tqsQbIhz2+Qd9sB
    =+nLn
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sam James@21:1/5 to Sam James on Sun May 19 17:40:01 2024
    Sam James <sam@gentoo.org> writes:

    Oh, and:
    * The code was broken before (badly) [...]

    ... and therefore you should be revbumping for fixes.

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

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

    iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZkobQ18UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZBAiQD+KR9SVS9B6U+uUzkybfOim2exGUehyrstpzmi HWotchABAM+keOGaGNvTFbpzQ1i0CZLG6B4C0sf+G/kwHiLQC9YA
    =+jvV
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)