All of lore.kernel.org
 help / color / mirror / Atom feed
From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] what's the value of "NORET_TYPE"?
Date: Tue, 22 May 2007 14:25:45 +0000	[thread overview]
Message-ID: <4652FD69.6000607@bfs.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0705211425310.25535@localhost.localdomain>

hi,

a quick grep -r looks promissing:

most times it is used like this:
kernel/exit.c:fastcall NORET_TYPE void do_exit(long code)

my favourite:
include/linux/kexec.h:extern NORET_TYPE void machine_kexec(struct kimage *image) ATTRIB_NORET;

since all defines do "" and i see no #IF  ...  --> s/NORET_TYPE//g

In some cases  it is used in place of ATTRIB_NORET
some janitor may like to  replace it

re,
 wh




Cripps wrote:
> Yeah, it looks to me like it was meant specifically to support old gcc
> versions on pre 2.x kernels, so it's mostly a safe bet to pull it out.
> Best way to double check would be to patch it, test with "make
> allyesconfig; make -k > /path/to/buildLog" and see if anything related
> to that Macro fails.
> Hope this helps some ;)
> 
> -Aaron Cripps
> 
> On 5/22/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
>> On Tue, 22 May 2007, walter harms wrote:
>>
>> >
>> > i have a (wild) guess
>> > gcc supports an __attribute__ ((noreturn)). To make stuff compatible
>> sometime ago
>> > someone decided he will need it.
>> >
>> > IMHO remove it look like ancient
>> >
>> > see also: http://www.ussg.iu.edu/hypermail/linux/kernel/9605/1957.html
>>
>> oh, gcc *definitely* supports __attribute__((noreturn)), for which a
>> short form already exists in include/linux/compiler-gcc.h:
>>
>>   #define __noreturn                      __attribute__((noreturn))
>>
>> i'm just trying to figure out if there was a reason to still keep
>> NORET_TYPE around, perhaps because it was defined to represent
>> something subtlely different from __noreturn.  i'll wait for a couple
>> more opinions before i submit a patch to rip it out.  and maybe i'll
>> ask on the main LKML, where i'm sure i'll be set straight in short
>> order. :-)
>>
>> rday
>> -- 
>> ====================================
>> Robert P. J. Day
>> Linux Consulting, Training and Annoying Kernel Pedantry
>> Waterloo, Ontario, CANADA
>>
>> http://fsdev.net/wiki/index.php?title=Main_Page
>> ====================================
>> _______________________________________________
>> Kernel-janitors mailing list
>> Kernel-janitors@lists.linux-foundation.org
>> https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors
>>
> _______________________________________________
> Kernel-janitors mailing list
> Kernel-janitors@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors
> 
> 
> 
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2007-05-22 14:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 18:26 [KJ] what's the value of "NORET_TYPE"? Robert P. J. Day
2007-05-22 12:08 ` Cripps
2007-05-22 12:08 ` walter harms
2007-05-22 12:13 ` Robert P. J. Day
2007-05-22 14:25 ` walter harms [this message]
2007-05-22 14:48 ` Robert P. J. Day

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=4652FD69.6000607@bfs.de \
    --to=wharms@bfs.de \
    --cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.