This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: df.c and partial writes/REG_EQUAL notes
- To: Michael Matz <matzmich at cs dot tu-berlin dot de>
- Subject: Re: df.c and partial writes/REG_EQUAL notes
- From: Jan Hubicka <jh at suse dot cz>
- Date: Sat, 29 Sep 2001 15:34:47 +0200
- Cc: Jan Hubicka <jh at suse dot cz>, Daniel Berlin <dan at cgsoftware dot com>, gcc at gcc dot gnu dot org, rth at cygnus dot com, m dot hayes at elec dot canterbury dot ac dot nz
- References: <20010925165908.G13734@atrey.karlin.mff.cuni.cz> <Pine.GSO.4.33.0109281917070.28239-100000@platon>
> Right. But I'm nearly sure, that I'll not use df.c at all. One reason
> is, that the allocator also must collect the constraints for all reg
> references (or better said for all operands), which would need a second
> pass over all insns if I would use df.* for collecting the references
> itself. Note that even currently df.* is only used for collecting all
> register references by the allocator. Esp. it's not used for building the
> use/def-chains. (But, Daniels rematerialization uses the chains from
> df.*)
Can't you actually use the df.c framework, but just different method to note
the defs/refs (by browsing the operands)?
I guess the code to propagate the chains and datastructures still can be
shared with some care..
Honza