This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Two problems with gimplify_init_constructor
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: rth at redhat dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 12 Aug 04 17:08:12 EDT
- Subject: Re: Two problems with gimplify_init_constructor
> My concern is the constant pool. You want to be sure that stores to user
> variables don't invalidate them.
Huh?
If you have a machine that references some objects via a constant pool,
we may have a MEM for that constant. Unless we make those in a unique
alias set (a real possibility), an indirect store to the same type would
appear to disallow CSE of that constant.