]> git.ipfire.org Git - thirdparty/gcc.git/blob - gcc/doc/options.texi
options.texi (Enum, EnumValue): Document new record types.
[thirdparty/gcc.git] / gcc / doc / options.texi
1 @c Copyright (C) 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010
2 @c Free Software Foundation, Inc.
3 @c This is part of the GCC manual.
4 @c For copying conditions, see the file gcc.texi.
5
6 @node Options
7 @chapter Option specification files
8 @cindex option specification files
9 @cindex @samp{optc-gen.awk}
10
11 Most GCC command-line options are described by special option
12 definition files, the names of which conventionally end in
13 @code{.opt}. This chapter describes the format of these files.
14
15 @menu
16 * Option file format:: The general layout of the files
17 * Option properties:: Supported option properties
18 @end menu
19
20 @node Option file format
21 @section Option file format
22
23 Option files are a simple list of records in which each field occupies
24 its own line and in which the records themselves are separated by
25 blank lines. Comments may appear on their own line anywhere within
26 the file and are preceded by semicolons. Whitespace is allowed before
27 the semicolon.
28
29 The files can contain the following types of record:
30
31 @itemize @bullet
32 @item
33 A language definition record. These records have two fields: the
34 string @samp{Language} and the name of the language. Once a language
35 has been declared in this way, it can be used as an option property.
36 @xref{Option properties}.
37
38 @item
39 A target specific save record to save additional information. These
40 records have two fields: the string @samp{TargetSave}, and a
41 declaration type to go in the @code{cl_target_option} structure.
42
43 @item
44 A variable record to define a variable used to store option
45 information. These records have two fields: the string
46 @samp{Variable}, and a declaration of the type and name of the
47 variable, optionally with an initializer (but without any trailing
48 @samp{;}). These records may be used for variables used for many
49 options where declaring the initializer in a single option definition
50 record, or duplicating it in many records, would be inappropriate, or
51 for variables set in option handlers rather than referenced by
52 @code{Var} properties.
53
54 @item
55 A variable record to define a variable used to store option
56 information. These records have two fields: the string
57 @samp{TargetVariable}, and a declaration of the type and name of the
58 variable, optionally with an initializer (but without any trailing
59 @samp{;}). @samp{TargetVariable} is a combination of @samp{Variable}
60 and @samp{TargetSave} records in that the variable is defined in the
61 @code{gcc_options} structure, but these variables are also stored in
62 the @code{cl_target_option} structure. The variables are saved in the
63 target save code and restored in the target restore code.
64
65 @item
66 A variable record to record any additional files that the
67 @file{options.h} file should include. This is useful to provide
68 enumeration or structure definitions needed for target variables.
69 These records have two fields: the string @samp{HeaderInclude} and the
70 name of the include file.
71
72 @item
73 A variable record to record any additional files that the
74 @file{options.c} file should include. This is useful to provide
75 inline functions needed for target variables and/or @code{#ifdef}
76 sequences to properly set up the initialization. These records have
77 two fields: the string @samp{SourceInclude} and the name of the
78 include file.
79
80 @item
81 An enumeration record to define a set of strings that may be used as
82 arguments to an option or options. These records have three fields:
83 the string @samp{Enum}, a space-separated list of properties and help
84 text used to describe the set of strings in @option{--help} output.
85 Properties use the same format as option properties; the following are
86 valid:
87 @table @code
88 @item Name(@var{name})
89 This property is required; @var{name} must be a name (suitable for use
90 in C identifiers) used to identify the set of strings in @code{Enum}
91 option properties.
92
93 @item Type(@var{type})
94 This property is required; @var{type} is the C type for variables set
95 by options using this enumeration together with @code{Var}.
96
97 @item UnknownError(@var{message})
98 The message @var{message} will be used as an error message if the
99 argument is invalid; for enumerations without @code{UnknownError}, a
100 generic error message is used. @var{message} should contain a single
101 @samp{%qs} format, which will be used to format the invalid argument.
102 @end table
103
104 @item
105 An enumeration value record to define one of the strings in a set
106 given in an @samp{Enum} record. These records have two fields: the
107 string @samp{EnumValue} and a space-separated list of properties.
108 Properties use the same format as option properties; the following are
109 valid:
110 @table @code
111 @item Enum(@var{name})
112 This property is required; @var{name} says which @samp{Enum} record
113 this @samp{EnumValue} record corresponds to.
114
115 @item String(@var{string})
116 This property is required; @var{string} is the string option argument
117 being described by this record.
118
119 @item Value(@var{value})
120 This property is required; it says what value (representable as
121 @code{int}) should be used for the given string.
122
123 @item Canonical
124 This property is optional. If present, it says the present string is
125 the canonical one among all those with the given value. Other strings
126 yielding that value will be mapped to this one so specs do not need to
127 handle them.
128
129 @item DriverOnly
130 This property is optional. If present, the present string will only
131 be accepted by the driver. This is used for cases such as
132 @option{-march=native} that are processed by the driver so that
133 @samp{gcc -v} shows how the options chosen depended on the system on
134 which the compiler was run.
135 @end table
136
137 @item
138 An option definition record. These records have the following fields:
139 @enumerate
140 @item
141 the name of the option, with the leading ``-'' removed
142 @item
143 a space-separated list of option properties (@pxref{Option properties})
144 @item
145 the help text to use for @option{--help} (omitted if the second field
146 contains the @code{Undocumented} property).
147 @end enumerate
148
149 By default, all options beginning with ``f'', ``W'' or ``m'' are
150 implicitly assumed to take a ``no-'' form. This form should not be
151 listed separately. If an option beginning with one of these letters
152 does not have a ``no-'' form, you can use the @code{RejectNegative}
153 property to reject it.
154
155 The help text is automatically line-wrapped before being displayed.
156 Normally the name of the option is printed on the left-hand side of
157 the output and the help text is printed on the right. However, if the
158 help text contains a tab character, the text to the left of the tab is
159 used instead of the option's name and the text to the right of the
160 tab forms the help text. This allows you to elaborate on what type
161 of argument the option takes.
162
163 @item
164 A target mask record. These records have one field of the form
165 @samp{Mask(@var{x})}. The options-processing script will automatically
166 allocate a bit in @code{target_flags} (@pxref{Run-time Target}) for
167 each mask name @var{x} and set the macro @code{MASK_@var{x}} to the
168 appropriate bitmask. It will also declare a @code{TARGET_@var{x}}
169 macro that has the value 1 when bit @code{MASK_@var{x}} is set and
170 0 otherwise.
171
172 They are primarily intended to declare target masks that are not
173 associated with user options, either because these masks represent
174 internal switches or because the options are not available on all
175 configurations and yet the masks always need to be defined.
176 @end itemize
177
178 @node Option properties
179 @section Option properties
180
181 The second field of an option record can specify any of the following
182 properties. When an option takes an argument, it is enclosed in parentheses
183 following the option property name. The parser that handles option files
184 is quite simplistic, and will be tricked by any nested parentheses within
185 the argument text itself; in this case, the entire option argument can
186 be wrapped in curly braces within the parentheses to demarcate it, e.g.:
187
188 @smallexample
189 Condition(@{defined (USE_CYGWIN_LIBSTDCXX_WRAPPERS)@})
190 @end smallexample
191
192 @table @code
193 @item Common
194 The option is available for all languages and targets.
195
196 @item Target
197 The option is available for all languages but is target-specific.
198
199 @item Driver
200 The option is handled by the compiler driver using code not shared
201 with the compilers proper (@file{cc1} etc.).
202
203 @item @var{language}
204 The option is available when compiling for the given language.
205
206 It is possible to specify several different languages for the same
207 option. Each @var{language} must have been declared by an earlier
208 @code{Language} record. @xref{Option file format}.
209
210 @item RejectDriver
211 The option is only handled by the compilers proper (@file{cc1} etc.)@:
212 and should not be accepted by the driver.
213
214 @item RejectNegative
215 The option does not have a ``no-'' form. All options beginning with
216 ``f'', ``W'' or ``m'' are assumed to have a ``no-'' form unless this
217 property is used.
218
219 @item Negative(@var{othername})
220 The option will turn off another option @var{othername}, which is
221 the option name with the leading ``-'' removed. This chain action will
222 propagate through the @code{Negative} property of the option to be
223 turned off.
224
225 @item Joined
226 @itemx Separate
227 The option takes a mandatory argument. @code{Joined} indicates
228 that the option and argument can be included in the same @code{argv}
229 entry (as with @code{-mflush-func=@var{name}}, for example).
230 @code{Separate} indicates that the option and argument can be
231 separate @code{argv} entries (as with @code{-o}). An option is
232 allowed to have both of these properties.
233
234 @item JoinedOrMissing
235 The option takes an optional argument. If the argument is given,
236 it will be part of the same @code{argv} entry as the option itself.
237
238 This property cannot be used alongside @code{Joined} or @code{Separate}.
239
240 @item MissingArgError(@var{message})
241 For an option marked @code{Joined} or @code{Separate}, the message
242 @var{message} will be used as an error message if the mandatory
243 argument is missing; for options without @code{MissingArgError}, a
244 generic error message is used. @var{message} should contain a single
245 @samp{%qs} format, which will be used to format the name of the option
246 passed.
247
248 @item Args(@var{n})
249 For an option marked @code{Separate}, indicate that it takes @var{n}
250 arguments. The default is 1.
251
252 @item UInteger
253 The option's argument is a non-negative integer. The option parser
254 will check and convert the argument before passing it to the relevant
255 option handler. @code{UInteger} should also be used on options like
256 @code{-falign-loops} where both @code{-falign-loops} and
257 @code{-falign-loops}=@var{n} are supported to make sure the saved
258 options are given a full integer.
259
260 @item NoDriverArg
261 For an option marked @code{Separate}, the option only takes an
262 argument in the compiler proper, not in the driver. This is for
263 compatibility with existing options that are used both directly and
264 via @option{-Wp,}; new options should not have this property.
265
266 @item Var(@var{var})
267 The state of this option should be stored in variable @var{var}
268 (actually a macro for @code{global_options.x_@var{var}}).
269 The way that the state is stored depends on the type of option:
270
271 @itemize @bullet
272 @item
273 If the option uses the @code{Mask} or @code{InverseMask} properties,
274 @var{var} is the integer variable that contains the mask.
275
276 @item
277 If the option is a normal on/off switch, @var{var} is an integer
278 variable that is nonzero when the option is enabled. The options
279 parser will set the variable to 1 when the positive form of the
280 option is used and 0 when the ``no-'' form is used.
281
282 @item
283 If the option takes an argument and has the @code{UInteger} property,
284 @var{var} is an integer variable that stores the value of the argument.
285
286 @item
287 If the option takes an argument and has the @code{Enum} property,
288 @var{var} is a variable (type given in the @code{Type} property of the
289 @samp{Enum} record whose @code{Name} property has the same argument as
290 the @code{Enum} property of this option) that stores the value of the
291 argument.
292
293 @item
294 If the option has the @code{Defer} property, @var{var} is a pointer to
295 a @code{VEC(cl_deferred_option,heap)} that stores the option for later
296 processing. (@var{var} is declared with type @code{void *} and needs
297 to be cast to @code{VEC(cl_deferred_option,heap)} before use.)
298
299 @item
300 Otherwise, if the option takes an argument, @var{var} is a pointer to
301 the argument string. The pointer will be null if the argument is optional
302 and wasn't given.
303 @end itemize
304
305 The option-processing script will usually zero-initialize @var{var}.
306 You can modify this behavior using @code{Init}.
307
308 @item Var(@var{var}, @var{set})
309 The option controls an integer variable @var{var} and is active when
310 @var{var} equals @var{set}. The option parser will set @var{var} to
311 @var{set} when the positive form of the option is used and @code{!@var{set}}
312 when the ``no-'' form is used.
313
314 @var{var} is declared in the same way as for the single-argument form
315 described above.
316
317 @item Init(@var{value})
318 The variable specified by the @code{Var} property should be statically
319 initialized to @var{value}. If more than one option using the same
320 variable specifies @code{Init}, all must specify the same initializer.
321
322 @item Mask(@var{name})
323 The option is associated with a bit in the @code{target_flags}
324 variable (@pxref{Run-time Target}) and is active when that bit is set.
325 You may also specify @code{Var} to select a variable other than
326 @code{target_flags}.
327
328 The options-processing script will automatically allocate a unique bit
329 for the option. If the option is attached to @samp{target_flags},
330 the script will set the macro @code{MASK_@var{name}} to the appropriate
331 bitmask. It will also declare a @code{TARGET_@var{name}} macro that has
332 the value 1 when the option is active and 0 otherwise. If you use @code{Var}
333 to attach the option to a different variable, the associated macros are
334 called @code{OPTION_MASK_@var{name}} and @code{OPTION_@var{name}} respectively.
335
336 You can disable automatic bit allocation using @code{MaskExists}.
337
338 @item InverseMask(@var{othername})
339 @itemx InverseMask(@var{othername}, @var{thisname})
340 The option is the inverse of another option that has the
341 @code{Mask(@var{othername})} property. If @var{thisname} is given,
342 the options-processing script will declare a @code{TARGET_@var{thisname}}
343 macro that is 1 when the option is active and 0 otherwise.
344
345 @item MaskExists
346 The mask specified by the @code{Mask} property already exists.
347 No @code{MASK} or @code{TARGET} definitions should be added to
348 @file{options.h} in response to this option record.
349
350 The main purpose of this property is to support synonymous options.
351 The first option should use @samp{Mask(@var{name})} and the others
352 should use @samp{Mask(@var{name}) MaskExists}.
353
354 @item Enum(@var{name})
355 The option's argument is a string from the set of strings associated
356 with the corresponding @samp{Enum} record. The string is checked and
357 converted to the integer specified in the corresponding
358 @samp{EnumValue} record before being passed to option handlers.
359
360 @item Defer
361 The option should be stored in a vector, specified with @code{Var},
362 for later processing.
363
364 @item Alias(@var{opt})
365 @itemx Alias(@var{opt}, @var{arg})
366 @itemx Alias(@var{opt}, @var{posarg}, @var{negarg})
367 The option is an alias for @option{-@var{opt}}. In the first form,
368 any argument passed to the alias is considered to be passed to
369 @option{-@var{opt}}, and @option{-@var{opt}} is considered to be
370 negated if the alias is used in negated form. In the second form, the
371 alias may not be negated or have an argument, and @var{posarg} is
372 considered to be passed as an argument to @option{-@var{opt}}. In the
373 third form, the alias may not have an argument, if the alias is used
374 in the positive form then @var{posarg} is considered to be passed to
375 @option{-@var{opt}}, and if the alias is used in the negative form
376 then @var{negarg} is considered to be passed to @option{-@var{opt}}.
377
378 Aliases should not specify @code{Var} or @code{Mask} or
379 @code{UInteger}. Aliases should normally specify the same languages
380 as the target of the alias; the flags on the target will be used to
381 determine any diagnostic for use of an option for the wrong language,
382 while those on the alias will be used to identify what command-line
383 text is the option and what text is any argument to that option.
384
385 When an @code{Alias} definition is used for an option, driver specs do
386 not need to handle it and no @samp{OPT_} enumeration value is defined
387 for it; only the canonical form of the option will be seen in those
388 places.
389
390 @item Ignore
391 This option is ignored apart from printing any warning specified using
392 @code{Warn}. The option will not be seen by specs and no @samp{OPT_}
393 enumeration value is defined for it.
394
395 @item SeparateAlias
396 For an option marked with @code{Joined}, @code{Separate} and
397 @code{Alias}, the option only acts as an alias when passed a separate
398 argument; with a joined argument it acts as a normal option, with an
399 @samp{OPT_} enumeration value. This is for compatibility with the
400 Java @option{-d} option and should not be used for new options.
401
402 @item Warn(@var{message})
403 If this option is used, output the warning @var{message}.
404 @var{message} is a format string, either taking a single operand with
405 a @samp{%qs} format which is the option name, or not taking any
406 operands, which is passed to the @samp{warning} function. If an alias
407 is marked @code{Warn}, the target of the alias must not also be marked
408 @code{Warn}.
409
410 @item Report
411 The state of the option should be printed by @option{-fverbose-asm}.
412
413 @item Warning
414 This is a warning option and should be shown as such in
415 @option{--help} output. This flag does not currently affect anything
416 other than @option{--help}.
417
418 @item Optimization
419 This is an optimization option. It should be shown as such in
420 @option{--help} output, and any associated variable named using
421 @code{Var} should be saved and restored when the optimization level is
422 changed with @code{optimize} attributes.
423
424 @item Undocumented
425 The option is deliberately missing documentation and should not
426 be included in the @option{--help} output.
427
428 @item Condition(@var{cond})
429 The option should only be accepted if preprocessor condition
430 @var{cond} is true. Note that any C declarations associated with the
431 option will be present even if @var{cond} is false; @var{cond} simply
432 controls whether the option is accepted and whether it is printed in
433 the @option{--help} output.
434
435 @item Save
436 Build the @code{cl_target_option} structure to hold a copy of the
437 option, add the functions @code{cl_target_option_save} and
438 @code{cl_target_option_restore} to save and restore the options.
439 @end table