1 .\" Process with groff -man -Tascii file.3
2 .TH GMQCC 1 2012-07-12 "" "gmqcc Manual"
4 gmqcc \- A Quake C compiler built from the NIH realm of sarcastic wit
7 [\fIOPTIONS\fR] [\fIfiles...\fR]
9 Traditionally, a QC compiler reads the file \fIprogs.src\fR which
10 in its first line contains the output filename, and the rest is a
11 list of QC source files that are to be compiled in order.
12 \fBgmqcc\fR optionally takes options to specify the output and
13 input files on the commandline, and also accepts assembly files.
15 \fBgmqcc\fR mostly tries to mimick gcc's commandline handling, though
16 there are also traditional long-options available.
19 Show a usage message and exit.
22 Turn on some compiler debugging mechanisms.
25 Turn on compiler mem-check. (Shows allocations and checks for leaks.)
27 .BI "-o, --output=" filename
28 Specify the output filename. Defaults to progs.dat. This will overwrite
29 the output file listed in a \fIprogs.src\fR file in case such a file is used.
32 Specify the optimization level
35 Highest optimization level
37 Default optimization level
39 Minimal optimization level
41 Disable optimization entierly
44 .BI "-O" name "\fR, " "" -Ono- name
45 Enable or disable a specific optimization. Note that these options
46 must be used after setting the optimization level, otherwise they'll
50 List all possible optimizations and the optimization level they're
53 .BI -W warning "\fR, " "" -Wno- warning
54 Enable or disable a warning.
57 Enable all warnings. Overrides preceding -W parameters.
60 List all possible warn flags.
62 .BI -f flag "\fR, " "" -fno- flag
63 Enable or disable a specific compile flag. See the list of flags
67 List all possible compile flags.
70 Disables colored output
73 Redirects standard output to a \fIfile\fR
76 Redirects standard error to a \fIfile\fR
79 Use the specified standard for parsing QC code. The following standards
81 .IR gmqcc , qcc , fteqcc
82 Selecting a standard also implies some -f options and behaves as if
83 those options have been written right after the -std option, meaning
84 if you changed them before the -std option, you're now overwriting
87 .BR -std=gmqcc " includes:"
89 -fadjust-vector-fields
91 .BR -std=qcc " includes:"
94 -fassign-function-types
95 -f\fIno-\fRadjust-vector-fields
98 .BR -std=fteqcc " includes:"
102 -ftranslatable-strings
103 -fassign-function-types
105 -f\fIno-\fRadjust-vector-fields
106 -f\fIno-\fRcorrect-ternary
112 Generate a warning about variables which are declared but never used.
113 This can be avoided by adding the \fInoref\fR keyword in front of the
114 variable declaration. Additionally a complete section of unreferenced
115 variables can be opened using \fI#pragma noref 1\fR, and closed via
116 \fI#pragma noref 0\fR.
118 .B -Wused-uninitialized
119 Generate a warning if it is possible that a variable can be used
120 without prior initialization. Note that this warning is not
121 necessarily reliable if the initialization happens only under certain
122 conditions. The other way is \fInot\fR possible: that the warning is
123 \fInot\fR generated when uninitialized use \fIis possible\fR.
125 .B -Wunknown-control-sequence
126 Generate an error when an unrecognized control sequence in a string is
127 used. Meaning: when there's a character after a backslash in a string
128 which has no known meaning.
131 Warn when using special extensions which are not part of the selected
134 .B -Wfield-redeclared
135 Generally QC compilers ignore redeclaration of fields. Here you can
136 optionally enable a warning.
138 .B -Wmissing-return-values
139 Functions which aren't of type \fIvoid\fR will warn if it possible to
140 reach the end without returning an actual value.
142 .B -Wtoo-few-parameters
143 Warn about a function call with fewer parameters than the function
147 Warn when a locally declared variable shadows variable.
150 Warn when the initialization of a local variable turns the variable
151 into a constant. This is default behaviour unless
152 \fI-finitialized-nonconstants\fR is used.
155 There are only 2 known global variables of type void: end_sys_globals
156 and end_sys_fields. Any other void-variable will warn.
158 .B -Wimplicit-function-pointer
159 A global function which is not declared with the \fIvar\fR keyword is
160 expected to have an implementing body, or be a builtin. If neither is
161 the case, it implicitly becomes a function pointer, and a warning is
164 .B -Wvariadic-function
165 Currently there's no way for an in QC implemented function to access
166 variadic parameters. If a function with variadic parameters has an
167 implementing body, a warning will be generated.
170 Generate warnings about \fI$frame\fR commands, for instance about
171 duplicate frame definitions.
173 .B -Weffectless-statement
174 Warn about statements which have no effect. Any expression which does
175 not call a function or assigns a variable.
178 The \fIend_sys_fields\fR variable is supposed to be a global variable
179 of type \fIvoid\fR. It is also recognized as a \fIfield\fR but this
180 will generate a warning.
182 .B -Wassign-function-types
183 Warn when assigning to a function pointer with an unmatching
184 signature. This usually happens in cases like assigning the null
185 function to an entity's .think function pointer.
188 Enable warnings coming from the preprocessor. Like duplicate macro
192 Warn if there's a preprocessor \fI#if\fR spanning across several
195 .B -Wdouble-declaration
196 Warn about multiple declarations of globals. This seems pretty common
197 in QC code so you probably do not want this unless you want to clean
201 The combination of \fIconst\fR and \fIvar\fR is not illegal, however
202 different compilers may handle them differently. We were told, the
203 intention is to create a function-pointer which is not assignable.
204 This is exactly how we interpret it. However for this interpretation
205 the \fIvar\fR keyword is considered superfluous (and philosophically
206 wrong), so it is possible to generate a warning about this.
208 .B -Wmultibyte-character
209 Warn about multibyte character constants, they do not work right now.
211 .B -Wternary-precedence
212 Warn if a ternary expression which contains a comma operator is used
213 without enclosing parenthesis, since this is most likely not what you
214 actually want. We recommend the \fI-fcorrect-ternary\fR option.
217 Warn when encountering an unrecognized \fI#pragma\fR line.
220 Enable some warnings added in order to help debugging in the compiler.
225 Allow local variables to overlap with each other if they don't
226 interfer with each other. (Not implemented right now)
228 .B -fdarkplaces-string-table-bug
229 Add some additional characters to the string table in order to
230 compensate for a wrong boundcheck in some specific version of the
233 .B -fadjust-vector-fields
234 When assigning to field pointers of type \fI.vector\fR the common
235 behaviour in compilers like \fIfteqcc\fR is to only assign the
236 x-component of the pointer. This means that you can use the vector as
237 such, but you cannot use its y and z components directly. This flag
238 fixes this behaviour. Before using it make sure your code does not
239 depend on the buggy behaviour.
242 Enable a partially fteqcc-compatible preprocessor. It supports all the
243 features used in the Xonotic codebase. If you need more, write a
247 Allow switch cases to use non constant variables.
250 Perform early out in logical AND and OR expressions. The final result
251 will be either a 0 or a 1, see the next flag for more possibilities.
254 In many languages, logical expressions perform early out in a special
255 way: If the left operand of an AND yeilds true, or the one of an OR
256 yields false, the complete expression evaluates to the right side.
257 Thus \fItrue && 5\fI evaluates to 5 rather than 1.
259 .B -ftranslatable-strings
260 Enable the underscore intrinsic: Using \fI_("A string constant")\fR
261 will cause the string immediate to get a name with a "dotranslate_"
262 prefix. The darkplaces engine recognizes these and translates them in
263 a way similar to how gettext works.
265 .B -finitialized-nonconstants
266 Don't implicitly convert initialized variables to constants. With this
267 flag, the \fIconst\fR keyword is required to make a constant.
269 .B -fassign-function-types
270 If this flag is not set, (and it is set by default in the qcc and
271 fteqcc standards), assigning function pointers of mismatching
272 signatures will result in an error rather than a warning.
275 Produce a linenumber file along with the output .dat file.
278 Use C's operator precedence for ternary expressions. Unless your code
279 depends on fteqcc-compatible behaviour, you'll want to use thi
282 .B -fsingle-vector-defs
283 Normally vectors generate 4 defs, once for the vector, and once for
284 its components with _x, _y, _z suffixes. This option
285 prevents components from being listed.