From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17787 invoked by alias); 1 Dec 2008 23:39:50 -0000 Received: (qmail 17598 invoked by uid 48); 1 Dec 2008 23:38:25 -0000 Date: Mon, 01 Dec 2008 23:39:00 -0000 Message-ID: <20081201233825.17597.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c/38354] Spurious error: initializer element is not computable at load time In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "gnu at behdad dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-12/txt/msg00106.txt.bz2 ------- Comment #2 from gnu at behdad dot org 2008-12-01 23:38 ------- It's not a useful use case, agreed, but I don't see how that affects the computability of a value at "load time", whatever that means. It did trick me: I was converting a vtable to use label values, and before converting the function pointer type of the array to int, I tried a compile and got the error. I didn't expect the error to go away if I replace the function pointer type with an int. To my surprise, it did. What I'm saying is that the statement in the error message is false. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38354