This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: initializer_constant_valid_p
- To: geoffk at ozemail dot com dot au
- Subject: Re: initializer_constant_valid_p
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Mon, 1 Nov 99 04:41:54 EST
- Cc: gcc-patches at gcc dot gnu dot org
breaks the build, because ch/typeck.c also defines
initializer_constant_valid_p. The two functions seem to be different;
I'm not sure if this intentional (in which case the change needs to be
reverted) or if they're supposed to be the same, in which case the
copy should be deleted from ch/typeck.c.
My view is that only varasm.c can "know" what initializers are valid
since it's the one that writes the initializers so if there's also a copy
if ch/typeck.c, that one is wrong. But I'd like some comments from the
Chill folks.