public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53829] Trivial static initializers are created for initialization with result of trivial static inline functions Date: Mon, 02 Jul 2012 10:15:00 -0000 [thread overview] Message-ID: <bug-53829-4-tDvfmfqigE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53829-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53829 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-07-02 10:15:35 UTC --- I guess we'd need to do some discovery of potential constexpr functions (that aren't marked that way though), use some bit other than DECL_DECLARED_CONSTEXPR_P for those, pass some flag from maybe_constant_value down to potential_constant_expression and cxx_eval_outermost_constant_expr (in addition to allow_non_constant or perhaps as enum instead of bool of allow_non_constant) and with optimize treat also !DECL_DECLARED_CONSTEXPR_P && DECL_CONSTEXPR_LIKE_P calls. Or is maybe_constant_value ever used to decide if a C++ program is valid or not?
prev parent reply other threads:[~2012-07-02 10:15 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-02 6:26 [Bug c++/53829] New: " mh+gcc at glandium dot org 2012-07-02 7:10 ` [Bug c++/53829] " jakub at gcc dot gnu.org 2012-07-02 7:12 ` pinskia at gcc dot gnu.org 2012-07-02 10:15 ` jakub at gcc dot gnu.org [this message]
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-53829-4-tDvfmfqigE@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).