public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "carlosgalvezp at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31331] Wenum-constexpr-conversion should be fixed, soon treated as a hard error Date: Sun, 11 Feb 2024 18:21:37 +0000 [thread overview] Message-ID: <bug-31331-4717-jZokYdlIY0@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31331-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31331 --- Comment #27 from Carlos Galvez <carlosgalvezp at gmail dot com> --- There's 2 orthogonal issues: - C enums have implementation-defined underlying type. - C enums get promoted to signed ints when operating arithmetically (well-defined behavior, specified in the Standard). If we change the logic of the code from detecting "is enum unsigned" to detecting "will enum be promoted to signed int" then there shouldn't be any implementation-defined behavior and the code should behave identically under all compilers. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-11 18:21 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-02 20:36 [Bug gdb/31331] New: " carlosgalvezp at gmail dot com 2024-02-03 2:40 ` [Bug gdb/31331] " tromey at sourceware dot org 2024-02-03 21:14 ` tromey at sourceware dot org 2024-02-03 21:30 ` sam at gentoo dot org 2024-02-04 18:10 ` carlosgalvezp at gmail dot com 2024-02-04 18:57 ` simon.marchi at polymtl dot ca 2024-02-04 19:56 ` tromey at sourceware dot org 2024-02-04 19:58 ` tromey at sourceware dot org 2024-02-04 21:02 ` tromey at sourceware dot org 2024-02-04 21:19 ` tromey at sourceware dot org 2024-02-04 21:26 ` carlosgalvezp at gmail dot com 2024-02-05 19:28 ` carlosgalvezp at gmail dot com 2024-02-05 19:29 ` carlosgalvezp at gmail dot com 2024-02-05 19:30 ` carlosgalvezp at gmail dot com 2024-02-05 19:47 ` carlosgalvezp at gmail dot com 2024-02-05 19:53 ` simon.marchi at polymtl dot ca 2024-02-05 20:04 ` carlosgalvezp at gmail dot com 2024-02-05 20:08 ` simon.marchi at polymtl dot ca 2024-02-05 20:09 ` simon.marchi at polymtl dot ca 2024-02-05 20:11 ` simon.marchi at polymtl dot ca 2024-02-05 20:43 ` carlosgalvezp at gmail dot com 2024-02-05 20:55 ` carlosgalvezp at gmail dot com 2024-02-05 21:03 ` carlosgalvezp at gmail dot com 2024-02-05 21:19 ` simon.marchi at polymtl dot ca 2024-02-06 18:32 ` carlosgalvezp at gmail dot com 2024-02-07 20:47 ` carlosgalvezp at gmail dot com 2024-02-11 10:02 ` carlosgalvezp at gmail dot com 2024-02-11 17:16 ` tromey at sourceware dot org 2024-02-11 17:19 ` tromey at sourceware dot org 2024-02-11 18:21 ` carlosgalvezp at gmail dot com [this message] 2024-02-11 18:44 ` tromey at sourceware dot org 2024-02-11 20:40 ` carlosgalvezp at gmail dot com 2024-02-13 23:54 ` tromey at sourceware dot org 2024-03-26 15:37 ` tromey at sourceware dot org 2024-04-16 22:57 ` tromey at sourceware dot org 2024-04-17 10:41 ` carlosgalvezp at gmail dot com 2024-04-20 18:22 ` brobecker at gnat dot com 2024-05-08 22:12 ` carlosgalvezp at gmail dot com 2024-05-10 20:35 ` carlosgalvezp at gmail dot com
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-31331-4717-jZokYdlIY0@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).