This is the mail archive of the gcc-patches@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: Patch: treat sibling calls as non-const


On Thu, Sep 11, 2003 at 12:54:27PM -0700, Dale Johannesen wrote:
> +            FIXME:  A better, but much more invasive, way to fix this
> +              is to establish a connection between the call and the
> +              parameters, so hoisted stores don't get deleted.  There
> +              is no good reason they shouldn't get hoisted.  */

The way to do this is to have these memories attached to the
CALL_FUNCTION_USAGE list as USEs.  I thought we already did that.
Am I misremembering, or are we not checking it somewhere we ought?


r~


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