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/94212] [9/10/11/12 Regression] Incorrect vectorization of loop with FP calculations Date: Tue, 01 Jun 2021 08:16:58 +0000 [thread overview] Message-ID: <bug-94212-4-a1bBu1So3k@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94212-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94212 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|9.4 |9.5 --- Comment #13 from Richard Biener <rguenth at gcc dot gnu.org> --- GCC 9.4 is being released, retargeting bugs to GCC 9.5.
next prev parent reply other threads:[~2021-06-01 8:16 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-18 12:41 [Bug c/94212] New: [AARCH64] [Regression] " dpochepk at gmail dot com 2020-03-18 12:56 ` [Bug middle-end/94212] " pinskia at gcc dot gnu.org 2020-03-18 12:58 ` pinskia at gcc dot gnu.org 2020-03-18 12:59 ` [Bug middle-end/94212] " pinskia at gcc dot gnu.org 2020-03-18 13:10 ` pinskia at gcc dot gnu.org 2020-03-18 13:44 ` [Bug tree-optimization/94212] [8/9/10 Regression] " rguenth at gcc dot gnu.org 2020-03-18 14:37 ` dpochepk at gmail dot com 2020-03-18 15:14 ` rguenth at gcc dot gnu.org 2020-03-18 16:49 ` dpochepk at gmail dot com 2021-01-14 8:34 ` [Bug tree-optimization/94212] [8/9/10/11 " rguenth at gcc dot gnu.org 2021-03-26 9:40 ` qianjh at cn dot fujitsu.com 2021-03-26 9:47 ` rguenther at suse dot de 2021-05-14 9:53 ` [Bug tree-optimization/94212] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:16 ` rguenth at gcc dot gnu.org [this message] 2022-05-27 9:42 ` [Bug tree-optimization/94212] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:40 ` jakub at gcc dot gnu.org 2022-07-26 13:47 ` rguenth 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-94212-4-a1bBu1So3k@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).