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, 04 Feb 2024 18:10:14 +0000 [thread overview] Message-ID: <bug-31331-4717-5A6Bhb1DYM@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 #3 from Carlos Galvez <carlosgalvezp at gmail dot com> --- Exactly, I really don't understand the purpose of that part of test - what requirement from the production code is it enforcing/protecting? I see a couple issues with the existing code: - The assumption that C-style enums are signed. This is not true - it's implementation-defined behavior, and one should typically not rely on that. In practice, we observe that if a C-style enum has all values positive, the underlying type is unsigned, otherwise signed. - As you point out, the expression: auto var = cond ? enum_1 : enum_2; Does not make much sense. If these were C++ enums, the code would not compile. One should either use a std::variant, or explicitly cast the enums to int. I would thus vote for removing that part from the test (as you mentioned, it's marked as unimportant). But it would be good to understand why it was added in the first place. I'm also unsure if we can trust that everything still works just because it compiles fine (maybe some implicit conversions leading to the wrong numbers). I was considering to fiddle with it and run "make check" but I had a couple of questions: - How long time is it expected to take, on say 16 cores? - Will the output log be deterministic even when running in parallel? I read in the wiki that there are failing tests on trunk, so one needs to diff the test logs. Diffing the test logs is only possible if they have the same content in the same order? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-04 18:10 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 [this message] 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 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-5A6Bhb1DYM@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).