public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "klaus.doldinger64 at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109532] New: -fshort-enums does not pick smallest underlying type for scoped enum Date: Mon, 17 Apr 2023 05:08:08 +0000 [thread overview] Message-ID: <bug-109532-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109532 Bug ID: 109532 Summary: -fshort-enums does not pick smallest underlying type for scoped enum Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: klaus.doldinger64 at googlemail dot com Target Milestone: --- In the follwoing code, the best code with 8-bit underlying for the enum-type is only optimized for unscoped enum. The scoped enum always produces a 16-bit enum underlying type. Compile with: -Os -mmcu=atmega328 -fshort-enums (note: equivalent C code (unscoped enums) produces optimal code with -fshort-enums) #include <avr/io.h> #include <stdint.h> volatile uint8_t o; struct FSM { // enum class State : uint8_t {A, B, C, D};// <2> 8bit enum // enum State {A, B, C, D}; // <3> 8bit enum with -fshort-enums enum class State {A, B, C, D}; // <1> 16bit enum with -fshort-enums static void f() __attribute__((noinline)) { switch(mState) { case State::A: o = 10; break; case State::B: o = 11; break; case State::C: o = 12; break; case State::D: o = 13; break; } } private: inline static State mState{State::A}; }; int main() { while(true) { FSM::f(); } }
next reply other threads:[~2023-04-17 5:08 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-17 5:08 klaus.doldinger64 at googlemail dot com [this message] 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 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@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).