From: Gabriel Dos Reis <gdr@cs.tamu.edu>
To: Andreas Schwab <schwab@suse.de>
Cc: "Dave Korn" <dk@artimi.com>,
"'Phil Edwards'" <phil@codesourcery.com>,
"'Zack Weinberg'" <zack@codesourcery.com>,
"'Geoffrey Keating'" <geoffk@apple.com>,
"'Ranjit Mathew'" <rmathew@gmail.com>, <gcc@gcc.gnu.org>
Subject: Re: Compiling GCC With a C++ Compiler (g++)
Date: Wed, 13 Oct 2004 13:29:00 -0000 [thread overview]
Message-ID: <m3llea6a6n.fsf@merlin.cs.tamu.edu> (raw)
In-Reply-To: <jeoej7x73u.fsf@sykes.suse.de>
Andreas Schwab <schwab@suse.de> writes:
| "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.
That is not true.
If you can a strcture with const-qualified field, you can modify any
part, except that field. (I'm talking of C here).
-- Gaby
next prev parent reply other threads:[~2004-10-13 13:04 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 9:53 Ranjit Mathew
2004-10-12 10:06 ` Ranjit Mathew
2004-10-12 13:17 ` Gabriel Dos Reis
2004-10-12 21:15 ` Geoffrey Keating
2004-10-12 23:00 ` Gabriel Dos Reis
2004-10-12 23:23 ` Zack Weinberg
2004-10-13 2:53 ` Phil Edwards
2004-10-13 6:24 ` Gabriel Dos Reis
2004-10-13 10:57 ` Andreas Schwab
2004-10-13 13:16 ` Gabriel Dos Reis
2004-10-13 13:56 ` Andreas Schwab
2004-10-13 14:22 ` Gabriel Dos Reis
2004-10-13 15:06 ` Andreas Schwab
2004-10-13 15:22 ` Gabriel Dos Reis
2004-10-13 15:33 ` Andreas Schwab
2004-10-13 18:20 ` Gabriel Dos Reis
2004-10-13 19:09 ` Andreas Schwab
2004-10-13 11:47 ` Dave Korn
2004-10-13 12:24 ` Andreas Schwab
2004-10-13 13:29 ` Gabriel Dos Reis [this message]
2004-10-13 14:10 ` Andreas Schwab
2004-10-13 14:30 ` Dave Korn
2004-10-13 14:50 ` Dave Korn
2004-10-13 18:25 ` Andreas Schwab
2004-10-13 15:04 ` Joseph S. Myers
2004-10-13 17:01 ` Dave Korn
2004-10-13 21:16 ` Geoffrey Keating
2004-10-14 13:26 ` Dave Korn
2004-10-14 13:32 ` Gabriel Dos Reis
2004-10-14 18:40 ` Andreas Schwab
2004-10-14 18:48 ` Gabriel Dos Reis
2004-10-14 20:33 ` Geoffrey Keating
2004-10-14 20:19 ` Geoffrey Keating
2004-10-15 12:03 ` Kai Henningsen
2004-10-13 14:53 ` Gabriel Dos Reis
2004-10-13 15:46 ` Gabriel Dos Reis
2004-10-13 19:41 ` Matt Austern
2004-10-13 20:29 ` Andreas Schwab
2004-10-13 20:41 ` Matt Austern
2004-10-13 20:58 ` Phil Edwards
2004-10-13 9:23 ` Ranjit Mathew
2004-10-13 13:09 ` Ranjit Mathew
2004-10-13 19:13 ` Richard Henderson
2004-10-13 21:55 ` Gabriel Dos Reis
2004-10-13 13:29 ` Gabriel Dos Reis
2004-10-13 5:49 ` Gabriel Dos Reis
2004-10-13 9:19 ` Zack Weinberg
2004-10-13 13:45 ` Gabriel Dos Reis
2004-10-13 20:39 ` Geoffrey Keating
2004-10-13 21:45 ` Gabriel Dos Reis
2004-10-13 22:15 ` Geoffrey Keating
2004-10-13 22:24 ` Gabriel Dos Reis
2004-10-13 22:53 ` Joseph S. Myers
2004-10-13 23:19 ` Geoffrey Keating
2004-10-14 0:21 ` Gabriel Dos Reis
2004-10-14 6:04 ` Andreas Schwab
2004-10-14 7:10 ` Gabriel Dos Reis
2004-10-14 11:29 ` Andreas Schwab
2004-10-14 13:06 ` Gabriel Dos Reis
2004-10-14 18:37 ` Andreas Schwab
2004-10-15 12:48 ` Kai Henningsen
2004-10-13 3:47 Steven L. Zook
2004-10-13 7:26 ` Gabriel Dos Reis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3llea6a6n.fsf@merlin.cs.tamu.edu \
--to=gdr@cs.tamu.edu \
--cc=dk@artimi.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@apple.com \
--cc=phil@codesourcery.com \
--cc=rmathew@gmail.com \
--cc=schwab@suse.de \
--cc=zack@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).