linux-kernel - Re: any value to "NORET

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.0.99.0705220950160.3308@sigma.j-a-k-j.com>
Date:	Tue, 22 May 2007 09:53:03 -0400 (EDT)
From:	"John Anthony Kazos Jr." <jakj@...-k-j.com>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: any value to "NORET_TYPE" macro?

>   given that:
> 
> $ grep -r "define.*NORET_TYPE" *
> include/linux/ext4_fs.h:# define NORET_TYPE    /**/
> include/linux/linkage.h:#define NORET_TYPE    /**/
> include/linux/ext3_fs.h:# define NORET_TYPE    /**/
> $
> 
> is there any obvious value to the 30 or so uses of that macro
> sprinkled throughout the tree?

Since it evaluates to absolutely empty code during pre-processing, there 
is no obvious value. The question is whether there is some odd hackish 
non-obvious value, I'd expect. (I'd also expect that to be another "no".)

If something that evaluates to nothingness ("There was nothing left...not 
even a hole!") actually does anything, then somebody in the 
standards-compilers-users pipeline needs to be violently beaten for 
stupidity.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/