This is the mail archive of the
mailing list for the GCC project.
Re: GCC Status Report (2004-03-09)
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: ebotcazou at libertysurf dot fr
- Cc: gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Fri, 19 Mar 04 13:44:20 EST
- Subject: Re: GCC Status Report (2004-03-09)
Before I start thinking about a replacement, I'd like to understand
what I'll be trying the replace. It appears that no-bo-dy can tell
what is the purpose of RTX_UNCHANGING_P.
Well I can tell you the *purpose*, but if you want the *definition*, that's
something else entirely.
The original idea was to separate objects that we knew could not be
modified by stores, like constant pool objects.
Then, at some later point, it was realized that we could also optimize by
allowing a *single* store to "constant" object to initialize it, but things
started rapidly going downhill once we started to take more and more
advantage of that property.