public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96496] New: Conversion to enum with underlying type bool produces wrong result
Date: Thu, 06 Aug 2020 13:36:40 +0000	[thread overview]
Message-ID: <bug-96496-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96496

            Bug ID: 96496
           Summary: Conversion to enum with underlying type bool produces
                    wrong result
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fw at gcc dot gnu.org
  Target Milestone: ---

enum E : bool { One, Two };

int
f1 (int x)
{
  return (E) x;
}

The conversion must first be to type bool, according to:

“If the enumeration type has a fixed underlying type, the value is first
converted to that type by integral conversion, if necessary, and then to the
enumeration type.”

<http://eel.is/c++draft/expr.static.cast#10>

And that must produce a comparison against zero:

“A zero value, null pointer value, or null member pointer value is converted to
false; any other value is converted to true.”

<http://eel.is/c++draft/conv.bool#1>

Currently, GCC performs a bit mask (at -O2):

_Z2f1i:
        movl    %edi, %eax
        andl    $1, %eax
        ret

             reply	other threads:[~2020-08-06 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 13:36 fw at gcc dot gnu.org [this message]
2020-08-06 13:40 ` [Bug c++/96496] " redi at gcc dot gnu.org
2020-08-06 13:56 ` mpolacek at gcc dot gnu.org
2020-08-25  9:22 ` redi at gcc dot gnu.org
2021-08-01  0:17 ` pinskia at gcc dot gnu.org
2022-10-28  0:38 ` cvs-commit at gcc dot gnu.org
2024-02-17 15:49 ` mpolacek 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-96496-4@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: 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).