------- Comment #3 from pinskia at gcc dot gnu dot org 2005-12-31 00:14 ------- Does anyone read: http://gcc.gnu.org/bugs.html
What we do not want A source file that #includes header files that are left out of the bug report (see above) That source file and a collection of header files. An attached archive (tar, zip, shar, whatever) containing all (or some :-) of the above. A code snippet that won't cause the compiler to produce the exact output mentioned in the bug report (e.g., a snippet with just a few lines around the one that apparently triggers the bug, with some pieces replaced with ellipses or comments for extra obfuscation :-) The location (URL) of the package that failed to build (we won't download it, anyway, since you've already given us what we need to duplicate the bug, haven't you? :-) An error that occurs only some of the times a certain file is compiled, such that retrying a sufficient number of times results in a successful compilation; this is a symptom of a hardware problem, not of a compiler bug (sorry) Assembly files (*.s) produced by the compiler, or any binary files, such as object files, executables, core files, or precompiled header files Duplicate bug reports, or reports of bugs already fixed in the development tree, especially those that have already been reported as fixed last week :-) Bugs in the assembler, the linker or the C library. These are separate projects, with separate mailing lists and different bug reporting procedures Bugs in releases or snapshots of GCC not issued by the GNU Project. Report them to whoever provided you with the release Questions about the correctness or the expected behavior of certain constructs that are not GCC extensions. Ask them in forums dedicated to the discussion of the programming language -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25608
