public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Matthew Malcomson <matmal01@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/ARM/heads/morello)] morello: Don't treat TYPE_P nodes as capability values
Date: Mon, 14 Mar 2022 10:35:17 +0000 (GMT)	[thread overview]
Message-ID: <20220314103517.5D530385E010@sourceware.org> (raw)

https://gcc.gnu.org/g:473121a7071e99c7953002b8e0103688bd1ba3a3

commit 473121a7071e99c7953002b8e0103688bd1ba3a3
Author: Alex Coplan <alex.coplan@arm.com>
Date:   Fri Feb 11 14:23:46 2022 +0000

    morello: Don't treat TYPE_P nodes as capability values
    
    Return false in tree_is_capability_value for TYPE_P tree nodes: these
    are not capability *values*. The C++ frontend often ends up with types
    where we expect a value when doing template substitution, we don't want
    to treat these as capability values.
    
    gcc/ChangeLog:
    
            * tree.h (tree_is_capability_value): Return false if argument is
            TYPE_P.

Diff:
---
 gcc/tree.h | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/gcc/tree.h b/gcc/tree.h
index c2fbd1eccdf..674eb1acf64 100644
--- a/gcc/tree.h
+++ b/gcc/tree.h
@@ -6366,7 +6366,10 @@ fndecl_built_in_p (const_tree node, built_in_function name)
 static inline bool
 tree_is_capability_value (const_tree t)
 {
-  return t && t != error_mark_node && capability_type_p (TREE_TYPE (t));
+  return t
+    && t != error_mark_node
+    && !TYPE_P (t)
+    && capability_type_p (TREE_TYPE (t));
 }
 
 inline wide_int


                 reply	other threads:[~2022-03-14 10:35 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=20220314103517.5D530385E010@sourceware.org \
    --to=matmal01@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).