public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103938] [10/11/12/13 Regression] ICE with __builtin_prefetch and vectors Date: Tue, 28 Jun 2022 10:47:36 +0000 [thread overview] Message-ID: <bug-103938-4-e0p8kUqqza@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103938-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103938 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|10.4 |10.5 --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- GCC 10.4 is being released, retargeting bugs to GCC 10.5.
next prev parent reply other threads:[~2022-06-28 10:47 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-07 10:12 [Bug target/103938] New: " pinskia at gcc dot gnu.org 2022-01-07 10:51 ` [Bug target/103938] " pinskia at gcc dot gnu.org 2022-01-28 0:33 ` [Bug target/103938] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-28 0:35 ` pinskia at gcc dot gnu.org 2022-04-06 16:28 ` acoplan at gcc dot gnu.org 2022-04-06 16:36 ` pinskia at gcc dot gnu.org 2022-04-07 9:17 ` acoplan at gcc dot gnu.org 2022-04-19 15:30 ` rguenth at gcc dot gnu.org 2022-04-28 17:29 ` [Bug target/103938] [9/10/11/12/13 " acoplan at gcc dot gnu.org 2022-04-28 19:14 ` pinskia at gcc dot gnu.org 2022-05-27 9:47 ` [Bug target/103938] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:47 ` jakub at gcc dot gnu.org [this message] 2023-07-07 10:41 ` [Bug target/103938] [11/12/13/14 " 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-103938-4-e0p8kUqqza@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).