public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-3349] Fix target/102173 ICE after error recovery
Date: Fri,  3 Sep 2021 16:57:28 +0000 (GMT)	[thread overview]
Message-ID: <20210903165728.A98E1384843D@sourceware.org> (raw)

https://gcc.gnu.org/g:6b69bf5729852d0510abbe8e04078ddecef0cf17

commit r12-3349-g6b69bf5729852d0510abbe8e04078ddecef0cf17
Author: Andrew Pinski <apinski@marvell.com>
Date:   Thu Sep 2 20:59:04 2021 +0000

    Fix target/102173 ICE after error recovery
    
    After the recent r12-3278-823685221de986a change, the testcase
    gcc.target/aarch64/sve/acle/general-c/type_redef_1.c started
    to ICE as the code was not ready for error_mark_node in the
    type.  This fixes that and the testcase now passes.
    
    gcc/ChangeLog:
    
            * config/aarch64/aarch64-sve-builtins.cc (register_vector_type):
            Handle error_mark_node as the type of the type_decl.

Diff:
---
 gcc/config/aarch64/aarch64-sve-builtins.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/config/aarch64/aarch64-sve-builtins.cc b/gcc/config/aarch64/aarch64-sve-builtins.cc
index f71b287570e..bc92213665c 100644
--- a/gcc/config/aarch64/aarch64-sve-builtins.cc
+++ b/gcc/config/aarch64/aarch64-sve-builtins.cc
@@ -3416,6 +3416,7 @@ register_vector_type (vector_type_index type)
      installing an incorrect type.  */
   if (decl
       && TREE_CODE (decl) == TYPE_DECL
+      && TREE_TYPE (decl) != error_mark_node
       && TYPE_MAIN_VARIANT (TREE_TYPE (decl)) == vectype)
     vectype = TREE_TYPE (decl);
   acle_vector_types[0][type] = vectype;


                 reply	other threads:[~2021-09-03 16:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210903165728.A98E1384843D@sourceware.org \
    --to=pinskia@gcc.gnu.org \
    --cc=gcc-cvs@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: link
Be 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).