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 21:56:25 +0000 [thread overview] Message-ID: <bug-92010-4-xIswz6Fp9U@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 --- Comment #15 from qingzhe huang <nickhuang99 at hotmail dot com> --- >>Might be better to open a separate PR for this as it seems to be a latent bug. thanks, I will file a new bug. From: ppalka at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> Sent: October 5, 2021 5:05 PM To: nickhuang99@hotmail.com <nickhuang99@hotmail.com> Subject: [Bug c++/92010] [8/9 Regression] gcc internal error since 8x on warning write-strings https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92010 --- Comment #14 from Patrick Palka <ppalka at gcc dot gnu.org> --- (In reply to qingzhe huang from comment #13) > (In reply to Patrick Palka from comment #12) > > (In reply to qingzhe huang from comment #11) > > > The testcase g++.dg/cpp2a/lambda-uneval11.C still suffers a segment fault if > > > run by compiler cc1plus with latest code. > > > > Hmm, I can't reproduce that on latest trunk. Is your working tree clean? > > I tested in both 10.2.x and 11.2.x and even latest 12.x with yesterday pull. > It won't show anything when compiling with driver, i.e. g++, but if you run > "cc1plus", it will crash. For example, > ${GCC_INSTALL}/libexec/gcc/x86_64-unknown-linux-gnu/11.2.0/cc1plus > -std=c++20 ./lambda-uneval11.C > > Thank you Ah yeah, I can reproduce the crash when invoking cc1plus directly and also when passing -Q to the driver. Might be better to open a separate PR for this as it seems to be a latent bug.
next prev parent reply other threads:[~2021-10-05 21:56 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 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 [this message] 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-xIswz6Fp9U@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: linkBe 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).