This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Doc PATCH: explain low vs high GIMPLE
- From: Ben Elliston <bje at au1 dot ibm dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Fri, 10 Feb 2006 10:57:56 +1100
- Subject: Doc PATCH: explain low vs high GIMPLE
I thought that this should be more clearly explained in the docs.
Tested with a `make info dvi'. Okay for the trunk?
Ben
2006-02-10 Ben Elliston <bje@au.ibm.com>
* doc/tree-ssa.texi (Interfaces): Describe low vs. high GIMPLE.
Index: doc/tree-ssa.texi
===================================================================
--- doc/tree-ssa.texi (revision 110815)
+++ doc/tree-ssa.texi (working copy)
@@ -132,6 +132,11 @@ convert the front end trees to GIMPLE@.
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