public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickhuang99 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92010] [8/9 Regression] gcc internal error since 8x on warning write-strings
Date: Tue, 05 Oct 2021 09:55:13 +0000 [thread overview]
Message-ID: <bug-92010-4-RtFYHjYqCR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92010-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92010
qingzhe huang <nickhuang99 at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nickhuang99 at hotmail dot com
--- Comment #11 from qingzhe huang <nickhuang99 at hotmail dot com> ---
The testcase g++.dg/cpp2a/lambda-uneval11.C still suffers a segment fault if
run by compiler cc1plus with latest code. And gdb shows that global var
"current_function_decl" is set to 0 when crashed. Should we reopen this bug?
./install/libexec/gcc/x86_64-unknown-linux-gnu/12.0.0/cc1plus -std=c++20
gcc-clone/gcc/testsuite/g++.dg/cpp2a/lambda-uneval11.C
<lambda()> void spam(decltype (<lambda>) (*)[sizeof (T)]) void foo()
<lambda()> static constexpr void<lambda()>::_FUN()
constexpr<lambda()>::operator void (*)()() const <lambda()> static constexpr
void<lambda()>::_FUN() constexpr<lambda()>::operator void (*)()() const
<lambda()> static constexpr void<lambda()>::_FUN()
constexpr<lambda()>::operator void (*)()() const <lambda()> static constexpr
void<lambda()>::_FUN() constexpr<lambda()>::operator void (*)()() const
constexpr<lambda()>::operator void (*)()() const <lambda()> static constexpr
void<lambda()>::_FUN() constexpr<lambda()>::operator void (*)()() const
gcc-clone/gcc/testsuite/g++.dg/cpp2a/lambda-uneval11.C: In instantiation of
‘constexpr<lambda()>::operator void (*)()() const’:
gcc-clone/gcc/testsuite/g++.dg/cpp2a/lambda-uneval11.C:9:12: required from
here
gcc-clone/gcc/testsuite/g++.dg/cpp2a/lambda-uneval11.C:4:25: internal compiler
error: Segmentation fault
4 | template <class T> void spam(decltype([]{}) (*s)[sizeof(T)] = nullptr)
| ^~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2021-10-05 9:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92010-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 15:29 ` [Bug c++/92010] [8/9/10 " ppalka at gcc dot gnu.org
2020-03-12 22:54 ` ppalka at gcc dot gnu.org
2020-03-12 23:02 ` ppalka at gcc dot gnu.org
2020-03-17 18:34 ` ppalka at gcc dot gnu.org
2020-04-08 14:17 ` cvs-commit at gcc dot gnu.org
2020-04-08 14:33 ` [Bug c++/92010] [8/9 " ppalka at gcc dot gnu.org
2021-04-21 21:25 ` ppalka at gcc dot gnu.org
2021-10-05 9:55 ` nickhuang99 at hotmail dot com [this message]
2021-10-05 14:23 ` ppalka at gcc dot gnu.org
2021-10-05 16:21 ` nickhuang99 at hotmail dot com
2021-10-05 21:05 ` ppalka at gcc dot gnu.org
2021-10-05 21:56 ` nickhuang99 at hotmail dot com
2021-10-05 22:08 ` nickhuang99 at hotmail dot com
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-92010-4-RtFYHjYqCR@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: link
Be 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).