This is the mail archive of the
mailing list for the GCC project.
Re: Higher level RTL issues
- To: Jan Hubicka <jh at suse dot cz>
- Subject: Re: Higher level RTL issues
- From: law at redhat dot com
- Date: Mon, 22 Oct 2001 08:04:07 -0600
- cc: gcc at gcc dot gnu dot org
- Reply-To: law at redhat dot com
In message <20011021194030.G12034@atrey.karlin.mff.cuni.cz>you write:
> > The details of the proof of concept are pretty simple. Remember, we don'
> > have the automatic lowering code, just proof of concepts at this point.
> > For the embedded target I have a series of state variables which indicate
> > whether or not we're working with generic RTL, lowering from generic to
> > target RTL or working with target RTL only.
> > The backend has a set of generic patterns which are only available when t
> > state variable indicates that we are working with generic RTL.
> I've imaginated that w/o patterns at all - just have some easy enought
> definition of "correct RTL", to get rid of the optimizer trying to hit into
> existing pattern, but this sounds sane too.
What Richard and I discussed as a generic set of patterns that would be
included by all ports via a #include or similar mechanism in the md file.