This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/81942] ICE on empty constexpr constructor with C++14
- From: "paolo.carlini at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 01 Sep 2017 21:52:55 +0000
- Subject: [Bug c++/81942] ICE on empty constexpr constructor with C++14
- Auto-submitted: auto-generated
- References: <bug-81942-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81942
--- Comment #11 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Uhm, no, we are not completely safe. Because in general, per 10.1.5, a
constexpr function is *not* supposed to contain goto statements, and our code
reflects that in various implicit/subtle ways. Thus the only completely Ok way
I see to fully fix the problem would be modeling somehow such special goto +
return this as plain returns, for example the returns helper function should
return true for those: the cxx_eval_statement_list loop would break as soon as
one is seen, consistently for the various targets.