[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2019-05-13 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #17 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #16) > I'd guess it was fixed by the patch for PR 86678. Confirmed, it was fixed by r264171 for PR 86678.

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2019-05-12 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #16 from Jonathan Wakely --- I'd guess it was fixed by the patch for PR 86678.

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2019-05-11 Thread fiesh at zefix dot tv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 fiesh at zefix dot tv changed: What|Removed |Added CC||fiesh at zefix dot tv --- Comment

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2017-08-25 Thread benni.buch at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 Benjamin Buch changed: What|Removed |Added CC||benni.buch at gmail dot com --- Comment

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2017-08-14 Thread yalterz at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 Иван Молодецких changed: What|Removed |Added CC||yalterz at gmail dot com --- Comment #

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2017-07-20 Thread matthijsvanduin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 Matthijs van Duin changed: What|Removed |Added CC||matthijsvanduin at gmail dot com --

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-12-19 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #12 from Markus Trippelsdorf --- (In reply to Markus Trippelsdorf from comment #11) > (In reply to rhalbersma from comment #10) > > Ping to get this merged into the upcoming 5.4 release. > > Only regressions should be backported. Thi

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-12-19 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #11 from Markus Trippelsdorf --- (In reply to rhalbersma from comment #10) > Ping to get this merged into the upcoming 5.4 release. Only regressions should be backported. This isn't one.

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-12-19 Thread rhalbersma at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #10 from rhalbersma --- Ping to get this merged into the upcoming 5.4 release.

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-08-29 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 Markus Trippelsdorf changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-08-29 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #8 from Markus Trippelsdorf --- Author: trippels Date: Sat Aug 29 18:51:26 2015 New Revision: 227323 URL: https://gcc.gnu.org/viewcvs?rev=227323&root=gcc&view=rev Log: Fix c++/67371 (issues with throw in constexpr) As PR67371 shows

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-08-28 Thread Casey at Carter dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #7 from Casey Carter --- (In reply to Markus Trippelsdorf from comment #6) > Well, my patch survives regression testing and fixes the issue. > > But unfortunately it leads to accept invalid cases like: > > constexpr int f1() { > t

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-08-28 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #6 from Markus Trippelsdorf --- Well, my patch survives regression testing and fixes the issue. But unfortunately it leads to accept invalid cases like: constexpr int f1() { throw; return 0; } or constexpr void f2() { throw

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-08-28 Thread miyuki at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 Mikhail Maltsev changed: What|Removed |Added CC||miyuki at gcc dot gnu.org --- Comment

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-08-28 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #4 from Markus Trippelsdorf --- The fix might be as simple as: diff --git a/gcc/cp/constexpr.c b/gcc/cp/constexpr.c index 1eacb8be9a44..7016b347a79c 100644 --- a/gcc/cp/constexpr.c +++ b/gcc/cp/constexpr.c @@ -4324,7 +4324,6 @@ poten

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-08-27 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 Markus Trippelsdorf changed: What|Removed |Added Keywords||rejects-valid Status|U

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-08-27 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 Markus Trippelsdorf changed: What|Removed |Added CC||rhalbersma at gmail dot com --- Co

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2015-08-27 Thread ldionne.2 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #1 from Louis Dionne --- This is almost certainly a duplicate of #66026, yet it is still unconfirmed.