Home My Page Projects Code Snippets Project Openings SML/NJ
Summary Activity Forums Tracker Lists Tasks Docs Surveys News SCM Files

SCM Repository

[smlnj] View of /sml/trunk/src/MLRISC/Doc/latex/future-work.tex
ViewVC logotype

View of /sml/trunk/src/MLRISC/Doc/latex/future-work.tex

Parent Directory Parent Directory | Revision Log Revision Log


Revision 651 - (download) (as text) (annotate)
Thu Jun 1 18:34:03 2000 UTC (19 years, 2 months ago) by monnier
File size: 1294 byte(s)
bring revisions from the vendor branch to the trunk
\section{Future Work}
\subsection{Short Term}

\begin{description}    
\item[Detailed user manual:]
    A detailed user manual describing the interfaces, algorithms, 
    and examples on how to put together code generators.
\item[Support for GC:]
      There is a strong interaction
     with support for GC and global code motion. MLRISC aims at
     providing a generic framework for code generators, and finding
     the right level of information to support GC and global code
     motion is an issue. I think we have several solutions to address
     this that need more evaluation.
\item[Other architectures:] There is the need to port
     to other architectures like the MIPS, and the IA-64. 
\end{description}
\hr
\subsection{Long Term}
\begin{description}
 \item[Predicated VLIW compilation:] Currently, the framework
for predicated VLIW architectures compilation
is incomplete, and contain only one back end (C6)
\item[Other compilers:] I would really like to see some
major compiler effort bootstrapped with an MLRISC backend.
\item[Verification] It is extremely difficult to
debug errors in modules that perform aggressive code
reorganizations. Ideas from formal methods such as typed assembly
language (TAL) or Proof Carrying Code (PCC) are worth investigating.
\end{description}

root@smlnj-gforge.cs.uchicago.edu
ViewVC Help
Powered by ViewVC 1.0.0