Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756801Ab2BATzs (ORCPT ); Wed, 1 Feb 2012 14:55:48 -0500 Received: from mx1.redhat.com ([209.132.183.28]:59517 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756650Ab2BATzq (ORCPT ); Wed, 1 Feb 2012 14:55:46 -0500 Message-ID: <4F299888.40307@redhat.com> Date: Wed, 01 Feb 2012 12:54:48 -0700 From: Jeff Law User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: "Boehm, Hans" CC: Torvald Riegel , Linus Torvalds , Jan Kara , LKML , "linux-ia64@vger.kernel.org" , "dsterba@suse.cz" , "ptesarik@suse.cz" , "rguenther@suse.de" , "gcc@gcc.gnu.org" Subject: Re: Memory corruption due to word sharing References: <20120201151918.GC16714@quack.suse.cz> <1328118174.15992.6206.camel@triegel.csb> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 882 Lines: 15 On 02/01/2012 12:44 PM, Boehm, Hans wrote: > C11 is a published standard. Last I checked, gcc did not follow many of the above rules. It looks like major changes were recently merged into the gcc trunk, and I haven't had a chance to test those, so it may well be fixed. But more importantly, so far I haven't read anything here to dissuade me that they are the right target. The bitfield changes didn't make it into gcc-4.7; we're still working through implementation details. GCC's bitfield support is a horrid nasty mess which has made implementation of the standard problematical. It's on Aldy's plate for gcc-4.8. jeff -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/