public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97379] [11 Regression] Invalid read of size 8 at outgoing_range::calc_switch_ranges(gswitch*) (gimple-range-edge.cc:140) since r11-3685-gfcae5121154d1c33 Date: Mon, 12 Oct 2020 08:40:51 +0000 [thread overview] Message-ID: <bug-97379-4-fdiCOe52Cd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97379-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97379 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-10-12 Summary|[11 Regression] Invalid |[11 Regression] Invalid |read of size 8 at |read of size 8 at |outgoing_range::calc_switch |outgoing_range::calc_switch |_ranges(gswitch*) |_ranges(gswitch*) |(gimple-range-edge.cc:140) |(gimple-range-edge.cc:140) | |since | |r11-3685-gfcae5121154d1c33 Target Milestone|--- |11.0 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Started with r11-3685-gfcae5121154d1c33.
next prev parent reply other threads:[~2020-10-12 8:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-12 8:40 [Bug tree-optimization/97379] New: [11 Regression] Invalid read of size 8 at outgoing_range::calc_switch_ranges(gswitch*) (gimple-range-edge.cc:140) marxin at gcc dot gnu.org 2020-10-12 8:40 ` marxin at gcc dot gnu.org [this message] 2020-10-12 11:42 ` [Bug tree-optimization/97379] [11 Regression] Invalid read of size 8 at outgoing_range::calc_switch_ranges(gswitch*) (gimple-range-edge.cc:140) since r11-3685-gfcae5121154d1c33 rguenth at gcc dot gnu.org 2020-10-13 9:00 ` aldyh at gcc dot gnu.org 2020-10-13 9:00 ` aldyh at gcc dot gnu.org 2020-10-13 15:03 ` cvs-commit at gcc dot gnu.org 2020-10-13 15:08 ` aldyh 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-97379-4-fdiCOe52Cd@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).