GMQCC(1)

📦 version 0.3.5+git20251116, in ubuntu resolute, ubuntu stonking

GMQCC(1) — Programmer's Manual 💖

okay bestie, grab a snack, this one's a long one (it comes in parts, we're on part 1) 🍓

✨ NAME ✨

gmqcc — a Quake C compiler, built from the NIH realm of sarcastic wit 💅

✨ SYNOPSIS ✨

gmqcc [options] [files...]

✨ DESCRIPTION ✨

so, back in the day, a QC compiler would read the file progs.src, and that file's first line is the output filename, and everything after that is a list of QC source files that get compiled in order. that's the whole vibe.

gmqcc optionally takes options so you can specify the output and input files right on the commandline instead, and it also accepts assembly files. iconic behavior honestly 🎀

✨ OPTIONS ✨

gmqcc mostly tries to mimic gcc's commandline handling, though there are also traditional long-options available if that's more your thing. both? both. 🫶

  • -h, --help — show a usage message and dip out. 👋
  • -o, --output=filename — pick the output filename. defaults to progs.dat. heads up: this will overwrite the output file listed in a progs.src file, in case such a file is being used. 😤
    • -Onumber — specify the optimization level:
      • 3 — highest optimization level 🔥
      • 2 — default optimization level ⭐
      • 1 — minimal optimization level
      • 0 — disable optimization entirely 💀
  • -Oname, -Ono-name — enable or disable one specific optimization. ⚠️ important: these have to be used after you set the optimization level, otherwise they'll just get overwritten. order matters, bestie.
  • -Ohelp — list all possible optimizations and the optimization level they're activated at. 👑
  • -q, --quiet — be less verbose. specifically it removes the messages about which files are being processed, which compilation mode is being used, and some others. warnings and errors will of course still be displayed, so no hiding from the truth. 🙈
  • -Dmacroname, -Dmacroname=value — predefine a macro, optionally with an optional value.
  • -E — run only the preprocessor, as if -fftepp was used, and print the preprocessed code to stdout.
  • -Wwarning, -Wno-warning — enable or disable a warning.
  • -Wall — enable almost all warnings. overrides preceding -W parameters. 💅

the following warnings will not be enabled:

  • -Wuninitialized-global
  • -Werror, -Wno-error — controls whether or not all warnings should be treated as errors. scary but slay.
  • -Werror-warning, -Wno-error-warning — controls whether a specific warning should be an error.
  • -Whelp — list all possible warn flags. 🌈
  • -fflag, -fno-flag — enable or disable a specific compile flag. see the list of flags below.
  • -fhelp — list all possible compile flags. ✨
  • -nocolor — disables colored output 🎨 (sad, but sometimes you gotta)
  • -config=file — use an ini file to read all the -O, -W and -f flag from. See the
  • -debug — turn on some compiler debugging mechanisms. 🔍
  • -memchk — turn on compiler mem-check. (shows allocations and checks for leaks.) 🧚
  • --memdumpcolscolumns — changes the number of columns to use for the debug memory dump, defaults to 16. "CONFIG" section about the file format.
  • -redirout=file — redirects standard output to a file.
  • -redirerr=file — redirects standard error to a file.
  • -std=standard — use the specified standard for parsing QC code. the following standards are available: gmqcc, qcc, fteqcc.
⚠️ selecting a standard also implies some -f options, and behaves as if those options have been written right after the -std option. meaning: if you changed them before the --std option, you're now overwriting them. 😭

-std=gmqcc includes:

  • -fadjust-vector-fields
  • -fcorrect-logic
  • -ftrue-empty-strings
  • -floop-labels
  • -finitialized-nonconstants
  • -ftranslatable-strings
  • -fno-false-empty-strings
  • -Winvalid-parameter-count
  • -Wmissing-returnvalues
  • -fcorrect-ternary (cannot be turned off) 🔒

-std=qcc includes:

  • -fassign-function-types
  • -fIno-adjust-vector-fields

-std=fteqcc includes:

  • -fftepp
  • -ftranslatable-strings
  • -fassign-function-types
  • -Wternary-precedence
  • -fno-adjust-vector-fields
  • -fno-correct-ternary
  • --add-info — adds compiler information to the generated binary file. currently this includes the following globals:
    • reserved:version — string containing the compiler version as printed by the --version parameter. 💖
  • --correct, --no-correct — when enabled, errors about undefined values try to suggest an existing value via spell checking. it's giving autocorrect but for your code ✨
  • -dump — DEBUG OPTION. print the code's intermediate representation before the optimization and finalization passes to stdout, before generating the binary.
  • -dumpfin — DEBUG OPTION. print the code's intermediate representation after the optimization and finalization passes to stdout, before generating the binary. the instructions will be enumerated, and values will contain a list of liferanges. 👑
  • -force-crc=CRC — force the produced progs file to use the specified CRC.
  • -state-fps=NUM — activate -femulate-state and set the emulated FPS to NUM.

ok that's part 1 bestie, more coming, don't go anywhere 💜

✨ COMPILE WARNINGS ✨

okay so warnings are like the compiler gently (or not so gently) telling you "bestie, this might be a problem" 💖 here's the whole list, no cap.

  • -Wunused-variable — warns about variables that are declared but never used, bestie. You can avoid it by putting the noref keyword in front of the variable declaration. Also, you can open a whole section of unreferenced variables with #pragma noref 1 and close it via #pragma noref 0. 💅
  • -Wunused-component — warns about vector variables that are declared but not all their components are used. like, you declared a whole vector but only use x? the compiler is not impressed. 😭
  • -Wused-uninitialized — warns if it's possible that a variable gets used without being initialized first. ngl, this warning isn't always reliable if the initialization only happens under certain conditions. but the reverse can't happen: it won't fail to warn when uninitialized use is actually possible. so it's giving cautious vibes. ✨
  • -Wunknown-control-sequence — generates an error when an unrecognized control sequence in a string is used. meaning: there's a character after a backslash in a string that has no known meaning. like "\q"? the compiler is like "what is this? 🙈"
  • -Wextensions — warns when you use special extensions that aren't part of the selected standard. staying in your lane, periodt.
  • -Wfield-redeclared — QC compilers usually ignore redeclaration of fields. here you can optionally enable a warning if you want that extra attention. 👑
  • -Wmissing-return-values — functions that aren't void will warn if it's possible to reach the end without returning an actual value. like, you promised a return but then just... didn't? the audacity. 💀
  • -Winvalid-parameter-count — warns about a function call with an invalid number of parameters. too many? too few? the compiler is counting on its fingers. 🍓
  • -Wlocal-shadows — warns when a locally declared variable shadows another variable. spooky shadowing energy. 👻
  • -Wlocal-constants — warns when the initialization of a local variable turns the variable into a constant. this is default behaviour unless you use -finitialized-nonconstants. so it's giving "you made it constant, bestie". 🎀
  • -Wvoid-variables — there are only 2 known global variables of type void: end_sys_globals and end_sys_fields. any other void-variable will warn. so don't be extra. 💅
  • -Wimplicit-function-pointer — a global function not declared with the var keyword is expected to have an implementing body, or be a builtin. if neither, it implicitly becomes a function pointer, and you get a warning. surprise! 🎉
  • -Wvariadic-function — currently there's no way for an in QC implemented function to access variadic parameters. if a function with variadic parameters has an implementing body, you'll get a warning. so don't even try. 😭
  • -Wframe-macros — generates warnings about $frame commands, like duplicate frame definitions. frame drama. 🎬
  • -Weffectless-statement — warns about statements that have no effect. any expression that doesn't call a function or assign a variable. it's just... there. 💀
  • -Wend-sys-fields — the end_sys_fields variable is supposed to be a global variable of type void. it's also recognized as a field but that will generate a warning. so don't do that. 🙈
  • -Wassign-function-types — warns when assigning to a function pointer with an unmatching signature. this usually happens when you assign the null function to an entity's .think function pointer. oops. 🔥
  • -Wcpp — shows warnings created using the preprocessor's #warning directive. preprocessor be like "hey bestie, just a heads up". 💌
  • -Wmultifile-if — warns if there's a preprocessor #if spanning across several files. that's messy. 🧹
  • -Wdouble-declaration — warns about multiple declarations of globals. this seems pretty common in QC code, so you probably don't want this unless you're cleaning up your code. no shade. 🧼
  • -Wconst-var — the combination of const and var is not illegal, but different compilers may handle them differently. we were told the intention is to create a function-pointer that isn't assignable. that's exactly how we interpret it. however, for this interpretation the var keyword is considered superfluous (and philosophically wrong), so you can get a warning about it. philosophy hour. 📚
  • -Wmultibyte-character — warns about multibyte character constants. they do not work right now. so don't. 🚫
  • -Wternary-precedence — warns if a ternary expression containing a comma operator is used without enclosing parenthesis. because that's most likely not what you actually want. we recommend the -fcorrect-ternary option. trust. 💅
  • -Wunknown-pragmas — warns when encountering an unrecognized #pragma line. the compiler is like "what is this? i don't know her." 🙈
  • -Wunreachable-code — warns about unreachable code. that is: code after a return statement, or code after a call to a function marked as noreturn. it's giving ghost code. 👻
  • -Wdebug — enables some warnings added to help debugging in the compiler. you won't need this. bestie, this is not for you. 💅
  • -Wunknown-attribute — warns on an unknown attribute. the warning will include only the first token inside the enclosing attribute-brackets. this may change when the actual attribute syntax is better defined. so it's a work in progress. 🚧
  • -Wreserved-names — warns when using reserved names such as nil. don't touch. 🚫
  • -Wuninitialized-constant — warns about global constants (using the const keyword) with no assigned value. like, you made a constant but didn't give it a value? that's a choice. 💀
  • -Wuninitialized-global — warns about global variables with no initializing value. this is off by default, and is added mostly to help find null-values which are supposed to be replaced by the untyped nil constant. so it's a niche vibe. 🧚
  • -Wdifferent-qualifiers — warns when a variable is redeclared with a different qualifier. for example, redeclaring a variable as var which was previously marked const. make up your mind. 💅
  • -Wdifferent-attributes — similar to the above but for attributes like [[noreturn]]. same energy, different drama. 🎭
  • -Wdeprecated — warns when a function is marked with the attribute [[deprecated]]. this flag enables a warning on calls to functions marked as such. so you know it's old and busted. 👵
  • -Wparenthesis — warns about possible mistakes caused by missing or wrong parenthesis. like an assignment in an if condition when there's no additional set of parens around the assignment. classic. 🙈
  • -Wunsafe-types — when passing variadic parameters via ...(N) it can happen that incompatible types are passed to functions. this enables several warnings when static typechecking cannot guarantee consistent behavior. so it's a safety net. 🕸️
  • -Wbreakdef — when compiling original id1 QC there is a definition for break which conflicts with the break keyword in GMQCC. enabling this will print a warning when the definition occurs. the definition is ignored for both cases. so it's just a heads up. 📢
  • -Wconst-overwrite — when compiling original QuakeWorld QC there are instances where code overwrites constants. this is considered an error, but for QuakeWorld to compile it needs to be treated as a warning instead. as such this warning only works when -std=qcc. special case. 🎯
  • -Wdirective-inmacro — warns about the use of preprocessor directives inside macros. that's a no-no. 🚫
  • -Wbuiltins — when using a function that is not explicitly defined, the compiler will search its intrinsics table for something that matches that function name by appending __builtin_ to it. this behaviour may be unexpected, so enabling this will produce a diagnostic when such a function is resolved to a builtin. so you know what's up. 🔍
  • -Winexact-compares — when comparing an inexact value such as 1.0/3.0 the result is pathologically wrong. enabling this will trigger a compiler warning on such expressions. so don't do math with floats like that. 😭

💖 COMPILE FLAGS 💖

okay these are the flags that change how the compiler does its thing. slay. ✨

  • -fdarkplaces-string-table-bug — adds some additional characters to the string table to compensate for a wrong boundcheck in some specific version of the darkplaces engine. so it's a workaround for a bug. 🐛
  • -fadjust-vector-fields — when assigning to field pointers of type .vector the common behaviour in compilers like fteqcc is to only assign the x-component of the pointer. this means you can use the vector as such, but you cannot use its y and z components directly. this flag fixes that behaviour. before using it, make sure your code does not depend on the buggy behaviour. so it's a fix but be careful. ⚠️
  • -fftepp — enables a partially fteqcc-compatible preprocessor. it supports all the features used in the Xonotic codebase. if you need more, write a ticket. so it's giving compatibility realness. 💅
  • -fftepp-predefs — enables some predefined macros. this only works in combination with -fftepp and is currently not included by -std=fteqcc. the following macros will be added:
__LINE__
__FILE__
__COUNTER__
__COUNTER_LAST__
__RANDOM__
__RANDOM_LAST__
__DATE__
__TIME__
__FUNC__

note that __FUNC__ is not actually a preprocessor macro, but is recognized by the parser even with the preprocessor disabled. also, fteqcc defines __NULL__ which becomes the first global. assigning it to a vector does not yield the same result as in gmqcc where __NULL__ is defined to nil (see -funtyped-nil), which will cause the vector to be zero in all components. with fteqcc only the first component will be 0, while the other two will become the first two of the global return value. this behavior is odd and relying on it should be discouraged, and thus is not supported by gmqcc. so don't rely on that. 🚫

  • -fftepp-mathdefs — enables math constant definitions. this only works in combination with -fftepp and is currently not included by -std=fteqcc. the following macros will be added:
M_E
M_LOG2E
M_LOG10E
M_LN2
M_LN10
M_PI
M_PI_2
M_PI_4
M_1_PI
M_2_PI
M_2_SQRTPI
M_SQRT2
M_SQRT1_2
M_TAU

math girls rise. 📐

  • -fftepp-indirect-expansion — turns on indirect macro expansion 🌀 this one only works when it's paired with -fftepp, and heads up, it is not included by -std=fteqcc right now. What it does is let the preprocessor vibe more like the standard C preprocessor, in that it'll let arguments of macros that get macro-expanded be substituted into the definition of the macro. Like:
#define STR1(x) #x
#define STR2(x) STR1(x)
#define THE_ANSWER 42
#define THE_ANSWER_STR STR2(THE_ANSWER) /* "42" */

With this on, expanding THE_ANSWER_STR gives you the string "42". With it off, expanding THE_ANSWER_STR gives you "THE_ANSWER". iykyk 💅

  • -frelaxed-switch — lets switch cases use non-constant variables, bestie. no cap.
  • -fshort-logic — does the early-out thing in logical AND and OR expressions. The final result is either a 0 or a 1 — peep the next flag if you want other possibilities 👀
  • -fperl-logic — in lots of languages, logical expressions early-out in a special way: if the left operand of an AND yields true, or one of an OR yields false, the whole expression evaluates to the right side. So true && 5 evaluates to 5 instead of 1. iconic behaviour fr fr ✨
  • -ftranslatable-strings — enables the underscore intrinsic: using _("A string constant") makes the string immediate get a name with a "dotranslate_" prefix. The darkplaces engine recognizes these and translates them kind of like how gettext works 🌈
  • -finitialized-nonconstants — does NOT implicitly convert initialized variables to constants. With this flag on, you actually need the const keyword to make a constant. periodt.
  • -fassign-function-types — if this flag is not set (and it is set by default in the qcc and fteqcc standards), then assigning function pointers with mismatching signatures gives you an error instead of a warning. so like, watch out 🫶
  • -flno — produces a linenumber file right alongside the output .dat file.
  • -fcorrect-ternary — uses C's operator precedence for ternary expressions. Unless your code is lowkey depending on fteqcc-compatible behaviour, you're gonna want this one 💖
  • -fsingle-vector-defs — normally vectors generate 4 defs: one for the vector, and one for each of its components with _x, _y, _z suffixes. This option stops the components from being listed. slay.
  • -fcorrect-logic — most QC compilers translate if(a_vector) directly as an IF on the vector, which means only the x-component actually gets checked 😭 This option casts vectors to actual booleans via a NOT_V and, if needed, a NOT_F chained onto it. Like:
if (a_vector) // becomes
if not(!a_vector)
// likewise
a = a_vector && a_float // becomes
a = !!a_vector && a_float
  • -ftrue-empty-strings — an empty string is considered true everywhere. The NOT_S instruction usually treats an empty string as false, and this option effectively makes the unary not on strings use NOT_F instead. 💅
  • -ffalse-empty-strings — an empty string is considered false everywhere. This means loops and if statements that depend on a string will run a NOT_S instruction on the string before using it.
  • -futf8 — enables utf8 characters 🦋 This lets you use utf-8 encoded character constants, and escape sequence codepoints in the valid utf-8 range. Effectively enabling escape sequences like '\{x2211}'. so cute.
  • -fbail-on-werror — when a warning gets treated as an error, and this option is set (which it is by default), it's like any other error and it'll make compilation stop 🛑 If you disable this flag with -fno-bail-on-werror, compilation keeps going until the end, but no output is generated. Instead, the first such error message's context gets shown.
  • -floop-labels — lets loops be labeled, and lets break and continue take an optional label to decide which loop you're actually jumping out of or continuing. main character energy:
for :outer (i = 0; i < n; ++i) {
    while (inner) {
        ...;
        if (something)
            continue outer;
    }
}
  • -funtyped-nil — adds a global named nil that has no type and can be assigned to anything. No typechecking gets done on assignments. But assigning to it is forbidden, and using it in any other kind of expression is also not allowed 🚫

Note that this is different from fteqcc's __NULL__: in fteqcc, __NULL__ maps to the integer written as '0i'. It can be assigned to function pointers and integers, but it'll error about invalid instructions when you assign it to floats without enabling the FTE instruction set. There's also a bug that lets it be assigned to vectors, for which the source will be the global at offset 0, meaning the vector's y and z components will contain the OFS_RETURN x and y components.

In gmqcc, the nil global is an actual global filled with zeroes, and it can be assigned to anything including fields, vectors or function pointers — and they all end up becoming zeroed. 💀

  • -fpermissive — various effects, usually to weaken some conditions.
    • with -funtyped-nil — allow local variables named nil. (This will not allow declaring a global of that name.)
  • -fvariadic-args — lets variadic parameters be accessed by QC code 🎀 This is done via the '...' function, which takes a parameter index and a typename. Example:
void vafunc(string...count) {
    float i;
    for (i = 0; i < count; ++i)
        print(...(i, string), "\n");
}
  • -flegacy-vector-maths — most Quake VMs, including the one from FTEQW or, up till recently, Darkplaces, do not cope well with vector instructions that have overlapping input and output. This option avoids producing such code. protecting your peace fr 💜
  • -fexpressions-for-builtins — usually builtin-numbers are just immediate constants. With this flag, expressions can be used, as long as they're compile-time constant. Example:
void printA() = #1; // the usual way
void printB() = #2-1; // with a constant expression
  • -freturn-assignments — enabling this option lets you assign values or expressions to the return keyword as if it were a local variable of the same type as the function's signature's return type 🌸 Example:
float bar() { return 1024; }
float fun() {
    return = bar();
    return; // returns value of bar
}
  • -funsafe-varargs — when passing on varargs to a different function, this turns some static error cases into warnings. Like when the caller's varargs are restricted to a different type than the callee's parameter. Or when a list of unrestricted varargs gets passed into restricted varargs. 🙈
  • -ftypeless-stores — always uses STORE_F, LOAD_F, STOREP_F when accessing scalar variables. This is kind of incorrect assembly instruction use, but in all engines they do exactly the same thing. It makes disassembly output harder to read and breaks decompilers, but it makes the output file more compressible. trade-offs, bestie ✨
  • -fsort-operands — in commutative instructions, always puts the lower-numbered operand first. This shaves off 1 byte of entropy from all these instructions, reducing the compressed size of the output file. tiny but mighty 💅
  • -femulate-state — emulates OP_STATE operations in code instead of using the instruction. The desired fps can be set via -state-fps=NUM, which defaults to 10. Specifying -state-fps implicitly sets this flag. Defaults to off in all standards.
  • -farithmetic-exceptions — turns on arithmetic exception tests in the compiler. In constant expressions that trigger exceptions like division by zero, overflow, underflow, etc, this flag produces diagnostics for what triggered that exception. very "not me catching that" energy 🔥
  • -fsplit-vector-parameters — with this flag, immediate vector literals that only ever appear as function parameters won't be stored as vector immediates. Instead, the 3 floats making up the vector get copied separately. Essentially this turns a vector-store instruction into 3 float-store instructions for those cases. This increases code size but can dramatically reduce the amount of vector globals — which is, after all, limited to 64k. There's at least one known codebase where this lowers the number of globals from over 80k down to around 3k 🫢 In other codebases it doesn't reduce the globals at all and only increases code size. Just try it and see whether it helps you. no cap.
  • -fdefault-eraseable — forces all expressions to be "eraseable", which permits the compiler to remove unused functions, variables and statements. This is equivalent to putting [[eraseable]] on all definitions. ⚠️ This is dangerous as it breaks auto cvars, definitions for functions the engine may be looking for, and translatable strings. Instead, you can mark a definition with [[noerase]] to stop this from happening. stay safe out there 🥺

✨ OPTIMIZATIONS ✨

Okay bestie, these are the -O flags that change how your QC code gets compiled. Turn them on and let the compiler do its little dance. 💅

  • -Opeephole — Some general peephole optimizations. For instance the code a = b + c typically generates 2 instructions, an ADD and a STORE. This optimization removes the STORE and lets the ADD write directly into A.
  • -Otail-recursion — Tail recursive function calls will be turned into loops to avoid the overhead of the CALL and RETURN instructions.
  • -Ooverlap-locals — Make all functions which use neither local arrays nor have locals which are seen as possibly uninitialized use the same local section. This should be pretty safe compared to other compilers which do not check for uninitialized values properly. The problem is that there's QC code out there which really doesn't initialize some values. This is fine as long as this kind of optimization isn't used, but also, only as long as the functions cannot be called in a recursive manner. Since it's hard to know whether or not an array is actually fully initialized, especially when initializing it via a loop, we assume functions with arrays to be too dangerous for this optimization.
Ngl, this one has lore. It's giving "trust me bestie, but also read the fine print" energy. 👀
  • -Olocal-temps — This promotes locally declared variables to "temps". Meaning when a temporary result of an operation has to be stored somewhere, a local variable which is not 'alive' at that point can be used to keep the result. This can reduce the size of the global section. This will not have declared variables overlap, even if it was possible.
  • -Oglobal-temps — Causes temporary values which do not need to be backed up on a CALL to not be stored in the function's locals-area. With this, a CALL to a function may need to back up fewer values and thus execute faster.
  • -Ostrip-constant-names — Don't generate defs for immediate values or even declared constants. Meaning variables which are implicitly constant or qualified as such using the 'const' keyword.
  • -Ooverlap-strings — Aggressively reuse strings in the string section. When a string should be added which is the trailing substring of an already existing string, the existing string's tail will be returned instead of the new string being added.

For example the following code will only generate 1 string:

print("Hello you!\n");
print("you!\n"); // trailing substring of "Hello you!\n"

There's however one limitation. Strings are still processed in order, so if the above print statements were reversed, this optimization would not happen.

  • -Ocall-stores — By default, all parameters of a CALL are copied into the parameter-globals right before the CALL instructions. This is the easiest and safest way to translate calls, but also adds a lot of unnecessary copying and unnecessary temporary values. This optimization makes operations which are used as a parameter evaluate directly into the parameter-global if that is possible, which is when there's no other CALL instruction in between.
  • -Ovoid-return — Usually an empty RETURN instruction is added to the end of a void typed function. However, additionally after every function a DONE instruction is added for several reasons. (For example the qcvm's disassemble switch uses it to know when the function ends.). This optimization replaces that last RETURN with DONE rather than adding the DONE additionally.
  • -Ovector-components — Because traditional QC code doesn't allow you to access individual vector components of a computed vector without storing it in a local first, sometimes people multiply it by a constant like ‘'0 1 0'’ to get, in this case, the y component of a vector. This optimization will turn such a multiplication into a direct component access. If the factor is anything other than 1, a float-multiplication will be added, which is still faster than a vector multiplication.
  • -Oconst-fold-dce — For constant expressions that result in dead code (such as a branch whos condition can be evaluated at compile-time), this will eliminate the branch and else body (if present) to produce more optimal code.

📝 CONFIG 📝

The configuration file is similar to regular .ini files. Comments start with hashtags or semicolons, sections are written in square brackets and in each section there can be arbitrary many key-value pairs.

There are 3 sections currently: ‘flags’, ‘warnings’, ‘optimizations’. They contain a list of boolean values of the form ‘VARNAME = true’ or ‘VARNAME = false’. The variable names are the same as for the corresponding -W, -f or -O flag written with only capital letters and dashes replaced by underscores.

Here's an example:

# a GMQCC configuration file
[flags]
    FTEPP = true
    ADJUST_VECTOR_FIELDS = false
    LNO = true

[warnings]
    UNUSED_VARIABLE = false
    USED_UNINITIALIZED = true

[optimizations]
    PEEPHOLE = true
    TAIL_RECURSION = true

📁 FILES 📁

  • gmqcc.ini.example — A documented example for a gmqcc.ini file.

👀 SEE ALSO 👀

💖 AUTHOR 💖

See <http://graphitemaster.github.com/gmqcc>.

🐛 BUGS 🐛

Currently the -fftepp-predefs flag is not included by -std=fteqcc, partially because it is not entirely conformant to fteqcc.

Please report bugs on <http://github.com/graphitemaster/gmqcc/issues>, or see <http://graphitemaster.github.com/gmqcc> on how to contact us.

That's the whole vibe, bestie. This page was served up by the Debian crew on January 24, 2013, and it's all about GMQCC(1). Now go compile something iconic. No cap. 💅✨

📦 where this page comes from