|a practical UNCOL firstname.lastname@example.org (Ralph Johnson) (1989-05-10)|
|Re: a practical UNCOL email@example.com (David Keppel) (1989-05-13)|
|Re: a practical UNCOL ima!ico.ISC.com!rcd (Dick Dunn) (1989-05-17)|
|a practical UNCOL firstname.lastname@example.org (Ralph Johnson) (1989-05-18)|
|From:||David Keppel <email@example.com>|
|Keywords:||compiler ir rtl dag code generation|
|Date:||13 May 89 12:57:26 GMT|
|Organization:||U of Washington, Computer Science, Seattle|
Ralph Johnson <firstname.lastname@example.org> writes:
>[Fraser/Davidson RTL IR]
>[moderator: isn't that what gcc uses (successfully)?]
My compilers prof has pointed out to me that matching for
optimizations and instruction selection in an RTL (Fraser/Davidson,
IBM PL.801) is a special case of matching in a DAG (directed acyclic
graph) -structured ir (Graham/Glanville/Henry).
One important distinction is that all matching in an RTL is done at
the level of things that usually look like RISC machine instructions.
Thus the code quality is better when there is a good match between the
instructions in the machine-independent RTL and the instructions in
the physical hardware.
;-D on ( The code degenerator ) Pardo
Return to the
Search the comp.compilers archives again.