Bugs in the Debian/GNU GNU compiler setup
=========================================

Before reporting a bug, please
------------------------------

- Check that the behaviour really is a bug. Have a look into some
  ANSI standards document.
- Check at the end of this document for known bugs/behaviour.
- Check http://www.debian.org/Bugs, if this behaviour / this bug already
  is reported.
- Check http://gcc.gnu.org/bugs.html for known bugs.

When reporting a bug, please
----------------------------

- read /usr/doc/debian/bug-reporting.txt
- read http://gcc.gnu.org/faq.html#bugreport.
- included the PREPROCESSED output (foo.i or foo.ii) in your report.
- decide where to report the bug. Please send a CC to gcc@packages.debian.org,
  if you decide to report the bug directly to gcc-bugs@gcc.gnu.org.

How to report a bug
-------------------

[Taken from http://gcc.gnu.org/faq.html#bugreport]

There are complete instructions in the egcs/gcc info manual, section Bugs.
The manual can also be read using `M-x info' in Emacs, or if the GNU info
program is installed on your system by `info --node "(gcc)Bugs"'. Or see
the file BUGS included with the egcs source code.

Before you report a bug for the C++ compiler, please check the list of
well-known bugs. If you want to report a bug with an earlier version, we
recommend upgrading to the current release first.

In short, if gcc/egcs says Internal compiler error (or any other error that
you'd like us to be able to reproduce, for that matter), please mail a bug
report to gcc-bugs@gcc.gnu.org including:

    - The egcs/gcc version 
    - The system type
    - All options you passed to egcs
    - Preprocessed output of the source file that caused the compiler error 

All this can normally be accomplished by mailing the command line, the output
of the command, and the resulting `your-file.i' for C, or `your-file.ii' for
C++, corresponding to:

    gcc -v --save-temps all-your-options your-file.c 

Typically the CPP output will be large, so please compress the resulting file
with one of the popular compression programs such as gzip, bzip2, compress or
pkzip, then include the compressed CPP output as an attachment to your message.

The egcs lists have message size limits (100 kbytes) and bug reports over
those limits will currently be bounced. We're trying to find a way to allow
larger bug reports to be posted, but this is currently impossible. So,
although we prefer to have complete bug reports archived, if you cannot reduce
the bug report below the limit, please make it available for ftp or http and
post the URL.

Known Bugs and Non-Bugs
-----------------------

[Please see http://gcc.gnu.org/faq.html first]

[EDIT ME: scan Debian bug reports and write some nice summaries ...]