Lines Matching refs:GCC

474     In addition GCC 8 is clever enough that it knows that strlen on char[4] can
1776     * GCC 10 will switch the default to `-fno-common`.
2720     When compiling with link time optimization, GCC thinks it's discovered
2740     where GCC believes that PanoramiXNumScreens might be 0. Unfortunately
2741     GCC is just smart enough to be an annoyance because this case is not
2747     GCC with information even in release builds and lets GCC understand that
6690     This slightly alters the GCC preprocessor output which this fragile
6691     code could not deal with when using GCC 5+
29666     using the GCC compiler.
29668     In 16bit code produced by the GCC compiler, the 0x66 prefix is used
39776     The logic was twisted though, confusing GCC's uninitialized value
39811     error return code, but GCC can't figure that out, so just initialize
41297     xserver: Move 'pragma GCC diagnostic' outside functions
41303 …/jhbuild/checkout/xorg/xserver/os/log.c:199: error: #pragma GCC diagnostic not allowed inside func…
41305 …/jhbuild/checkout/xorg/xserver/os/log.c:212: error: #pragma GCC diagnostic not allowed inside func…
42316     support #pragma GCC diagnostic ignored"), some compile time
42325     log.c:199:9: error: #pragma GCC diagnostic not allowed inside functions
42327     log.c:212:9: error: #pragma GCC diagnostic not allowed inside functions
42805     GCC 4.2 doesn't accept 2 typedef declarations of the same type, so
44688     contains only a character, causing GCC to complain. Add the missing
47208     value. This keeps GCC from emitting a warning when the server is
50381     gcc 4.2.1 doesn't support #pragma GCC diagnostic ignored
69114     tests: move GCC diagnostics pragma outside of function
69118     signal-logging.c:210: error: #pragma GCC diagnostic not allowed inside
80520     This silences the GCC warning:
100404     problems with GCC 4.3.3. Even if the problems still persisted, this
100406     should be modified to be empty if GCC/ARM is used. However, currently
107110     Silence GCC warning about uninitialized lastSlave variable
110262     else, so just use the format string literal. This makes GCC happy since
119476     Suppress certain GCC warnings in auto-generated code.
119490     GCC warns about casting a double return value to int.
119499     Suppress GCC warnings like "the address of `u1' will always evaluate as `true'".
120310     On 64-bit systems, int and pointers don't have the same size, so GCC gives
120324     Fix GCC warnings in xorg_backtrace
122989     the platform is Compaq C, and it doesn't support GCC style inline
188657         on having GCC 3.4 on i386.