1 From 54907dbd122d6e4661b9583247e5574b9349c130 Mon Sep 17 00:00:00 2001
2 From: gerald <gerald@138bc75d-0d04-0410-961f-82ee72b054a4>
3 Date: Sun, 17 Apr 2011 21:59:00 +0000
4 Subject: [PATCH 135/200] * doc/passes.texi: Fill crossref nodes.
6 git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/gcc-4_6-branch@172621 138bc75d-0d04-0410-961f-82ee72b054a4
8 index 7453821..e5ee8c3 100644
9 --- a/gcc/doc/passes.texi
10 +++ b/gcc/doc/passes.texi
12 -@c markers: CROSSREF BUG TODO
15 @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
16 @c 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010
17 @@ -32,7 +32,7 @@ where near complete.
18 The language front end is invoked only once, via
19 @code{lang_hooks.parse_file}, to parse the entire input. The language
20 front end may use any intermediate language representation deemed
21 -appropriate. The C front end uses GENERIC trees (CROSSREF), plus
22 +appropriate. The C front end uses GENERIC trees (@pxref{GENERIC}), plus
23 a double handful of language specific tree codes defined in
24 @file{c-common.def}. The Fortran front end uses a completely different
25 private representation.
26 @@ -46,10 +46,9 @@ private representation.
27 At some point the front end must translate the representation used in the
28 front end to a representation understood by the language-independent
29 portions of the compiler. Current practice takes one of two forms.
30 -The C front end manually invokes the gimplifier (CROSSREF) on each function,
31 +The C front end manually invokes the gimplifier (@pxref{GIMPLE}) on each function,
32 and uses the gimplifier callbacks to convert the language-specific tree
33 -nodes directly to GIMPLE (CROSSREF) before passing the function off to
35 +nodes directly to GIMPLE before passing the function off to be compiled.
36 The Fortran front end converts from a private representation to GENERIC,
37 which is later lowered to GIMPLE when the function is compiled. Which
38 route to choose probably depends on how well GENERIC (plus extensions)
39 @@ -111,11 +110,10 @@ definitions immediately or queue them for later processing.
41 @dfn{Gimplification} is a whimsical term for the process of converting
42 the intermediate representation of a function into the GIMPLE language
43 -(CROSSREF). The term stuck, and so words like ``gimplification'',
44 +(@pxref{GIMPLE}). The term stuck, and so words like ``gimplification'',
45 ``gimplify'', ``gimplifier'' and the like are sprinkled throughout this
49 While a front end may certainly choose to generate GIMPLE directly if
50 it chooses, this can be a moderately complex process unless the
51 intermediate language used by the front end is already fairly simple.
