TDM-GCC is from the MINGW-W64 project patch, all using static links, the thread does not need additional DLLs, the default use of SJLJ exception (really good things)

Windows version of GCC TDM-GCC 4.5.2

Usually write a C + + small program, do not like to open vs, too large, but also to build projects. For small programs, a single-file compilation of the IDE is my first choice, I use C-free 5.0, built-in compiler version Mingw,windows GCC.

The first few in C-free 5.0 write sort program, want to see the approximate execution time, so with C standard library function clock (), the result contains the Time.h header file can not be compiled. Copy the source code to VS 2008 actually successfully compiled pass, guess this should be compiler MinGW problem, endure it.

The day before yesterday to make a tread bad, helpless under restore, today found a latest version of the MinGW compiler, did not think time.h the problem of the head file is not, cool.

In fact, I am not using the official version of MinGW, but another release version TDM-GCC, currently the latest version of 4.5.2, a brief introduction of translation:

TDM-GCC is a version of the compiler suite for Windows.
It combines the latest stable releases from the GCC toolset, including the free and open source MinGW or MINGW-W64 runtime APIs, creating a LIBRE to replace the Microsoft compiler and its platform SDK.
It can create a 32-bit or 64-bit binary file that is on top of any Windows operating system version since Windows 95.

Offers a: http://tdm-gcc.tdragon.net/

In addition, on a blog has the following paragraph:

TDM (Twilight Dragon Media) has nothing to do with the official MinGW. The version of the package in TDM is generally newer than the official version of MinGW, and it seems that MinGW members are also using the TDM version. There seems to be quite a lot of people who have this kind of power.

TDM GCC is divided into two versions (exception handling in different ways)

SJLJ (SETJMP/LONGJMP)
DW2 (Dwarf-2)
The latter is used in MinGW, and TDM GCC recommends the first choice.

Http://www.cnblogs.com/wxxweb/archive/2011/05/30/2063434.html

--------------------------------------------------------------------------------------------------------------- --

Self-explanatory:

TDM-GCC is pleased to present new toolchains based on GCC 5.1.0, as well as updated GDB packages for 32-bit and 64-bit NAT Ive Windows.

This TDM-GCC release incorporates a few more local patches from the MINGW-W64 project ' s mingw-builds releases. Also, a 32-bit gdb is now available, and both 32-bit and 64-bit GDB automatically load GCC ' s libstdc++ "pretty Printers", If available, to provide more readable debugging output for libstdc++ objects. See the README files included in the core and GDB packages for details on all local patches.

Sure to read the Quirks page for more information about the differences between TDM-GCC and other GCC Toolchai Ns.

Http://tdm-gcc.tdragon.net/quirks

--------------------------------------------------------------------------------------------------------------- --

Main differences:

Static Runtime linkage (LIBGCC & Friends)

• TDM-GCC doesn ' t link your programs with the LIBGCC or libstdc++ runtime DLLs by default.
• Other toolchains Default-DLL runtime linkage in order-to-allow-you-to-throw exceptions among DLLs and EXEs.
• TDM-GCC lets you throw exceptions among DLLs and EXEs even with the static runtime.
• Your programs won't rely on any additional DLLs when compiling with default options.
• TDM-GCC still includes DLL versions of the LIBGCC and Libstdc++ runtimes, which you can enable for your program with "-sha RED-LIBGCC "and"-shared-libstdc++ "if desired.

Http://tdm-gcc.tdragon.net/quirks

TDM-GCC is from the MINGW-W64 project patch, all using static links, the thread does not need additional DLLs, the default use of SJLJ exception (really good things)