public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95726] ICE with aarch64 __Float32x4_t as template argument Date: Tue, 30 Jun 2020 21:10:14 +0000 [thread overview] Message-ID: <bug-95726-4-3wO4OPkcQ2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95726-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95726 rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|aarch64-linux |aarch64*-*-* arm*-*-* --- Comment #10 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- Fixed on trunk for aarch64*-*-* only. Still needs fixing for arm*-*-* on trunk, and for both targets on branches.
next prev parent reply other threads:[~2020-06-30 21:10 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-17 19:02 [Bug c++/95726] New: " jakub at gcc dot gnu.org 2020-06-17 19:07 ` [Bug c++/95726] " jason at gcc dot gnu.org 2020-06-17 19:08 ` jason at gcc dot gnu.org 2020-06-17 19:29 ` rsandifo at gcc dot gnu.org 2020-06-17 19:36 ` jakub at gcc dot gnu.org 2020-06-18 12:49 ` rsandifo at gcc dot gnu.org 2020-06-18 16:11 ` rsandifo at gcc dot gnu.org 2020-06-18 16:46 ` jakub at gcc dot gnu.org 2020-06-18 20:10 ` jason at gcc dot gnu.org 2020-06-19 16:23 ` jason at gcc dot gnu.org 2020-06-22 16:04 ` rsandifo at gcc dot gnu.org 2020-06-30 20:40 ` cvs-commit at gcc dot gnu.org 2020-06-30 21:10 ` rsandifo at gcc dot gnu.org [this message] 2020-07-10 18:07 ` cvs-commit at gcc dot gnu.org 2020-07-15 10:58 ` cvs-commit at gcc dot gnu.org 2020-08-04 12:47 ` jakub 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-95726-4-3wO4OPkcQ2@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).