https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117394
--- Comment #2 from vincent.lebourlot at starqube dot com ---
fair enough. Any chance this might be looked at at some point? llvm doesn't
seem to have such a problem on that regex.
Cheers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117394
Bug ID: 117394
Summary: evil regex causes a stack overflow and a crash
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115941
--- Comment #4 from vincent.lebourlot at starqube dot com ---
Thank you very much for the quick answer. This can be closed then.
If I understand correctly, as this follows the standard, it won't ever be
accepted anymore in gcc despite clang acc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115941
Bug ID: 115941
Summary: g++ compiler version 15 doesn't fails to build when
g++ 12 does (may be related to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109247)
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109888
Bug ID: 109888
Summary: GCC 13 Fails to Compile Code with Explicit Constructor
for std::array in Template Class
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
