public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redbeard0531 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102876] New: GCC fails to use constant initialization even when it knows the value to initialize Date: Thu, 21 Oct 2021 11:48:45 +0000 [thread overview] Message-ID: <bug-102876-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102876 Bug ID: 102876 Summary: GCC fails to use constant initialization even when it knows the value to initialize Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: redbeard0531 at gmail dot com Target Milestone: --- See: https://godbolt.org/z/KnKv9j8b9 #include <chrono> using namespace std::literals; /*not constexpr*/ inline std::chrono::sys_days compute_days() { return 1776y/7/4; } std::chrono::sys_days BURN_IN_TO_BINARY = compute_days(); Clang and MSVC both correctly burn BURN_IN_TO_BINARY into the binary image with the correct value. Even with -O3, gcc zero-initializes it then uses a dynamic initializer to complete the initialization. Both are valid implementation strategies according to https://eel.is/c++draft/basic.start.static#3, however, I think the strategy used by clang and MSVC is clearly superior QoI here.
next reply other threads:[~2021-10-21 11:48 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-21 11:48 redbeard0531 at gmail dot com [this message] 2021-10-21 12:37 ` [Bug c++/102876] " redi at gcc dot gnu.org 2021-10-21 12:52 ` rguenth at gcc dot gnu.org 2021-10-21 13:43 ` redbeard0531 at gmail dot com 2021-10-21 14:50 ` ppalka at gcc dot gnu.org 2021-10-21 15:20 ` jakub at gcc dot gnu.org 2021-10-21 18:36 ` jason at gcc dot gnu.org 2021-10-21 19:32 ` jason at gcc dot gnu.org 2021-10-22 21:35 ` pinskia at gcc dot gnu.org 2021-10-25 9:55 ` jakub at gcc dot gnu.org 2021-10-25 21:19 ` jason at gcc dot gnu.org 2021-10-26 8:41 ` jakub at gcc dot gnu.org 2021-10-26 8:46 ` jakub at gcc dot gnu.org 2021-10-26 11:04 ` redbeard0531 at gmail dot com 2021-10-26 11:38 ` jakub at gcc dot gnu.org 2021-10-27 17:11 ` jakub at gcc dot gnu.org 2021-11-03 18:25 ` jakub at gcc dot gnu.org 2022-10-17 14:11 ` ppalka 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-102876-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).