public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99381] SVE: ICE with ACLE intrinsics when missing -march=armv8.2-a+sve Date: Thu, 11 Mar 2021 12:49:58 +0000 [thread overview] Message-ID: <bug-99381-4-MjiaGWMEVc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99381-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99381 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Alex Coplan <acoplan@gcc.gnu.org>: https://gcc.gnu.org/g:6925d4763e469e43b9d06e4a17187215bc03d3c9 commit r10-9436-g6925d4763e469e43b9d06e4a17187215bc03d3c9 Author: Alex Coplan <alex.coplan@arm.com> Date: Thu Mar 4 14:36:39 2021 +0000 aarch64: Add missing error_mark_node check [PR99381] We were missing a check in function_resolver::require_vector_type to see if the argument type was already invalid. This was causing us to attempt to emit a diagnostic and subsequently ICE in print_type. Fixed thusly. gcc/ChangeLog: PR target/99381 * config/aarch64/aarch64-sve-builtins.cc (function_resolver::require_vector_type): Handle error_mark_node. gcc/testsuite/ChangeLog: PR target/99381 * gcc.target/aarch64/pr99381.c: New test. (cherry picked from commit a6bc1680a493de356d6a381718021c6a44401201)
next prev parent reply other threads:[~2021-03-11 12:49 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-04 9:56 [Bug target/99381] New: " acoplan at gcc dot gnu.org 2021-03-04 14:37 ` [Bug target/99381] " cvs-commit at gcc dot gnu.org 2021-03-04 14:39 ` acoplan at gcc dot gnu.org 2021-03-04 14:47 ` acoplan at gcc dot gnu.org 2021-03-11 12:49 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-11 12:50 ` acoplan 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-99381-4-MjiaGWMEVc@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).