linux-kernel - Re: [patch 01/10] compiler: define __attribute_unused_

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: <20070503190522.GM3531@stusta.de>
Date:	Thu, 3 May 2007 21:05:22 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch 01/10] compiler: define __attribute_unused__

On Thu, May 03, 2007 at 11:56:34AM -0700, David Rientjes wrote:
> On Thu, 3 May 2007, Adrian Bunk wrote:
> 
> > > That's only addressing part of the issue.  What about automatic or static 
> > > external variables that are declared but may go unreferenced depending on 
> > 
> > This is only about static code. For non-static code it would be
> > impossible for gcc to issue warnings.
> 
> static external variables are certainly still static code and gcc issues 
> the proper warnings if I do:
> 
> 	static struct bootnode nodes[MAX_NUMNODES];
> 
> and I never reference nodes.

No disagreement.

But you said:
  What about automatic or static external variables that are declared but ...

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/