public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "macro at orcam dot me.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107405] [13 Regression] enum change causing Linux kernel to fail to build due to Linux depending on old behavior Date: Sat, 19 Nov 2022 13:18:04 +0000 [thread overview] Message-ID: <bug-107405-4-wUsp9sQ1et@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107405-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107405 --- Comment #15 from Maciej W. Rozycki <macro at orcam dot me.uk> --- If in older C standard versions such enums are invalid, then I think this should be a hard error rather than a silent ABI change for the code produced. Not all code out there will have sanity checks such as the Linux kernel does and things will break for people in a tough way (think a public header file defining an enumeration and objects linked that define data of such an enumeration type and have been built with different compiler versions).
next prev parent reply other threads:[~2022-11-19 13:18 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-26 4:26 [Bug c/107405] New: enums can be long in gcc-13 jirislaby at gmail dot com 2022-10-26 4:28 ` [Bug c/107405] enums can be wrongly long in gcc-13 (in gnu99) jirislaby at gmail dot com 2022-10-26 6:55 ` marxin at gcc dot gnu.org 2022-10-26 7:08 ` marxin at gcc dot gnu.org 2022-10-26 7:27 ` jirislaby at gmail dot com 2022-10-26 7:31 ` jirislaby at gmail dot com 2022-10-26 7:45 ` jakub at gcc dot gnu.org 2022-10-26 7:53 ` jirislaby at gmail dot com 2022-10-26 8:04 ` jakub at gcc dot gnu.org 2022-10-26 8:21 ` redi at gcc dot gnu.org 2022-10-26 8:39 ` jirislaby at gmail dot com 2022-10-26 8:49 ` jirislaby at gmail dot com 2022-10-26 16:55 ` [Bug c/107405] [13 Regression] enum change causing Linux kernel to fail to build due to Linux depending on old behavior pinskia at gcc dot gnu.org 2022-10-26 17:35 ` joseph at codesourcery dot com 2022-10-28 11:19 ` rguenth at gcc dot gnu.org 2022-11-19 8:43 ` jakub at gcc dot gnu.org 2022-11-19 13:18 ` macro at orcam dot me.uk [this message] 2022-11-19 20:46 ` jakub at gcc dot gnu.org 2022-11-21 18:10 ` joseph at codesourcery dot com 2022-11-22 14:53 ` macro at orcam dot me.uk 2022-11-22 22:47 ` joseph at codesourcery dot com 2022-11-29 14:57 ` pinskia at gcc dot gnu.org 2023-01-13 11:36 ` rguenth at gcc dot gnu.org 2023-03-24 9:27 ` rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-107405-4-wUsp9sQ1et@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).