public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c: support attribs starting with '_'
Date: Wed, 5 Oct 2022 14:52:05 +0200	[thread overview]
Message-ID: <b29bca96-96c3-f3f2-a797-bfae7f3030b6@suse.cz> (raw)
In-Reply-To: <Yz1yBO/ug9ADbUB3@tucnak>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

On 10/5/22 14:01, Jakub Jelinek wrote:
> On Wed, Oct 05, 2022 at 01:49:40PM +0200, Martin Liška wrote:
>> 	PR c/107156
>>
>> gcc/ChangeLog:
>>
>> 	* attribs.h (lookup_attribute_by_prefix): Support attributes
>> 	starting with underscore (like _noreturn, or __Noreturn).
> 
> There are no _noreturn or __Noreturn attributes, there is just
> _Noreturn.
> And, the assert is useful to catch that non-canonicalized attributes
> don't make it into the attribute lists.
> Now that we have the first attribute that starts with an underscore
> in canonicalized form (do we accept ___Noreturn__ attribute too, perhaps
> we shouldn't?), I'd say instead of removing the assert it should verify
> 	gcc_checking_assert (attr_len == 0 || p[0] != '_'
> 			     || (ident_len > 1 && p[1] != '_'));

Works for me, I'm going to install the following patch.

Martin

> ?
>> ---
>>  gcc/attribs.h | 2 --
>>  1 file changed, 2 deletions(-)
>>
>> diff --git a/gcc/attribs.h b/gcc/attribs.h
>> index b2836560fc2..706d35e63d8 100644
>> --- a/gcc/attribs.h
>> +++ b/gcc/attribs.h
>> @@ -274,8 +274,6 @@ lookup_attribute_by_prefix (const char *attr_name, tree list)
>>  	    }
>>  
>>  	  const char *p = IDENTIFIER_POINTER (name);
>> -	  gcc_checking_assert (attr_len == 0 || p[0] != '_');
>> -
>>  	  if (strncmp (attr_name, p, attr_len) == 0)
>>  	    break;
>>  
>> -- 
>> 2.37.3
> 
> 	Jakub
> 

[-- Attachment #2: 0001-c-support-the-attribute-starting-with-_.patch --]
[-- Type: text/x-patch, Size: 910 bytes --]

From b7eb1e7a0e887849470ec96c5f31422b2224c461 Mon Sep 17 00:00:00 2001
From: Martin Liska <mliska@suse.cz>
Date: Wed, 5 Oct 2022 12:34:30 +0200
Subject: [PATCH] c: support the attribute starting with '_'

	PR c/107156

gcc/ChangeLog:

	* attribs.h (lookup_attribute_by_prefix): Support the attribute
	starting with underscore (_Noreturn).
---
 gcc/attribs.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/attribs.h b/gcc/attribs.h
index b2836560fc2..121b9ebbc39 100644
--- a/gcc/attribs.h
+++ b/gcc/attribs.h
@@ -274,8 +274,8 @@ lookup_attribute_by_prefix (const char *attr_name, tree list)
 	    }
 
 	  const char *p = IDENTIFIER_POINTER (name);
-	  gcc_checking_assert (attr_len == 0 || p[0] != '_');
-
+	  gcc_checking_assert (attr_len == 0 || p[0] != '_'
+			       || (ident_len > 1 && p[1] != '_'));
 	  if (strncmp (attr_name, p, attr_len) == 0)
 	    break;
 
-- 
2.37.3


      reply	other threads:[~2022-10-05 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 11:42 Martin Liška
2022-10-05 11:48 ` Andreas Schwab
2022-10-05 11:49   ` Martin Liška
2022-10-05 12:01     ` Jakub Jelinek
2022-10-05 12:52       ` Martin Liška [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=b29bca96-96c3-f3f2-a797-bfae7f3030b6@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).