public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97268] 11 Regression] Segfault on 11.0.0 20200930 Date: Fri, 02 Oct 2020 07:08:20 +0000 [thread overview] Message-ID: <bug-97268-4-kIVS2V9DGQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97268-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97268 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.0 Status|WAITING |NEW Summary|Segfault on 11.0.0 20200930 |11 Regression] Segfault on | |11.0.0 20200930 CC| |msebor at gcc dot gnu.org --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- OK, confirmed. It's -Wextra that triggers the following for me: during GIMPLE pass: *early_warn_uninitialized t.C: In constructor 'BetterObject<CACHED>::BetterObject(const char*, int, Handle&) [with bool CACHED = true]': t.C:63:1: internal compiler error: in gimple_call_arg, at gimple.h:3256 63 | } | ^ 0x1a61d17 gimple_call_arg /home/rguenther/src/gcc3/gcc/gimple.h:3256 0x1a61d6d gimple_call_arg /home/rguenther/src/gcc3/gcc/gimple.h:3264 0x1a63c4d maybe_warn_pass_by_reference /home/rguenther/src/gcc3/gcc/tree-ssa-uninit.c:526 0x1a6434d warn_uninitialized_vars /home/rguenther/src/gcc3/gcc/tree-ssa-uninit.c:643 0x1a693d9 execute_early_warn_uninitialized /home/rguenther/src/gcc3/gcc/tree-ssa-uninit.c:3018 0x1a6944c execute /home/rguenther/src/gcc3/gcc/tree-ssa-uninit.c:3053 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. where on a stmt Object<true>::Object (_2, _3); we try to access argument 3. Not sure how readwrite attributes ended up there, I see them on some libstdc++ functions only. Maybe some bad sharing of function type trees? CCing Martin.
next prev parent reply other threads:[~2020-10-02 7:08 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-02 5:48 [Bug c++/97268] New: " ext-gcc at burakarslan dot com 2020-10-02 6:55 ` [Bug c++/97268] " rguenth at gcc dot gnu.org 2020-10-02 7:01 ` ext-gcc at burakarslan dot com 2020-10-02 7:03 ` ext-gcc at burakarslan dot com 2020-10-02 7:08 ` rguenth at gcc dot gnu.org [this message] 2020-10-02 7:16 ` [Bug c++/97268] [11 Regression] ICE in maybe_warn_pass_by_reference at gcc/tree-ssa-uninit.c:514 since r11-1763-g27aebb7d6cf14175 marxin at gcc dot gnu.org 2020-10-02 12:06 ` marxin at gcc dot gnu.org 2020-10-02 16:56 ` nathan at gcc dot gnu.org
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-97268-4-kIVS2V9DGQ@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).