This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Q: C++ FE emitting assignments to global read-only symbols?

From: Mark Mitchell <mark at codesourcery dot com>
To: Daniel Berlin <dberlin at dberlin dot org>
Cc: Diego Novillo <dnovillo at redhat dot com>, gcc at gcc dot gnu dot org
Date: Fri, 08 Apr 2005 16:40:01 -0700
Subject: Re: Q: C++ FE emitting assignments to global read-only symbols?
Organization: CodeSourcery, LLC
References: <20050408164525.GA17793@topo.toronto.redhat.com> <1112979734.5606.10.camel@linux-009002218068.watson.ibm.com>

Daniel Berlin wrote:

Your transform is correct.
The FE is not. The variable is not read only.
It is write once, then read-only.

Diego, your analysis is exactly correct about what is happenning.

I agree, in principle. The C++ FE should not set TREE_READONLY on variables that require dynanmic initialization. Until now, that's not been a problem, and it does result in better code. But, it's now becoming a problem, and we have others way to get good code coming down the pipe.

I do think the C++ FE needs fixing before Diego's change gets merged, though. I can make the change, but not instantly. If someone files a PR, and assigns to me, I'll get to it at some not-too-distant point.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304

Follow-Ups:
- Re: Q: C++ FE emitting assignments to global read-only symbols?
  - From: Dale Johannesen
- Re: Q: C++ FE emitting assignments to global read-only symbols?
  - From: Diego Novillo

References:
- Q: C++ FE emitting assignments to global read-only symbols?
  - From: Diego Novillo
- Re: Q: C++ FE emitting assignments to global read-only symbols?
  - From: Daniel Berlin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]