This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Loop optimiser upgrade (Was RFC: BB duplication code)
- To: Jan Hubicka <jh at suse dot cz>
- Subject: Re: Loop optimiser upgrade (Was RFC: BB duplication code)
- From: Michael Hayes <m dot hayes at elec dot canterbury dot ac dot nz>
- Date: Sun, 09 Sep 2001 11:56:14 +1200 (NZST)
- Cc: Michael Hayes <m dot hayes at elec dot canterbury dot ac dot nz>, gcc at gcc dot gnu dot org
- References: <20010822202900.D30704@atrey.karlin.mff.cuni.cz> <20010822121440.H29601@redhat.com> <20010822212756.G30704@atrey.karlin.mff.cuni.cz> <20010822130404.K29601@redhat.com> <20010823154400.A4372@atrey.karlin.mff.cuni.cz><15257.37306.220097.483860@ongaonga.elec.canterbury.ac.nz> <20010908180923.I8451@atrey.karlin.mff.cuni.cz>
Jan Hubicka writes:
> What do you think about restructuring it to kind of "loop library"
> as I've mentioned previously?
>
> As we already have code to discover loops, I would love to see everything
> designed in similar way - ie function to create preheaders/landing pads,
> function to discover invariants, function to discover BIVs and implement each
> optimization as separate pass.
Yes, I agree. Each of these modules should be decoupled as much as
possible to simplify the maintenance.
Maybe we should try the unthinkable and have a go at designing the
interfaces first ;-)
Michael.