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 20:40:04 +0000	[thread overview]
Message-ID: <bug-31331-4717-sibnwCxpvc@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 #29 from Carlos Galvez <carlosgalvezp at gmail dot com> ---
Hmm, applying Aaron's suggestion above, I found what I believe to be a bug.

With this change:

+template <typename T>
+struct enum_decays_to_signed
+{
+  static constexpr bool value = std::is_signed_v<decltype(true ?
std::declval<T>() : std::declval<std::underlying_type_t<T>>())>;
+};
+
 template<typename T>
 struct enum_underlying_type
 {
   DIAGNOSTIC_PUSH
   DIAGNOSTIC_IGNORE_ENUM_CONSTEXPR_CONVERSION
   typedef typename
-    integer_for_size<sizeof (T), static_cast<bool>(T (-1) < T (0))>::type
+    integer_for_size<sizeof (T), enum_decays_to_signed<T>::value>::type
     type;
   D

I get:

./dwarf2/cooked-index.h:212:22: error: use of deleted function ‘constexpr void
operator~(enum_type) [with enum_type = cooked_index_flag_enum;
<template-parameter-1-2> = void; <template-parameter-1-3> = void]’
  212 |     flags = flags & ~IS_PARENT_DEFERRED;
      |                      ^~~~~~~~~~~~~~~~~~


This is because that enum has an underlying type of "unsigned char":

enum cooked_index_flag_enum : unsigned char


Unsigned char does decay/promote to signed integer when performing arithmetic
on it:

https://godbolt.org/z/Tfv7e3f8Y

So current master is allowing operator~ on an enum of type unsigned char, which
will decay to signed int before applying operator~ (which is what we want to
avoid, since bitwise operations shall be performed on unsigned types only).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-02-11 20:40 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
2024-02-11 18:44 ` tromey at sourceware dot org
2024-02-11 20:40 ` carlosgalvezp at gmail dot com [this message]
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-sibnwCxpvc@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: link
Be 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).