mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Russell King <rmk@arm.linux.org.uk>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	bryan.wu@analog.com, michael.frysinger@analog.com,
	robin.getz@analog.com, Paul Mackerras <paulus@samba.org>,
	LKML Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Replace __attribute_pure__ with __pure
Date: Sat, 6 Oct 2007 14:49:57 -0400	[thread overview]
Message-ID: <3CD096B0-2235-46AD-B0FC-83ED02778E41@mac.com> (raw)
In-Reply-To: <4706DC09.1060403@zytor.com>

Trimmed the CC list a bit

On Oct 05, 2007, at 20:51:21, H. Peter Anvin wrote:
> Ralf Baechle wrote:
>> To be consistent with the use of attributes in the rest of the  
>> kernel replace all use of __attribute_pure__ with __pure and  
>> delete the definition of __attribute_pure__.
>
> Concern: __attribute_pure__ is very similar to __attribute_const__,  
> which is almost completely, but not totally unlike the keyword  
> "const"...

Yes, there's also the fact that __pure is a reserved GCC keyword.   
Essentially according to GCC docs all of the GCC-specific keywords  
are equivalently defined as "keyword", "__keyword", and  
"__keyword__", with only the latter two defined in strict-ANSI mode.   
The following is valid according to GCC docs:

static int __attribute__((__pure)) my_strlen(const char *str);

With the proposed definition of __pure, that becomes a noticeably  
invalid __attribute__((__attribute__((__pure__))))


Cheers,
Kyle Moffett


      reply	other threads:[~2007-10-06 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 13:13 Ralf Baechle
2007-10-05 13:23 ` Mauro Carvalho Chehab
2007-10-05 15:35 ` Mike Frysinger
2007-10-05 22:36 ` Robin Getz
2007-10-06  0:51 ` H. Peter Anvin
2007-10-06 18:49   ` Kyle Moffett [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=3CD096B0-2235-46AD-B0FC-83ED02778E41@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=akpm@linux-foundation.org \
    --cc=bryan.wu@analog.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=michael.frysinger@analog.com \
    --cc=paulus@samba.org \
    --cc=ralf@linux-mips.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=robin.getz@analog.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

Powered by JetHome