summaryrefslogtreecommitdiff
path: root/gcc/doc/gimple.texi
diff options
context:
space:
mode:
authorrwild <rwild@138bc75d-0d04-0410-961f-82ee72b054a4>2010-12-20 07:26:12 +0000
committerrwild <rwild@138bc75d-0d04-0410-961f-82ee72b054a4>2010-12-20 07:26:12 +0000
commitc23d8da9a3ab0081d88623c1f725c77ff08fc4a5 (patch)
treebbeca672c40e18af22fcb37603551094b24bf388 /gcc/doc/gimple.texi
parentab7102895d7be931dcc69fedf8f56ace19438648 (diff)
downloadgcc-c23d8da9a3ab0081d88623c1f725c77ff08fc4a5.tar.gz
doc: @var fixes.
gcc/: * doc/cppopts.texi: Use @var when appropriate. * doc/extend.texi (Structure-Packing Pragmas): Likewise. * doc/gimple.texi (Logical Operators) (Adding a new GIMPLE statement code): Likewise. * doc/invoke.texi (Target Options, Precompiled Headers): Likewise. * doc/plugins.texi (Plugins): Likewise. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@168081 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc/gimple.texi')
-rw-r--r--gcc/doc/gimple.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/doc/gimple.texi b/gcc/doc/gimple.texi
index 5e217a772da..e8cecd75d3c 100644
--- a/gcc/doc/gimple.texi
+++ b/gcc/doc/gimple.texi
@@ -635,7 +635,7 @@ access the operands.
When adding a new operand to a gimple statement, the operand will
be validated according to what each tuple accepts in its operand
vector. These predicates are called by the
-@code{gimple_<name>_set_...()}. Each tuple will use one of the
+@code{gimple_@var{name}_set_...()}. Each tuple will use one of the
following predicates (Note, this list is not exhaustive):
@deftypefn {GIMPLE function} is_gimple_operand (tree t)
@@ -2497,7 +2497,7 @@ in @code{gimple.c}.
You will probably want to create a function to build the new
gimple statement in @code{gimple.c}. The function should be called
-@code{gimple_build_<@code{NEW_TUPLE_NAME}>}, and should return the new tuple
+@code{gimple_build_@var{new-tuple-name}}, and should return the new tuple
of type gimple.
If your new statement requires accessors for any members or