| 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
| ||
|
Message-ID: <20080403015946.GX9785@ZenIV.linux.org.uk> Date: Thu, 3 Apr 2008 02:59:46 +0100 From: Al Viro <viro@...IV.linux.org.uk> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Harvey Harrison <harvey.harrison@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, josh@...edesktop.org Subject: Re: [PATCH 7/7] asm-generic: suppress sparse warning in ioctl.h On Wed, Apr 02, 2008 at 06:50:20PM -0700, Linus Torvalds wrote: > > > On Thu, 3 Apr 2008, Al Viro wrote: > > > > Umm... How far do you want sparse to go? You _really_ don't want > > bug-for-bug compatibility with gcc - it's far too weird (and that's > > even before going into the effects of optimization flags). > > I would suggest just accepting link-time constants in constant > expressions. But yeah, maybe limit even that just to unevaluated > subexpressions. Um... But that's _not_ a link-time constant - simply an int variable not defined in any object file... > That said, for sparse, the right thing to do would be to use > __builtin_warning() or something, but gcc doesn't have that kind of thing, > so.. > > > BTW, what happened with sparse.git? > > Yeah, we do seem to have lost a maintainer. -- 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/
Powered by blists - more mailing lists