A compiler suite for 32- and 64-bit Windows based on the GNU toolchain
Rules for reporting bugs
Above all else, put yourself in the developer's shoes! Imagine yourself as the
recipient of the bug report you're about to submit, and make sure you keep it as
simple, legible, and polite as possible while providing all relevant
- DO provide a thorough description of the bug -- copy GCC's error output, if
any, and describe what the expected result should be.
- DO provide a single-file, preprocessed test case. Just add
"-save-temps" to your command line; the ".i" or
".ii" file it creates is the preprocessed source.
- DO state your edition of Windows, GCC verbose version ("gcc -v"),
binutils ld version ("ld -v"), and build environment (Windows shell,
mSYS, Cygwin, an IDE).
- DO NOT file a bug stating only that you encountered a bug compiling some
other library. It's best for you to instead report the bug to that library's
developers. At the very least, narrow the problem down to a single file from the
library and attach that file (preprocessed, of course) to the bug report.
TDM-GCC SourceForge tracker
You can submit a bug report at
SourceForge bug tracker
. A SourceForge account is not required, but you must
have one if you want to receive email notifications when the bug is updated.