🚀 go-pugleaf

If you compile a program with GCC, and the result doesn't work, it
could be that you have found a bug in GCC.  What should you do about it?

It's not helpful to ask whether GCC is known to have bugs.  Any program
as large as GCC surely has bugs.

It's not helpful to ask whether GCC has many bugs or few bugs, because
the answer is irrelevant to what has happened to you.  Most likely you
have hit one particular bug.  Each test case is different, and it
isn't useful to generalize about them.

The only thing that is helpful is to send a proper bug report.  That
is helpful because it might lead to fixing the bug.

We are all in this together.  Bugs are fixed when people send workable
bug reports.  If you don't do it, how can you expect someone else to
do it?

To make your bug report usable, you need to supply the right
information.  Read the chapter on bugs in the GCC manual to see what
is involved.

It is possible that the problem does not result from a GCC bug.  There
are undefined cases in C that work differently with different
compilers; it's possible that you have found one of these cases in the
program you compiled.  If so, that is a bug in that program, rather
than a GCC bug.  However, the same steps needed to prepare for a
usable GCC bug report would also find the bug in the other program.