1 ===================================
2 Customizing LLVMC: Reference Manual
3 ===================================
5 This file was automatically generated by rst2html.
6 Please do not edit directly!
7 The ReST source lives in the directory 'tools/llvmc/doc'.
13 <div class="doc_author">
14 <p>Written by <a href="mailto:foldr@codedgers.com">Mikhail Glushenkov</a></p>
20 LLVMC is a generic compiler driver, designed to be customizable and
21 extensible. It plays the same role for LLVM as the ``gcc`` program
22 does for GCC - LLVMC's job is essentially to transform a set of input
23 files into a set of targets depending on configuration rules and user
24 options. What makes LLVMC different is that these transformation rules
25 are completely customizable - in fact, LLVMC knows nothing about the
26 specifics of transformation (even the command-line options are mostly
27 not hard-coded) and regards the transformation structure as an
28 abstract graph. The structure of this graph is completely determined
29 by plugins, which can be either statically or dynamically linked. This
30 makes it possible to easily adapt LLVMC for other purposes - for
31 example, as a build tool for game resources.
33 Because LLVMC employs TableGen_ as its configuration language, you
34 need to be familiar with it to customize LLVMC.
36 .. _TableGen: http://llvm.org/docs/TableGenFundamentals.html
42 LLVMC tries hard to be as compatible with ``gcc`` as possible,
43 although there are some small differences. Most of the time, however,
44 you shouldn't be able to notice them::
46 $ # This works as expected:
47 $ llvmc -O3 -Wall hello.cpp
51 One nice feature of LLVMC is that one doesn't have to distinguish between
52 different compilers for different languages (think ``g++`` vs. ``gcc``) - the
53 right toolchain is chosen automatically based on input language names (which
54 are, in turn, determined from file extensions). If you want to force files
55 ending with ".c" to compile as C++, use the ``-x`` option, just like you would
58 $ # hello.c is really a C++ file
59 $ llvmc -x c++ hello.c
63 On the other hand, when using LLVMC as a linker to combine several C++
64 object files you should provide the ``--linker`` option since it's
65 impossible for LLVMC to choose the right linker in that case::
69 [A lot of link-time errors skipped]
70 $ llvmc --linker=c++ hello.o
74 By default, LLVMC uses ``llvm-gcc`` to compile the source code. It is also
75 possible to choose the ``clang`` compiler with the ``-clang`` option.
81 LLVMC has some built-in options that can't be overridden in the
82 configuration libraries:
84 * ``-o FILE`` - Output file name.
86 * ``-x LANGUAGE`` - Specify the language of the following input files
87 until the next -x option.
89 * ``-load PLUGIN_NAME`` - Load the specified plugin DLL. Example:
90 ``-load $LLVM_DIR/Release/lib/LLVMCSimple.so``.
92 * ``-v`` - Enable verbose mode, i.e. print out all executed commands.
94 * ``--save-temps`` - Write temporary files to the current directory and do not
95 delete them on exit. This option can also take an argument: the
96 ``--save-temps=obj`` switch will write files into the directory specified with
97 the ``-o`` option. The ``--save-temps=cwd`` and ``--save-temps`` switches are
98 both synonyms for the default behaviour.
100 * ``--temp-dir DIRECTORY`` - Store temporary files in the given directory. This
101 directory is deleted on exit unless ``--save-temps`` is specified. If
102 ``--save-temps=obj`` is also specified, ``--temp-dir`` is given the
105 * ``--check-graph`` - Check the compilation for common errors like mismatched
106 output/input language names, multiple default edges and cycles. Because of
107 plugins, these checks can't be performed at compile-time. Exit with code zero
108 if no errors were found, and return the number of found errors
109 otherwise. Hidden option, useful for debugging LLVMC plugins.
111 * ``--view-graph`` - Show a graphical representation of the compilation graph
112 and exit. Requires that you have ``dot`` and ``gv`` programs installed. Hidden
113 option, useful for debugging LLVMC plugins.
115 * ``--write-graph`` - Write a ``compilation-graph.dot`` file in the current
116 directory with the compilation graph description in Graphviz format (identical
117 to the file used by the ``--view-graph`` option). The ``-o`` option can be
118 used to set the output file name. Hidden option, useful for debugging LLVMC
121 * ``--help``, ``--help-hidden``, ``--version`` - These options have
122 their standard meaning.
124 Compiling LLVMC plugins
125 =======================
127 It's easiest to start working on your own LLVMC plugin by copying the
128 skeleton project which lives under ``$LLVMC_DIR/plugins/Simple``::
130 $ cd $LLVMC_DIR/plugins
131 $ cp -r Simple MyPlugin
134 Makefile PluginMain.cpp Simple.td
136 As you can see, our basic plugin consists of only two files (not
137 counting the build script). ``Simple.td`` contains TableGen
138 description of the compilation graph; its format is documented in the
139 following sections. ``PluginMain.cpp`` is just a helper file used to
140 compile the auto-generated C++ code produced from TableGen source. It
141 can also contain hook definitions (see `below`__).
145 The first thing that you should do is to change the ``LLVMC_PLUGIN``
146 variable in the ``Makefile`` to avoid conflicts (since this variable
147 is used to name the resulting library)::
149 LLVMC_PLUGIN=MyPlugin
151 It is also a good idea to rename ``Simple.td`` to something less
154 $ mv Simple.td MyPlugin.td
156 To build your plugin as a dynamic library, just ``cd`` to its source
157 directory and run ``make``. The resulting file will be called
158 ``plugin_llvmc_$(LLVMC_PLUGIN).$(DLL_EXTENSION)`` (in our case,
159 ``plugin_llvmc_MyPlugin.so``). This library can be then loaded in with the
160 ``-load`` option. Example::
162 $ cd $LLVMC_DIR/plugins/Simple
164 $ llvmc -load $LLVM_DIR/Release/lib/plugin_llvmc_Simple.so
166 Compiling standalone LLVMC-based drivers
167 ========================================
169 By default, the ``llvmc`` executable consists of a driver core plus several
170 statically linked plugins (``Base`` and ``Clang`` at the moment). You can
171 produce a standalone LLVMC-based driver executable by linking the core with your
172 own plugins. The recommended way to do this is by starting with the provided
173 ``Skeleton`` example (``$LLVMC_DIR/example/Skeleton``)::
175 $ cd $LLVMC_DIR/example/
176 $ cp -r Skeleton mydriver
182 If you're compiling LLVM with different source and object directories, then you
183 must perform the following additional steps before running ``make``::
185 # LLVMC_SRC_DIR = $LLVM_SRC_DIR/tools/llvmc/
186 # LLVMC_OBJ_DIR = $LLVM_OBJ_DIR/tools/llvmc/
187 $ cp $LLVMC_SRC_DIR/example/mydriver/Makefile \
188 $LLVMC_OBJ_DIR/example/mydriver/
189 $ cd $LLVMC_OBJ_DIR/example/mydriver
192 Another way to do the same thing is by using the following command::
195 $ make LLVMC_BUILTIN_PLUGINS=MyPlugin LLVMC_BASED_DRIVER_NAME=mydriver
197 This works with both srcdir == objdir and srcdir != objdir, but assumes that the
198 plugin source directory was placed under ``$LLVMC_DIR/plugins``.
200 Sometimes, you will want a 'bare-bones' version of LLVMC that has no
201 built-in plugins. It can be compiled with the following command::
204 $ make LLVMC_BUILTIN_PLUGINS=""
207 Customizing LLVMC: the compilation graph
208 ========================================
210 Each TableGen configuration file should include the common
213 include "llvm/CompilerDriver/Common.td"
215 Internally, LLVMC stores information about possible source
216 transformations in form of a graph. Nodes in this graph represent
217 tools, and edges between two nodes represent a transformation path. A
218 special "root" node is used to mark entry points for the
219 transformations. LLVMC also assigns a weight to each edge (more on
220 this later) to choose between several alternative edges.
222 The definition of the compilation graph (see file
223 ``plugins/Base/Base.td`` for an example) is just a list of edges::
225 def CompilationGraph : CompilationGraph<[
226 Edge<"root", "llvm_gcc_c">,
227 Edge<"root", "llvm_gcc_assembler">,
230 Edge<"llvm_gcc_c", "llc">,
231 Edge<"llvm_gcc_cpp", "llc">,
234 OptionalEdge<"llvm_gcc_c", "opt", (case (switch_on "opt"),
236 OptionalEdge<"llvm_gcc_cpp", "opt", (case (switch_on "opt"),
240 OptionalEdge<"llvm_gcc_assembler", "llvm_gcc_cpp_linker",
241 (case (input_languages_contain "c++"), (inc_weight),
242 (or (parameter_equals "linker", "g++"),
243 (parameter_equals "linker", "c++")), (inc_weight))>,
248 As you can see, the edges can be either default or optional, where
249 optional edges are differentiated by an additional ``case`` expression
250 used to calculate the weight of this edge. Notice also that we refer
251 to tools via their names (as strings). This makes it possible to add
252 edges to an existing compilation graph in plugins without having to
253 know about all tool definitions used in the graph.
255 The default edges are assigned a weight of 1, and optional edges get a
256 weight of 0 + 2*N where N is the number of tests that evaluated to
257 true in the ``case`` expression. It is also possible to provide an
258 integer parameter to ``inc_weight`` and ``dec_weight`` - in this case,
259 the weight is increased (or decreased) by the provided value instead
260 of the default 2. It is also possible to change the default weight of
261 an optional edge by using the ``default`` clause of the ``case``
264 When passing an input file through the graph, LLVMC picks the edge
265 with the maximum weight. To avoid ambiguity, there should be only one
266 default edge between two nodes (with the exception of the root node,
267 which gets a special treatment - there you are allowed to specify one
268 default edge *per language*).
270 When multiple plugins are loaded, their compilation graphs are merged
271 together. Since multiple edges that have the same end nodes are not
272 allowed (i.e. the graph is not a multigraph), an edge defined in
273 several plugins will be replaced by the definition from the plugin
274 that was loaded last. Plugin load order can be controlled by using the
275 plugin priority feature described above.
277 To get a visual representation of the compilation graph (useful for
278 debugging), run ``llvmc --view-graph``. You will need ``dot`` and
279 ``gsview`` installed for this to work properly.
284 Command-line options that the plugin supports are defined by using an
287 def Options : OptionList<[
288 (switch_option "E", (help "Help string")),
289 (alias_option "quiet", "q")
293 As you can see, the option list is just a list of DAGs, where each DAG
294 is an option description consisting of the option name and some
295 properties. A plugin can define more than one option list (they are
296 all merged together in the end), which can be handy if one wants to
297 separate option groups syntactically.
299 * Possible option types:
301 - ``switch_option`` - a simple boolean switch without arguments, for example
302 ``-O2`` or ``-time``. At most one occurrence is allowed.
304 - ``parameter_option`` - option that takes one argument, for example
305 ``-std=c99``. It is also allowed to use spaces instead of the equality
306 sign: ``-std c99``. At most one occurrence is allowed.
308 - ``parameter_list_option`` - same as the above, but more than one option
309 occurence is allowed.
311 - ``prefix_option`` - same as the parameter_option, but the option name and
312 argument do not have to be separated. Example: ``-ofile``. This can be also
313 specified as ``-o file``; however, ``-o=file`` will be parsed incorrectly
314 (``=file`` will be interpreted as option value). At most one occurrence is
317 - ``prefix_list_option`` - same as the above, but more than one occurence of
318 the option is allowed; example: ``-lm -lpthread``.
320 - ``alias_option`` - a special option type for creating aliases. Unlike other
321 option types, aliases are not allowed to have any properties besides the
322 aliased option name. Usage example: ``(alias_option "preprocess", "E")``
325 * Possible option properties:
327 - ``help`` - help string associated with this option. Used for ``--help``
330 - ``required`` - this option must be specified exactly once (or, in case of
331 the list options without the ``multi_val`` property, at least
332 once). Incompatible with ``zero_or_one`` and ``one_or_more``.
334 - ``one_or_more`` - the option must be specified at least one time. Useful
335 only for list options in conjunction with ``multi_val``; for ordinary lists
336 it is synonymous with ``required``. Incompatible with ``required`` and
339 - ``optional`` - the option can be specified zero or one times. Useful only
340 for list options in conjunction with ``multi_val``. Incompatible with
341 ``required`` and ``one_or_more``.
343 - ``hidden`` - the description of this option will not appear in
344 the ``--help`` output (but will appear in the ``--help-hidden``
347 - ``really_hidden`` - the option will not be mentioned in any help
350 - ``comma_separated`` - Indicates that any commas specified for an option's
351 value should be used to split the value up into multiple values for the
352 option. This property is valid only for list options. In conjunction with
353 ``forward_value`` can be used to implement option forwarding in style of
356 - ``multi_val n`` - this option takes *n* arguments (can be useful in some
357 special cases). Usage example: ``(parameter_list_option "foo", (multi_val
358 3))``; the command-line syntax is '-foo a b c'. Only list options can have
359 this attribute; you can, however, use the ``one_or_more``, ``optional``
360 and ``required`` properties.
362 - ``init`` - this option has a default value, either a string (if it is a
363 parameter), or a boolean (if it is a switch; as in C++, boolean constants
364 are called ``true`` and ``false``). List options can't have ``init``
366 Usage examples: ``(switch_option "foo", (init true))``; ``(prefix_option
367 "bar", (init "baz"))``.
369 - ``extern`` - this option is defined in some other plugin, see `below`__.
378 Sometimes, when linking several plugins together, one plugin needs to
379 access options defined in some other plugin. Because of the way
380 options are implemented, such options must be marked as
381 ``extern``. This is what the ``extern`` option property is
385 (switch_option "E", (extern))
388 If an external option has additional attributes besides 'extern', they are
389 ignored. See also the section on plugin `priorities`__.
395 Conditional evaluation
396 ======================
398 The 'case' construct is the main means by which programmability is
399 achieved in LLVMC. It can be used to calculate edge weights, program
400 actions and modify the shell commands to be executed. The 'case'
401 expression is designed after the similarly-named construct in
402 functional languages and takes the form ``(case (test_1), statement_1,
403 (test_2), statement_2, ... (test_N), statement_N)``. The statements
404 are evaluated only if the corresponding tests evaluate to true.
408 // Edge weight calculation
410 // Increases edge weight by 5 if "-A" is provided on the
411 // command-line, and by 5 more if "-B" is also provided.
413 (switch_on "A"), (inc_weight 5),
414 (switch_on "B"), (inc_weight 5))
417 // Tool command line specification
419 // Evaluates to "cmdline1" if the option "-A" is provided on the
420 // command line; to "cmdline2" if "-B" is provided;
421 // otherwise to "cmdline3".
424 (switch_on "A"), "cmdline1",
425 (switch_on "B"), "cmdline2",
426 (default), "cmdline3")
428 Note the slight difference in 'case' expression handling in contexts
429 of edge weights and command line specification - in the second example
430 the value of the ``"B"`` switch is never checked when switch ``"A"`` is
431 enabled, and the whole expression always evaluates to ``"cmdline1"`` in
434 Case expressions can also be nested, i.e. the following is legal::
436 (case (switch_on "E"), (case (switch_on "o"), ..., (default), ...)
439 You should, however, try to avoid doing that because it hurts
440 readability. It is usually better to split tool descriptions and/or
441 use TableGen inheritance instead.
443 * Possible tests are:
445 - ``switch_on`` - Returns true if a given command-line switch is provided by
446 the user. Can be given a list as argument, in that case ``(switch_on ["foo",
447 "bar", "baz"])`` is equivalent to ``(and (switch_on "foo"), (switch_on
448 "bar"), (switch_on "baz"))``.
449 Example: ``(switch_on "opt")``.
451 - ``any_switch_on`` - Given a list of switch options, returns true if any of
452 the switches is turned on.
453 Example: ``(any_switch_on ["foo", "bar", "baz"])`` is equivalent to ``(or
454 (switch_on "foo"), (switch_on "bar"), (switch_on "baz"))``.
456 - ``parameter_equals`` - Returns true if a command-line parameter equals
458 Example: ``(parameter_equals "W", "all")``.
460 - ``element_in_list`` - Returns true if a command-line parameter
461 list contains a given value.
462 Example: ``(element_in_list "l", "pthread")``.
464 - ``input_languages_contain`` - Returns true if a given language
465 belongs to the current input language set.
466 Example: ``(input_languages_contain "c++")``.
468 - ``in_language`` - Evaluates to true if the input file language is equal to
469 the argument. At the moment works only with ``cmd_line`` and ``actions`` (on
471 Example: ``(in_language "c++")``.
473 - ``not_empty`` - Returns true if a given option (which should be either a
474 parameter or a parameter list) is set by the user. Like ``switch_on``, can
475 be also given a list as argument.
476 Example: ``(not_empty "o")``.
478 - ``any_not_empty`` - Returns true if ``not_empty`` returns true for any of
479 the options in the list.
480 Example: ``(any_not_empty ["foo", "bar", "baz"])`` is equivalent to ``(or
481 (not_empty "foo"), (not_empty "bar"), (not_empty "baz"))``.
483 - ``empty`` - The opposite of ``not_empty``. Equivalent to ``(not (not_empty
484 X))``. Provided for convenience. Can be given a list as argument.
486 - ``any_not_empty`` - Returns true if ``not_empty`` returns true for any of
487 the options in the list.
488 Example: ``(any_empty ["foo", "bar", "baz"])`` is equivalent to ``(not (and
489 (not_empty "foo"), (not_empty "bar"), (not_empty "baz")))``.
491 - ``single_input_file`` - Returns true if there was only one input file
492 provided on the command-line. Used without arguments:
493 ``(single_input_file)``.
495 - ``multiple_input_files`` - Equivalent to ``(not (single_input_file))`` (the
496 case of zero input files is considered an error).
498 - ``default`` - Always evaluates to true. Should always be the last
499 test in the ``case`` expression.
501 - ``and`` - A standard binary logical combinator that returns true iff all of
502 its arguments return true. Used like this: ``(and (test1), (test2),
503 ... (testN))``. Nesting of ``and`` and ``or`` is allowed, but not
506 - ``or`` - A binary logical combinator that returns true iff any of its
507 arguments returns true. Example: ``(or (test1), (test2), ... (testN))``.
509 - ``not`` - Standard unary logical combinator that negates its
510 argument. Example: ``(not (or (test1), (test2), ... (testN)))``.
514 Writing a tool description
515 ==========================
517 As was said earlier, nodes in the compilation graph represent tools,
518 which are described separately. A tool definition looks like this
519 (taken from the ``include/llvm/CompilerDriver/Tools.td`` file)::
521 def llvm_gcc_cpp : Tool<[
523 (out_language "llvm-assembler"),
524 (output_suffix "bc"),
525 (cmd_line "llvm-g++ -c $INFILE -o $OUTFILE -emit-llvm"),
529 This defines a new tool called ``llvm_gcc_cpp``, which is an alias for
530 ``llvm-g++``. As you can see, a tool definition is just a list of
531 properties; most of them should be self-explanatory. The ``sink``
532 property means that this tool should be passed all command-line
533 options that aren't mentioned in the option list.
535 The complete list of all currently implemented tool properties follows.
537 * Possible tool properties:
539 - ``in_language`` - input language name. Can be either a string or a
540 list, in case the tool supports multiple input languages.
542 - ``out_language`` - output language name. Multiple output languages are not
545 - ``output_suffix`` - output file suffix. Can also be changed
546 dynamically, see documentation on actions.
548 - ``cmd_line`` - the actual command used to run the tool. You can
549 use ``$INFILE`` and ``$OUTFILE`` variables, output redirection
550 with ``>``, hook invocations (``$CALL``), environment variables
551 (via ``$ENV``) and the ``case`` construct.
553 - ``join`` - this tool is a "join node" in the graph, i.e. it gets a
554 list of input files and joins them together. Used for linkers.
556 - ``sink`` - all command-line options that are not handled by other
557 tools are passed to this tool.
559 - ``actions`` - A single big ``case`` expression that specifies how
560 this tool reacts on command-line options (described in more detail
570 A tool often needs to react to command-line options, and this is
571 precisely what the ``actions`` property is for. The next example
572 illustrates this feature::
574 def llvm_gcc_linker : Tool<[
575 (in_language "object-code"),
576 (out_language "executable"),
577 (output_suffix "out"),
578 (cmd_line "llvm-gcc $INFILE -o $OUTFILE"),
580 (actions (case (not_empty "L"), (forward "L"),
581 (not_empty "l"), (forward "l"),
583 [(append_cmd "-dummy1"), (append_cmd "-dummy2")])
586 The ``actions`` tool property is implemented on top of the omnipresent
587 ``case`` expression. It associates one or more different *actions*
588 with given conditions - in the example, the actions are ``forward``,
589 which forwards a given option unchanged, and ``append_cmd``, which
590 appends a given string to the tool execution command. Multiple actions
591 can be associated with a single condition by using a list of actions
592 (used in the example to append some dummy options). The same ``case``
593 construct can also be used in the ``cmd_line`` property to modify the
596 The "join" property used in the example means that this tool behaves
599 The list of all possible actions follows.
603 - ``append_cmd`` - Append a string to the tool invocation command.
604 Example: ``(case (switch_on "pthread"), (append_cmd "-lpthread"))``.
606 - ``error`` - Exit with error.
607 Example: ``(error "Mixing -c and -S is not allowed!")``.
609 - ``warning`` - Print a warning.
610 Example: ``(warning "Specifying both -O1 and -O2 is meaningless!")``.
612 - ``forward`` - Forward the option unchanged.
613 Example: ``(forward "Wall")``.
615 - ``forward_as`` - Change the option's name, but forward the argument
617 Example: ``(forward_as "O0", "--disable-optimization")``.
619 - ``forward_value`` - Forward only option's value. Cannot be used with switch
620 options (since they don't have values), but works fine with lists.
621 Example: ``(forward_value "Wa,")``.
623 - ``forward_transformed_value`` - As above, but applies a hook to the
624 option's value before forwarding (see `below`__). When
625 ``forward_transformed_value`` is applied to a list
626 option, the hook must have signature
627 ``std::string hooks::HookName (const std::vector<std::string>&)``.
628 Example: ``(forward_transformed_value "m", "ConvertToMAttr")``.
632 - ``output_suffix`` - Modify the output suffix of this tool.
633 Example: ``(output_suffix "i")``.
635 - ``stop_compilation`` - Stop compilation after this tool processes its
636 input. Used without arguments.
637 Example: ``(stop_compilation)``.
643 If you are adding support for a new language to LLVMC, you'll need to
644 modify the language map, which defines mappings from file extensions
645 to language names. It is used to choose the proper toolchain(s) for a
646 given input file set. Language map definition looks like this::
648 def LanguageMap : LanguageMap<
649 [LangToSuffixes<"c++", ["cc", "cp", "cxx", "cpp", "CPP", "c++", "C"]>,
650 LangToSuffixes<"c", ["c"]>,
654 For example, without those definitions the following command wouldn't work::
657 llvmc: Unknown suffix: cpp
659 The language map entries should be added only for tools that are
660 linked with the root node. Since tools are not allowed to have
661 multiple output languages, for nodes "inside" the graph the input and
662 output languages should match. This is enforced at compile-time.
667 It is sometimes useful to run error-checking code before processing the
668 compilation graph. For example, if optimization options "-O1" and "-O2" are
669 implemented as switches, we might want to output a warning if the user invokes
670 the driver with both of these options enabled.
672 The ``OptionPreprocessor`` feature is reserved specially for these
673 occasions. Example (adapted from the built-in Base plugin)::
675 def Preprocess : OptionPreprocessor<
676 (case (and (switch_on "O3"), (any_switch_on ["O0", "O1", "O2"])),
677 [(unset_option ["O0", "O1", "O2"]),
678 (warning "Multiple -O options specified, defaulted to -O3.")],
679 (and (switch_on "O2"), (any_switch_on ["O0", "O1"])),
680 (unset_option ["O0", "O1"]),
681 (and (switch_on "O1"), (switch_on "O0")),
685 Here, ``OptionPreprocessor`` is used to unset all spurious optimization options
686 (so that they are not forwarded to the compiler).
688 ``OptionPreprocessor`` is basically a single big ``case`` expression, which is
689 evaluated only once right after the plugin is loaded. The only allowed actions
690 in ``OptionPreprocessor`` are ``error``, ``warning`` and a special action
691 ``unset_option``, which, as the name suggests, unsets a given option. For
692 convenience, ``unset_option`` also works on lists.
700 Hooks and environment variables
701 -------------------------------
703 Normally, LLVMC executes programs from the system ``PATH``. Sometimes,
704 this is not sufficient: for example, we may want to specify tool paths
705 or names in the configuration file. This can be easily achieved via
706 the hooks mechanism. To write your own hooks, just add their
707 definitions to the ``PluginMain.cpp`` or drop a ``.cpp`` file into the
708 your plugin directory. Hooks should live in the ``hooks`` namespace
709 and have the signature ``std::string hooks::MyHookName ([const char*
710 Arg0 [ const char* Arg2 [, ...]]])``. They can be used from the
711 ``cmd_line`` tool property::
713 (cmd_line "$CALL(MyHook)/path/to/file -o $CALL(AnotherHook)")
715 To pass arguments to hooks, use the following syntax::
717 (cmd_line "$CALL(MyHook, 'Arg1', 'Arg2', 'Arg # 3')/path/to/file -o1 -o2")
719 It is also possible to use environment variables in the same manner::
721 (cmd_line "$ENV(VAR1)/path/to/file -o $ENV(VAR2)")
723 To change the command line string based on user-provided options use
724 the ``case`` expression (documented `above`__)::
729 "llvm-g++ -E -x c $INFILE -o $OUTFILE",
731 "llvm-g++ -c -x c $INFILE -o $OUTFILE -emit-llvm"))
737 How plugins are loaded
738 ----------------------
740 It is possible for LLVMC plugins to depend on each other. For example,
741 one can create edges between nodes defined in some other plugin. To
742 make this work, however, that plugin should be loaded first. To
743 achieve this, the concept of plugin priority was introduced. By
744 default, every plugin has priority zero; to specify the priority
745 explicitly, put the following line in your plugin's TableGen file::
747 def Priority : PluginPriority<$PRIORITY_VALUE>;
748 # Where PRIORITY_VALUE is some integer > 0
750 Plugins are loaded in order of their (increasing) priority, starting
751 with 0. Therefore, the plugin with the highest priority value will be
757 When writing LLVMC plugins, it can be useful to get a visual view of
758 the resulting compilation graph. This can be achieved via the command
759 line option ``--view-graph``. This command assumes that Graphviz_ and
760 Ghostview_ are installed. There is also a ``--write-graph`` option that
761 creates a Graphviz source file (``compilation-graph.dot``) in the
764 Another useful ``llvmc`` option is ``--check-graph``. It checks the
765 compilation graph for common errors like mismatched output/input
766 language names, multiple default edges and cycles. These checks can't
767 be performed at compile-time because the plugins can load code
768 dynamically. When invoked with ``--check-graph``, ``llvmc`` doesn't
769 perform any compilation tasks and returns the number of encountered
770 errors as its status code.
772 .. _Graphviz: http://www.graphviz.org/
773 .. _Ghostview: http://pages.cs.wisc.edu/~ghost/
775 Conditioning on the executable name
776 -----------------------------------
778 For now, the executable name (the value passed to the driver in ``argv[0]``) is
779 accessible only in the C++ code (i.e. hooks). Use the following code::
782 extern const char* ProgramName;
787 std::string MyHook() {
789 if (strcmp(ProgramName, "mydriver") == 0) {
794 } // end namespace hooks
796 In general, you're encouraged not to make the behaviour dependent on the
797 executable file name, and use command-line switches instead. See for example how
798 the ``Base`` plugin behaves when it needs to choose the correct linker options
799 (think ``g++`` vs. ``gcc``).
805 <a href="http://jigsaw.w3.org/css-validator/check/referer">
806 <img src="http://jigsaw.w3.org/css-validator/images/vcss-blue"
807 alt="Valid CSS" /></a>
808 <a href="http://validator.w3.org/check?uri=referer">
809 <img src="http://www.w3.org/Icons/valid-xhtml10-blue"
810 alt="Valid XHTML 1.0 Transitional"/></a>
812 <a href="mailto:foldr@codedgers.com">Mikhail Glushenkov</a><br />
813 <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br />
815 Last modified: $Date: 2008-12-11 11:34:48 -0600 (Thu, 11 Dec 2008) $