public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/107514] New: quick crash of gcc due to noexcept specification
@ 2022-11-03 8:36 janezz55 at gmail dot com
2022-11-03 9:50 ` [Bug c++/107514] " janezz55 at gmail dot com
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: janezz55 at gmail dot com @ 2022-11-03 8:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107514
Bug ID: 107514
Summary: quick crash of gcc due to noexcept specification
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: janezz55 at gmail dot com
Target Milestone: ---
The noexcept specification is probably c++ non-complaint, but still causes a
crash:
constexpr void assign_tuple(auto& t, auto&& ...a)
noexcept(noexcept(
[]<auto ...I>(std::index_sequence<I...>)
noexcept(noexcept(
((std::get<I>(t) = std::forward<decltype(a)>(a)), ...)
)
)
{
}(std::make_index_sequence<sizeof...(a)>())
)
)
{
[&]<auto ...I>(std::index_sequence<I...>)
noexcept(noexcept(((std::get<I>(t) = std::forward<decltype(a)>(a)), ...)))
{
((std::get<I>(t) = std::forward<decltype(a)>(a)), ...);
}(std::make_index_sequence<sizeof...(a)>());
}
prog.cc: In instantiation of 'assign_tuple<std::tuple<int, int, int>, int, int,
int>(std::tuple<int, int, int>&, int&&, int&&,
int&&)::<lambda(std::index_sequence<I ...>)> [with auto ...I = {0, 1, 2};
std::index_sequence<I ...> = std::integer_sequence<long unsigned int, 0, 1,
2>]':
prog.cc:21:4: required from 'constexpr void assign_tuple(auto:1&, auto:2&&
...) [with auto:1 = std::tuple<int, int, int>; auto:2 = {int, int, int}]'
prog.cc:29:15: required from here
prog.cc:18:73: internal compiler error: Segmentation fault
18 | noexcept(noexcept(((std::get<I>(t) = std::forward<decltype(a)>(a)),
...)))
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
The source is here:
https://wandbox.org/permlink/alJJGFEkTE8b7EXn
I can't provide anything else, since I typed it in over at wandbox. I suspect
the bug is a duplicate anyway. clang does not crash while compiling the
snippet.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug c++/107514] quick crash of gcc due to noexcept specification
2022-11-03 8:36 [Bug c++/107514] New: quick crash of gcc due to noexcept specification janezz55 at gmail dot com
@ 2022-11-03 9:50 ` janezz55 at gmail dot com
2022-11-05 10:54 ` rguenth at gcc dot gnu.org
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: janezz55 at gmail dot com @ 2022-11-03 9:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107514
--- Comment #1 from Janez Zemva <janezz55 at gmail dot com> ---
A working version:
https://wandbox.org/permlink/ki45SRwCNwuMRw7G
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug c++/107514] quick crash of gcc due to noexcept specification
2022-11-03 8:36 [Bug c++/107514] New: quick crash of gcc due to noexcept specification janezz55 at gmail dot com
2022-11-03 9:50 ` [Bug c++/107514] " janezz55 at gmail dot com
@ 2022-11-05 10:54 ` rguenth at gcc dot gnu.org
2022-11-05 13:30 ` janezz55 at gmail dot com
2022-11-08 1:31 ` ppalka at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-11-05 10:54 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107514
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-11-05
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Please attach the full example.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug c++/107514] quick crash of gcc due to noexcept specification
2022-11-03 8:36 [Bug c++/107514] New: quick crash of gcc due to noexcept specification janezz55 at gmail dot com
2022-11-03 9:50 ` [Bug c++/107514] " janezz55 at gmail dot com
2022-11-05 10:54 ` rguenth at gcc dot gnu.org
@ 2022-11-05 13:30 ` janezz55 at gmail dot com
2022-11-08 1:31 ` ppalka at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: janezz55 at gmail dot com @ 2022-11-05 13:30 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107514
--- Comment #3 from Janez Zemva <janezz55 at gmail dot com> ---
Created attachment 53833
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53833&action=edit
example
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug c++/107514] quick crash of gcc due to noexcept specification
2022-11-03 8:36 [Bug c++/107514] New: quick crash of gcc due to noexcept specification janezz55 at gmail dot com
` (2 preceding siblings ...)
2022-11-05 13:30 ` janezz55 at gmail dot com
@ 2022-11-08 1:31 ` ppalka at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: ppalka at gcc dot gnu.org @ 2022-11-08 1:31 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107514
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppalka at gcc dot gnu.org
Keywords| |ice-on-invalid-code
Status|WAITING |NEW
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-11-08 1:31 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-03 8:36 [Bug c++/107514] New: quick crash of gcc due to noexcept specification janezz55 at gmail dot com
2022-11-03 9:50 ` [Bug c++/107514] " janezz55 at gmail dot com
2022-11-05 10:54 ` rguenth at gcc dot gnu.org
2022-11-05 13:30 ` janezz55 at gmail dot com
2022-11-08 1:31 ` ppalka at gcc dot gnu.org
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).