This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Using the DFA scheduler for a new VLIW port
- From: law at redhat dot com
- To: Dan Towner <dant at picochip dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 07 Jun 2002 09:34:03 -0600
- Subject: Re: Using the DFA scheduler for a new VLIW port
- Reply-to: law at redhat dot com
In message <3D00CF2A.251ED15D@picochip.com>, Dan Towner writes:
> 1) I plan on looking at how other ports use the DFA scheduler. Doing a
> quick grep through the latest dfa-branch revision, it seems that only
> the sh/pa/sparc ports currently use the DFA scheduler, but the web page
> mentions IA64, Fujitsu, Pentium, Alpha and others. Where are the other
> sources? In particular, I am after a good VLIW port.
The DFA branch is dead and no longer being used. The DFA code is in the
mainline sources. You'll find the Alpha and Pentium descriptions in the
mainline sources.
Some descriptions have been posted to the gcc-patches list for comments
(the PPC family, Athlon)
Some are still inside Red Hat waiting to be contributed (MIPS, FRV).
One is in my local source tree (PPro/P2/P3).
Probably the next one to come out of Red Hat will be the FRV which is
a VLIW target.
> 2) My port is currently based upon gcc 3.1, but hasn't yet been
> officially integrated into the gcc CVS. Would there be complications
> associated with continuing my port using the dfa-branch, or should I
> make an official contribution first?
You're best off getting your code into the mainline sources as the DFA
branch isn't being used for development anymore.
jeff