Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761121AbXHBUSa (ORCPT ); Thu, 2 Aug 2007 16:18:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759399AbXHBUSX (ORCPT ); Thu, 2 Aug 2007 16:18:23 -0400 Received: from sovereign.computergmbh.de ([85.214.69.204]:59323 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754943AbXHBUSW (ORCPT ); Thu, 2 Aug 2007 16:18:22 -0400 Date: Thu, 2 Aug 2007 22:18:21 +0200 (CEST) From: Jan Engelhardt To: Guennadi Liakhovetski cc: linux-kernel@vger.kernel.org Subject: Re: gcc fixed size char array initialization bug - known? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 719 Lines: 31 On Aug 2 2007 21:55, Guennadi Liakhovetski wrote: >Hi > >I've run across the following gcc "feature": > > char c[4] = "01234"; > >gcc emits a nice warning > >warning: initializer-string for array of chars is too long > >But do a > > char c[4] = "0123"; > >and - a wonder - no warning. No warning with gcc 3.3.2, 3.3.5, 3.4.5, >4.1.2. I was told 4.2.x does produce a warning. Now do a Unfortunately, gcc 4.2.1 does not produce a warning for char a[4] = "haha"; Jan -- - 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/