From the GCC manual: Many options have long names starting with -f or with -W—for example, -fforce-mem, -fstrength-reduce, -Wformat and so on. Most of these have both positive and negative forms; the negative form of -ffoo would be -fno-foo. This manual documents only one of these two forms, whichever one is not the default. But …
Ad 1. Those types are designed to work with numbers with huge dynamic range. The long double is implemented in a native way in the x87 FPU. The 128b double I suspect would be implemented in software mode on modern x86s, as there’s no hardware to do the computations in hardware. The funny thing is …
CMake generates files for other build systems. These can be Makefiles, Ninja files or projects files for IDEs like Visual Studio or Eclipse. The build files contain calls to compilers like GCC, Clang, or cl.exe. If you have several compilers installed, you can choose one. All three parts are independent. The compiler, the build system …
I’m not sure what the correct warning is, but once you’ve found it, you can change its disposition with the following (using ‘format’ as the example): #pragma GCC diagnostic error “-Wformat” Or as strager points out: gcc -Werror=format … I’ve checked the gcc source for this and this specific warning cannot be disabled via command …
GCC 4.8 introduces a new optimization level: -Og for the best of both worlds. -Og Optimize debugging experience. -Og enables optimizations that do not interfere with debugging. It should be the optimization level of choice for the standard edit-compile-debug cycle, offering a reasonable level of optimization while maintaining fast compilation and a good debugging experience. …
See this answer. Is this even the correct approach here No: you can’t use mismatched versions of glibc as your link command does. You used crt0.o and ld-linux.so from new (system-installed) libc, but libc.so.6 from an old (copied from cluster) libc. That is just not going to work.
Gcc 4.9 seems to have added this feature via the -fdiagnostics-color flag:
You probably want #error: $ cd /tmp $ g++ -Wall -DGoOn -o stopthis stopthis.cpp $ ./stopthis Hello, world $ g++ -Wall -o stopthis stopthis.cpp stopthis.cpp:7:6: error: #error I had enough File stopthis.cpp #include <iostream> int main(void) { std::cout << “Hello, world\n”; #ifndef GoOn #error I had enough #endif return 0; }
Gcc uses specs-strings, which control which subprocesses to run and what parameters it shall pass to them. The behavior defined by the spec-strings can be overridden using spec-files, whose purpose and syntax is documented here: https://gcc.gnu.org/onlinedocs/gcc/Spec-Files.html Looking at these spec files in the lib folder of the gcc tool chain (e.g. /usr/lib/arm-none-eabi/lib) we can see …
Any idea about what I might be doing wrong? The t function is indeed local to the library. This could happen due to a number or reasons. The most likely ones are: You declared the function static, or You compiled the library with -fvisibility=hidden and did not have __attribute__((visibility(“default”))) on the function, or You linked …