BlogTech

How can I tell if I'm using libc++ ?

If you're writing cross-platform code, sometimes you need to know what standard library you are using. In theory, they should all offer equivalent functionality, but that's just theory. Sometimes you just need to know. The best way to check for libc is to look for the preprocessor symbol _LIBCPP_VERSION. If that's defined, then you're using libc++.

    #ifdef  _LIBCPP_VERSION
    //  libc   specific code here
    #else
    //  generic code here
    #endif

Note that this symbol is only defined after you include any of the libc++ header files. If you need a small header file to include just for this, you can do:

    #include <ciso646>

The header file "ciso646" is required by both the C++03 and C++11 standards, and defined to do nothing.

Other significant improvements GCC can now emit code for protecting applications from stack-smashing attacks. The protection is realized by buffer overflow detection and reordering of stack variables to avoid pointer corruption. Some built-in functions have been fortified to protect them against various buffer overflow (and format string) vulnerabilities. Compared to the mudflap bounds checking feature, the safe builtins have far smaller overhead. This means that programs built using safe builtins should not experience any measurable slowdown.

Buffer overflow protection - Wikipedia, the free encyclopedia

gcc 3.4.4 support (22 August, 2005) eliminate the protection instrument from the function that defines buffers, but doesn't use them. fix buffer address corruptions in the case where multiple sub-blocks have buffers. gcc 4.1 stage2 incorporates "Reimplementation of IBM Pro Police Stack Detector." (17 July, 2005)

Setting up Code::Blocks and MINGW, A Free C and C Compiler, on Windows - Cprogramming.com

Map

Programming and Web Design

Using the Free SDCC C Compiler to Develop Firmware for the DS89C430/450 Family of Microcontrollers - Maxim

Keyworks: compiler,assembler,microcontroller,c,develop,firmware