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: Andreas Schwab <schwab at suse dot de>
- To: "Dave Korn" <dk at artimi dot com>
- Cc: "'Gabriel Dos Reis'" <gdr at cs dot tamu dot edu>,"'Phil Edwards'" <phil at codesourcery dot com>,"'Zack Weinberg'" <zack at codesourcery dot com>,"'Geoffrey Keating'" <geoffk at apple dot com>,"'Ranjit Mathew'" <rmathew at gmail dot com>, <gcc at gcc dot gnu dot org>
- Date: Wed, 13 Oct 2004 12:09:09 +0200
- Subject: Re: Compiling GCC With a C++ Compiler (g++)
- References: <NUTMEGgh8qWO8OsmOP00000041e@NUTMEG.CAM.ARTIMI.COM>
"Dave Korn" <dk@artimi.com> writes:
>> -----Original Message-----
>> From: gcc-owner On Behalf Of Gabriel Dos Reis
>> Sent: 13 October 2004 04:47
>
>> Phil Edwards writes:
>>
>> [...]
>>
>> | particular place. Since member init-lists aren't available
>> for STRING_CST,
>> | we have to cast away the const in build_string
>>
>> which is undefined behaviour by C rules (and C++ too).
>
> I'll bet alias analysis just loves it too. Wouldn't using tricks like
> this lead to a situation in the future (if and) when there's full IPA in gcc
> and it can't bootstrap itself reliably any more?
In C you are always allowed to cast away const and write through the
resulting lvalue as long as the underlying object is not read-only.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."