This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Compiling GCC With a C++ Compiler (g++)
- From: Ranjit Mathew <rmathew at gmail dot com>
- To: GCC <gcc at gcc dot gnu dot org>
- Cc: gkeating at apple dot com
- Date: Tue, 12 Oct 2004 13:08:26 +0530
- Subject: Re: Compiling GCC With a C++ Compiler (g++)
- References: <ckdds6$kpt$1@sea.gmane.org>
Ranjit Mathew wrote:
> The definition of tree_string is:
>
> struct tree_string GTY(())
> {
> struct tree_common common;
> int length;
> const char str[1];
> };
>
> If the "const" is removed from above, the compilation
> proceeds.
The "const char *pointer" -> "const char str[1]" change
was done by geoffk as a part of fixing pch/13361.
We now want to store the string in the node itself,
rather than merely pointing to it.
However, I still think that the "const" is
misleading/incorrect. In build_string() in tree.c,
we cast it to (char *) anyways before memcpy-ing the
desired string into it.
Would it be wrong to remove it? (And thus re-enable
compiling this bit of GCC with a C++ compiler like
g++.)
Thanks,
Ranjit.
--
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.tripod.com/