]> git.ipfire.org Git - thirdparty/gcc.git/blob - gcc/doc/options.texi
Update copyright years.
[thirdparty/gcc.git] / gcc / doc / options.texi
1 @c Copyright (C) 2003-2021 Free Software Foundation, Inc.
2 @c This is part of the GCC manual.
3 @c For copying conditions, see the file gcc.texi.
4
5 @node Options
6 @chapter Option specification files
7 @cindex option specification files
8 @cindex @samp{optc-gen.awk}
9
10 Most GCC command-line options are described by special option
11 definition files, the names of which conventionally end in
12 @code{.opt}. This chapter describes the format of these files.
13
14 @menu
15 * Option file format:: The general layout of the files
16 * Option properties:: Supported option properties
17 @end menu
18
19 @node Option file format
20 @section Option file format
21
22 Option files are a simple list of records in which each field occupies
23 its own line and in which the records themselves are separated by
24 blank lines. Comments may appear on their own line anywhere within
25 the file and are preceded by semicolons. Whitespace is allowed before
26 the semicolon.
27
28 The files can contain the following types of record:
29
30 @itemize @bullet
31 @item
32 A language definition record. These records have two fields: the
33 string @samp{Language} and the name of the language. Once a language
34 has been declared in this way, it can be used as an option property.
35 @xref{Option properties}.
36
37 @item
38 A target specific save record to save additional information. These
39 records have two fields: the string @samp{TargetSave}, and a
40 declaration type to go in the @code{cl_target_option} structure.
41
42 @item
43 A variable record to define a variable used to store option
44 information. These records have two fields: the string
45 @samp{Variable}, and a declaration of the type and name of the
46 variable, optionally with an initializer (but without any trailing
47 @samp{;}). These records may be used for variables used for many
48 options where declaring the initializer in a single option definition
49 record, or duplicating it in many records, would be inappropriate, or
50 for variables set in option handlers rather than referenced by
51 @code{Var} properties.
52
53 @item
54 A variable record to define a variable used to store option
55 information. These records have two fields: the string
56 @samp{TargetVariable}, and a declaration of the type and name of the
57 variable, optionally with an initializer (but without any trailing
58 @samp{;}). @samp{TargetVariable} is a combination of @samp{Variable}
59 and @samp{TargetSave} records in that the variable is defined in the
60 @code{gcc_options} structure, but these variables are also stored in
61 the @code{cl_target_option} structure. The variables are saved in the
62 target save code and restored in the target restore code.
63
64 @item
65 A variable record to record any additional files that the
66 @file{options.h} file should include. This is useful to provide
67 enumeration or structure definitions needed for target variables.
68 These records have two fields: the string @samp{HeaderInclude} and the
69 name of the include file.
70
71 @item
72 A variable record to record any additional files that the
73 @file{options.c} or @file{options-save.c} file should include. This
74 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. The driver will prune options, removing those that are
224 turned off by some later option. This pruning is not done for options
225 with @code{Joined} or @code{JoinedOrMissing} properties, unless the
226 options have either @code{RejectNegative} property or the @code{Negative}
227 property mentions an option other than itself.
228
229 As a consequence, if you have a group of mutually-exclusive
230 options, their @code{Negative} properties should form a circular chain.
231 For example, if options @option{-@var{a}}, @option{-@var{b}} and
232 @option{-@var{c}} are mutually exclusive, their respective @code{Negative}
233 properties should be @samp{Negative(@var{b})}, @samp{Negative(@var{c})}
234 and @samp{Negative(@var{a})}.
235
236 @item Joined
237 @itemx Separate
238 The option takes a mandatory argument. @code{Joined} indicates
239 that the option and argument can be included in the same @code{argv}
240 entry (as with @code{-mflush-func=@var{name}}, for example).
241 @code{Separate} indicates that the option and argument can be
242 separate @code{argv} entries (as with @code{-o}). An option is
243 allowed to have both of these properties.
244
245 @item JoinedOrMissing
246 The option takes an optional argument. If the argument is given,
247 it will be part of the same @code{argv} entry as the option itself.
248
249 This property cannot be used alongside @code{Joined} or @code{Separate}.
250
251 @item MissingArgError(@var{message})
252 For an option marked @code{Joined} or @code{Separate}, the message
253 @var{message} will be used as an error message if the mandatory
254 argument is missing; for options without @code{MissingArgError}, a
255 generic error message is used. @var{message} should contain a single
256 @samp{%qs} format, which will be used to format the name of the option
257 passed.
258
259 @item Args(@var{n})
260 For an option marked @code{Separate}, indicate that it takes @var{n}
261 arguments. The default is 1.
262
263 @item UInteger
264 The option's argument is a non-negative integer consisting of either
265 decimal or hexadecimal digits interpreted as @code{int}. Hexadecimal
266 integers may optionally start with the @code{0x} or @code{0X} prefix.
267 The option parser validates and converts the argument before passing
268 it to the relevant option handler. @code{UInteger} should also be used
269 with options like @code{-falign-loops} where both @code{-falign-loops}
270 and @code{-falign-loops}=@var{n} are supported to make sure the saved
271 options are given a full integer. Positive values of the argument in
272 excess of @code{INT_MAX} wrap around zero.
273
274 @item Host_Wide_Int
275 The option's argument is a non-negative integer consisting of either
276 decimal or hexadecimal digits interpreted as the widest integer type
277 on the host. As with an @code{UInteger} argument, hexadecimal integers
278 may optionally start with the @code{0x} or @code{0X} prefix. The option
279 parser validates and converts the argument before passing it to
280 the relevant option handler. @code{Host_Wide_Int} should be used with
281 options that need to accept very large values. Positive values of
282 the argument in excess of @code{HOST_WIDE_INT_M1U} are assigned
283 @code{HOST_WIDE_INT_M1U}.
284
285 @item IntegerRange(@var{n}, @var{m})
286 The options's arguments are integers of type @code{int}. The option's
287 parser validates that the value of an option integer argument is within
288 the closed range [@var{n}, @var{m}].
289
290 @item ByteSize
291 A property applicable only to @code{UInteger} or @code{Host_Wide_Int}
292 arguments. The option's integer argument is interpreted as if in infinite
293 precision using saturation arithmetic in the corresponding type. The argument
294 may be followed by a @samp{byte-size} suffix designating a multiple of bytes
295 such as @code{kB} and @code{KiB} for kilobyte and kibibyte, respectively,
296 @code{MB} and @code{MiB} for megabyte and mebibyte, @code{GB} and @code{GiB}
297 for gigabyte and gigibyte, and so on. @code{ByteSize} should be used for
298 with options that take a very large argument representing a size in bytes,
299 such as @option{-Wlarger-than=}.
300
301 @item ToLower
302 The option's argument should be converted to lowercase as part of
303 putting it in canonical form, and before comparing with the strings
304 indicated by any @code{Enum} property.
305
306 @item NoDriverArg
307 For an option marked @code{Separate}, the option only takes an
308 argument in the compiler proper, not in the driver. This is for
309 compatibility with existing options that are used both directly and
310 via @option{-Wp,}; new options should not have this property.
311
312 @item Var(@var{var})
313 The state of this option should be stored in variable @var{var}
314 (actually a macro for @code{global_options.x_@var{var}}).
315 The way that the state is stored depends on the type of option:
316
317 @item WarnRemoved
318 The option is removed and every usage of such option will
319 result in a warning. We use it option backward compatibility.
320
321 @item Var(@var{var}, @var{set})
322 The option controls an integer variable @var{var} and is active when
323 @var{var} equals @var{set}. The option parser will set @var{var} to
324 @var{set} when the positive form of the option is used and @code{!@var{set}}
325 when the ``no-'' form is used.
326
327 @var{var} is declared in the same way as for the single-argument form
328 described above.
329
330 @itemize @bullet
331 @item
332 If the option uses the @code{Mask} or @code{InverseMask} properties,
333 @var{var} is the integer variable that contains the mask.
334
335 @item
336 If the option is a normal on/off switch, @var{var} is an integer
337 variable that is nonzero when the option is enabled. The options
338 parser will set the variable to 1 when the positive form of the
339 option is used and 0 when the ``no-'' form is used.
340
341 @item
342 If the option takes an argument and has the @code{UInteger} property,
343 @var{var} is an integer variable that stores the value of the argument.
344
345 @item
346 If the option takes an argument and has the @code{Enum} property,
347 @var{var} is a variable (type given in the @code{Type} property of the
348 @samp{Enum} record whose @code{Name} property has the same argument as
349 the @code{Enum} property of this option) that stores the value of the
350 argument.
351
352 @item
353 If the option has the @code{Defer} property, @var{var} is a pointer to
354 a @code{VEC(cl_deferred_option,heap)} that stores the option for later
355 processing. (@var{var} is declared with type @code{void *} and needs
356 to be cast to @code{VEC(cl_deferred_option,heap)} before use.)
357
358 @item
359 Otherwise, if the option takes an argument, @var{var} is a pointer to
360 the argument string. The pointer will be null if the argument is optional
361 and wasn't given.
362 @end itemize
363
364 The option-processing script will usually zero-initialize @var{var}.
365 You can modify this behavior using @code{Init}.
366
367 @item Init(@var{value})
368 The variable specified by the @code{Var} property should be statically
369 initialized to @var{value}. If more than one option using the same
370 variable specifies @code{Init}, all must specify the same initializer.
371
372 @item Mask(@var{name})
373 The option is associated with a bit in the @code{target_flags}
374 variable (@pxref{Run-time Target}) and is active when that bit is set.
375 You may also specify @code{Var} to select a variable other than
376 @code{target_flags}.
377
378 The options-processing script will automatically allocate a unique bit
379 for the option. If the option is attached to @samp{target_flags},
380 the script will set the macro @code{MASK_@var{name}} to the appropriate
381 bitmask. It will also declare a @code{TARGET_@var{name}} macro that has
382 the value 1 when the option is active and 0 otherwise. If you use @code{Var}
383 to attach the option to a different variable, the bitmask macro with be
384 called @code{OPTION_MASK_@var{name}}.
385
386 @item InverseMask(@var{othername})
387 @itemx InverseMask(@var{othername}, @var{thisname})
388 The option is the inverse of another option that has the
389 @code{Mask(@var{othername})} property. If @var{thisname} is given,
390 the options-processing script will declare a @code{TARGET_@var{thisname}}
391 macro that is 1 when the option is active and 0 otherwise.
392
393 @item Enum(@var{name})
394 The option's argument is a string from the set of strings associated
395 with the corresponding @samp{Enum} record. The string is checked and
396 converted to the integer specified in the corresponding
397 @samp{EnumValue} record before being passed to option handlers.
398
399 @item Defer
400 The option should be stored in a vector, specified with @code{Var},
401 for later processing.
402
403 @item Alias(@var{opt})
404 @itemx Alias(@var{opt}, @var{arg})
405 @itemx Alias(@var{opt}, @var{posarg}, @var{negarg})
406 The option is an alias for @option{-@var{opt}} (or the negative form
407 of that option, depending on @code{NegativeAlias}). In the first form,
408 any argument passed to the alias is considered to be passed to
409 @option{-@var{opt}}, and @option{-@var{opt}} is considered to be
410 negated if the alias is used in negated form. In the second form, the
411 alias may not be negated or have an argument, and @var{posarg} is
412 considered to be passed as an argument to @option{-@var{opt}}. In the
413 third form, the alias may not have an argument, if the alias is used
414 in the positive form then @var{posarg} is considered to be passed to
415 @option{-@var{opt}}, and if the alias is used in the negative form
416 then @var{negarg} is considered to be passed to @option{-@var{opt}}.
417
418 Aliases should not specify @code{Var} or @code{Mask} or
419 @code{UInteger}. Aliases should normally specify the same languages
420 as the target of the alias; the flags on the target will be used to
421 determine any diagnostic for use of an option for the wrong language,
422 while those on the alias will be used to identify what command-line
423 text is the option and what text is any argument to that option.
424
425 When an @code{Alias} definition is used for an option, driver specs do
426 not need to handle it and no @samp{OPT_} enumeration value is defined
427 for it; only the canonical form of the option will be seen in those
428 places.
429
430 @item NegativeAlias
431 For an option marked with @code{Alias(@var{opt})}, the option is
432 considered to be an alias for the positive form of @option{-@var{opt}}
433 if negated and for the negative form of @option{-@var{opt}} if not
434 negated. @code{NegativeAlias} may not be used with the forms of
435 @code{Alias} taking more than one argument.
436
437 @item Ignore
438 This option is ignored apart from printing any warning specified using
439 @code{Warn}. The option will not be seen by specs and no @samp{OPT_}
440 enumeration value is defined for it.
441
442 @item SeparateAlias
443 For an option marked with @code{Joined}, @code{Separate} and
444 @code{Alias}, the option only acts as an alias when passed a separate
445 argument; with a joined argument it acts as a normal option, with an
446 @samp{OPT_} enumeration value. This is for compatibility with the
447 Java @option{-d} option and should not be used for new options.
448
449 @item Warn(@var{message})
450 If this option is used, output the warning @var{message}.
451 @var{message} is a format string, either taking a single operand with
452 a @samp{%qs} format which is the option name, or not taking any
453 operands, which is passed to the @samp{warning} function. If an alias
454 is marked @code{Warn}, the target of the alias must not also be marked
455 @code{Warn}.
456
457 @item Warning
458 This is a warning option and should be shown as such in
459 @option{--help} output. This flag does not currently affect anything
460 other than @option{--help}.
461
462 @item Optimization
463 This is an optimization option. It should be shown as such in
464 @option{--help} output, and any associated variable named using
465 @code{Var} should be saved and restored when the optimization level is
466 changed with @code{optimize} attributes.
467
468 @item PerFunction
469 This is an option that can be overridden on a per-function basis.
470 @code{Optimization} implies @code{PerFunction}, but options that do not
471 affect executable code generation may use this flag instead, so that the
472 option is not taken into account in ways that might affect executable
473 code generation.
474
475 @item Param
476 This is an option that is a parameter.
477
478 @item Undocumented
479 The option is deliberately missing documentation and should not
480 be included in the @option{--help} output.
481
482 @item Condition(@var{cond})
483 The option should only be accepted if preprocessor condition
484 @var{cond} is true. Note that any C declarations associated with the
485 option will be present even if @var{cond} is false; @var{cond} simply
486 controls whether the option is accepted and whether it is printed in
487 the @option{--help} output.
488
489 @item Save
490 Build the @code{cl_target_option} structure to hold a copy of the
491 option, add the functions @code{cl_target_option_save} and
492 @code{cl_target_option_restore} to save and restore the options.
493
494 @item SetByCombined
495 The option may also be set by a combined option such as
496 @option{-ffast-math}. This causes the @code{gcc_options} struct to
497 have a field @code{frontend_set_@var{name}}, where @code{@var{name}}
498 is the name of the field holding the value of this option (without the
499 leading @code{x_}). This gives the front end a way to indicate that
500 the value has been set explicitly and should not be changed by the
501 combined option. For example, some front ends use this to prevent
502 @option{-ffast-math} and @option{-fno-fast-math} from changing the
503 value of @option{-fmath-errno} for languages that do not use
504 @code{errno}.
505
506 @item EnabledBy(@var{opt})
507 @itemx EnabledBy(@var{opt} || @var{opt2})
508 @itemx EnabledBy(@var{opt} && @var{opt2})
509 If not explicitly set, the option is set to the value of
510 @option{-@var{opt}}; multiple options can be given, separated by
511 @code{||}. The third form using @code{&&} specifies that the option is
512 only set if both @var{opt} and @var{opt2} are set. The options @var{opt}
513 and @var{opt2} must have the @code{Common} property; otherwise, use
514 @code{LangEnabledBy}.
515
516 @item LangEnabledBy(@var{language}, @var{opt})
517 @itemx LangEnabledBy(@var{language}, @var{opt}, @var{posarg}, @var{negarg})
518 When compiling for the given language, the option is set to the value
519 of @option{-@var{opt}}, if not explicitly set. @var{opt} can be also a list
520 of @code{||} separated options. In the second form, if
521 @var{opt} is used in the positive form then @var{posarg} is considered
522 to be passed to the option, and if @var{opt} is used in the negative
523 form then @var{negarg} is considered to be passed to the option. It
524 is possible to specify several different languages. Each
525 @var{language} must have been declared by an earlier @code{Language}
526 record. @xref{Option file format}.
527
528 @item NoDWARFRecord
529 The option is omitted from the producer string written by
530 @option{-grecord-gcc-switches}.
531
532 @item PchIgnore
533 Even if this is a target option, this option will not be recorded / compared
534 to determine if a precompiled header file matches.
535
536 @item CPP(@var{var})
537 The state of this option should be kept in sync with the preprocessor
538 option @var{var}. If this property is set, then properties @code{Var}
539 and @code{Init} must be set as well.
540
541 @item CppReason(@var{CPP_W_Enum})
542 This warning option corresponds to @code{cpplib.h} warning reason code
543 @var{CPP_W_Enum}. This should only be used for warning options of the
544 C-family front-ends.
545
546 @end table