public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109532] -fshort-enums does not pick smallest underlying type for scoped enum Date: Tue, 18 Apr 2023 08:15:15 +0000 [thread overview] Message-ID: <bug-109532-4-MNYCqdSjcG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109532-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109532 --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Wilhelm M from comment #5) > So in general a scoped-enum inside a class (nested type) maybe always a bad > idea, because it prevents optimization. I don't know how you have drawn that conclusion or how it's related to this bug report. > And when specifying the underlying > type, the -fstrict-enums can't be applied because all values of the > underlying type are possible. Correct, with a fixed underlying type -fstrict-enums and -fshort-enums have no effect.
next prev parent reply other threads:[~2023-04-18 8:15 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-17 5:08 [Bug c++/109532] New: " klaus.doldinger64 at googlemail dot com 2023-04-17 5:16 ` [Bug rtl-optimization/109532] " pinskia at gcc dot gnu.org 2023-04-17 5:16 ` pinskia at gcc dot gnu.org 2023-04-17 5:24 ` [Bug c++/109532] " klaus.doldinger64 at googlemail dot com 2023-04-17 5:30 ` pinskia at gcc dot gnu.org 2023-04-17 5:37 ` klaus.doldinger64 at googlemail dot com 2023-04-18 8:15 ` redi at gcc dot gnu.org [this message] 2023-05-17 13:03 ` cvs-commit at gcc dot gnu.org 2023-05-17 13:52 ` redi 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-109532-4-MNYCqdSjcG@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).