On Thu, Apr 28, 2011 at 6:36 AM, Sisyphus <[email protected]> wrote: >> >> All win64-targeting toolchains created after 2010-04-28, including >> the sezero's gcc-4.4-based personal builds follow the MS convention. > > Just a quick follow-up question on that. > > Is there a simple way for a program to determine the date that the compiler > was built ? > (A #define that tells us would be ideal, if such exists.) > > I know we can peruse the output of 'gcc -v' or 'gcc --version', though even > that doesn't show us the date for the 2 sezero builds I looked at.
For my personal buikds, "gcc -v" gives a hint about the revision date about the gcc used in that build, like: gcc version 4.4.6 20110416 (release) [svn/rev.172578 - mingw-w64/oz] (GCC) However you should know which build you downloaded, for both personal and automated builds, for more detailed specifics about the toolchain in question. > > Cheers, > Rob -- Ozkan ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
