This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Make alias_sets_conflict_p less conservative
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: matz at suse dot de
- Cc: dberlin at dberlin dot org, gcc at gcc dot gnu dot org, joseph at codesourcery dot com, rguenther at suse dot de
- Date: Wed, 05 Mar 2008 15:42:03 EST
- Subject: Re: [PATCH] Make alias_sets_conflict_p less conservative
- References: <Pine.LNX.4.64.0803042155430.4133@zhemvz.fhfr.qr> <Pine.LNX.4.64.0803051336170.4133@zhemvz.fhfr.qr> <10803051256.AA05161@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0803051452510.4133@zhemvz.fhfr.qr> <10803051426.AA05981@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0803051559450.4133@zhemvz.fhfr.qr> <10803051515.AA06678@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0803051614490.4133@zhemvz.fhfr.qr> <Pine.LNX.4.64.0803051724530.4133@zhemvz.fhfr.qr> <10803051630.AA08112@vlsi1.ultra.nyu.edu> <4aca3dc20803050857k45cccdf6r4c0f8ac3a3b336c6@mail.gmail.com> <10803051924.AA09430@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0803052102210.20583@wotan.suse.de>
> The problem lies in the way how we represent load and store dependencies
> as virtual operands. Conflicts between a pair of mem accesses are not
> evaluated by asking alias_set_conflicts_p() on both accesses, but instead
> via a chain of virtual def and use operands.
But I thought this whole discussion was about a change to
alias_sets_conflict_p. So you've lost me.