From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28156 invoked by alias); 3 Dec 2002 00:26:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 28142 invoked by uid 71); 3 Dec 2002 00:26:01 -0000 Date: Mon, 02 Dec 2002 16:26:00 -0000 Message-ID: <20021203002601.28141.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Wolfgang Bangerth Subject: Re: c++/8778: ICE on illegal initialization of non-integral static in-class constant Reply-To: Wolfgang Bangerth X-SW-Source: 2002-12/txt/msg00106.txt.bz2 List-Id: The following reply was made to PR c++/8778; it has been noted by GNATS. From: Wolfgang Bangerth To: Volker Reichelt Cc: gcc-gnats@gcc.gnu.org, , Subject: Re: c++/8778: ICE on illegal initialization of non-integral static in-class constant Date: Mon, 2 Dec 2002 18:19:36 -0600 (CST) > I don't quite agree with Wolfgangs analysis. :-) > Initializing const arrays is usually supported by gcc. True, but not as static member variables. > In fact, the code compiles if you just leave out the curly > braces around the initializer. > > So the ICE is neither caused by the array initializer nor by the > infinite recursion (which might also come to mind as a compiler crasher) > as the following example shows: > > --------------------snip here---------------------- > template struct A > { > static const int i = A<0>::i; // works > static const int i = { A<0>::i }; // ICE > static const int i = { 1 }; // works > }; > --------------------snip here---------------------- Your analysis gives a clue as to what goes wrong in the compiler, but note that the original code reads const static int result[] = { mylist::result }; ^^^^ This is what makes it illegal, not the curly braces. In your example, you are initializing a scalar, he is initializing an array/pointer. However, the curly braces seem to be the reason for the ICE, as you point out. But thanks for the analysis anyway, it will help those that actually fix the problem :-) W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth