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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 20 Oct 2014 00:19:08 +0100 From: Al Viro <viro@...IV.linux.org.uk> To: "Kirill A. Shutemov" <kirill@...temov.name> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Aaro Koskinen <aaro.koskinen@....fi>, Andrew Pinski <pinskia@...il.com>, Sasha Levin <sasha.levin@...cle.com>, Andrew Morton <akpm@...ux-foundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] kernel: use the gnu89 standard explicitly On Mon, Oct 20, 2014 at 02:10:31AM +0300, Kirill A. Shutemov wrote: > On Sun, Oct 19, 2014 at 04:05:25PM -0700, Linus Torvalds wrote: > > On Sun, Oct 19, 2014 at 2:03 PM, Aaro Koskinen <aaro.koskinen@....fi> wrote: > > > > > > Here's one example how it fails: http://marc.info/?l=gcc&m=141349914632010&w=2 > > > > Ok, that just looks like a gnu11 bug, then. Not being able to > > initialize structures because some sub-structure has a volatile member > > is just pure BS. > > > > Has anybody reported this as a gcc bug? That email may be on the gcc > > list, but I'm not seeing anybody acknowledge it as a bug.. > > > > I cannot imagine that anybody sane claims that this is *wanted* > > behavior from "gnu11". > > IIUC, it's nothing to do with volatile. C11 and above reads > > (rwlock_t) { .raw_lock = { 0 }, } > > as compound literal (which is not constant) rather than constant > initalizer plus a cast. Ah... They hadn't even pulled it into gnu99; IIRC, they even tried to remove it in gnu89, but Linus' complaints had stopped that attempt. -- 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