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 tree-optimization/97494] [11 regression] several vector test case failures starting with r11-3966 Date: Mon, 19 Oct 2020 15:21:42 +0000 [thread overview] Message-ID: <bug-97494-4-cm5mvwR5Kr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97494-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97494 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Target Milestone|--- |11.0 Last reconfirmed| |2020-10-19 Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Hmm, I'll have a look how/if to adjust testcases. Help appreciated.
next prev parent reply other threads:[~2020-10-19 15:21 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-19 15:07 [Bug tree-optimization/97494] New: " seurer at gcc dot gnu.org 2020-10-19 15:21 ` rguenth at gcc dot gnu.org [this message] 2020-10-21 9:18 ` [Bug tree-optimization/97494] " clyon at gcc dot gnu.org 2020-12-11 12:15 ` ro at gcc dot gnu.org 2021-01-14 9:27 ` rguenth at gcc dot gnu.org 2021-01-18 14:00 ` rguenth at gcc dot gnu.org 2021-01-18 14:19 ` rguenth at gcc dot gnu.org 2021-01-18 14:20 ` cvs-commit at gcc dot gnu.org 2021-03-11 12:32 ` cvs-commit at gcc dot gnu.org 2021-03-11 13:03 ` rguenth at gcc dot gnu.org 2021-03-11 13:05 ` cvs-commit at gcc dot gnu.org 2021-03-11 13:13 ` cvs-commit at gcc dot gnu.org 2021-03-11 13:16 ` rguenth at gcc dot gnu.org 2021-03-11 18:48 ` seurer 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-97494-4-cm5mvwR5Kr@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).