public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [PATCH 3/3] attribs: Namespace-aware lookup_attribute_spec
Date: Fri, 10 Nov 2023 13:27:48 -0700	[thread overview]
Message-ID: <ef9a8040-b9b8-4690-9394-e2d198f4453e@gmail.com> (raw)
In-Reply-To: <mptwmuvax2x.fsf@arm.com>



On 11/6/23 05:24, Richard Sandiford wrote:
> attribute_ignored_p already used a namespace-aware query
> to find the attribute_spec for an existing attribute:
> 
>        const attribute_spec *as = lookup_attribute_spec (TREE_PURPOSE (attr));
> 
> This patch does the same for other callers in the file.
> 
> Tested on aarch64-linux-gnu & x86_64-linux-gnu.  OK to install?
> 
> Richard
> 
> 
> gcc/
> 	* attribs.cc (comp_type_attributes): Pass the full TREE_PURPOSE
> 	to lookup_attribute_spec, rather than just the name.
> 	(remove_attributes_matching): Likewise.
OK
jeff

      reply	other threads:[~2023-11-10 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 12:24 Richard Sandiford
2023-11-10 20:27 ` Jeff Law [this message]

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=ef9a8040-b9b8-4690-9394-e2d198f4453e@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.sandiford@arm.com \
    /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).