From 9c603f8f1ea0910836a42a0f6d0207626d8bcbef Mon Sep 17 00:00:00 2001 From: Ben Elliston Date: Sun, 19 Feb 2006 23:09:26 +0000 Subject: * doc/tree-ssa.texi (Interfaces): Describe low vs. high GIMPLE. From-SVN: r111286 --- gcc/doc/tree-ssa.texi | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'gcc/doc/tree-ssa.texi') diff --git a/gcc/doc/tree-ssa.texi b/gcc/doc/tree-ssa.texi index 77a2f0a..ef2bb8a 100644 --- a/gcc/doc/tree-ssa.texi +++ b/gcc/doc/tree-ssa.texi @@ -132,6 +132,11 @@ convert the front end trees to GIMPLE@. Usually such a hook will involve much of the same code for expanding front end trees to RTL@. This function can return fully lowered GIMPLE, or it can return GENERIC trees and let the main gimplifier lower them the rest of the way; this is often simpler. +GIMPLE that is not fully lowered is known as ``high GIMPLE'' and +consists of the IL before the pass @code{pass_lower_cf}. High GIMPLE +still contains lexical scopes and nested expressions, while low GIMPLE +exposes all of the implicit jumps for control expressions like +@code{COND_EXPR}. The C and C++ front ends currently convert directly from front end trees to GIMPLE, and hand that off to the back end rather than first -- cgit v1.1