OAR

RTEMS GNU Tools On-Line Library


Bugs

PREV UP NEXT Bookshelf Using and Porting the GNU Compiler Collection (GCC)

Chapter 8: Reporting Bugs

Your bug reports play an essential role in making GCC reliable.

When you encounter a problem, the first thing to do is to see if it is already known. See Trouble. If it isn't known, then you should report the problem.

Reporting a bug may help you by bringing a solution to your problem, or it may not. (If it does not, look in the service directory; see Service.) In any case, the principal function of a bug report is to help the entire community by making the next version of GCC work better. Bug reports are your contribution to the maintenance of GCC.

Since the maintainers are very overloaded, we cannot respond to every bug report. However, if the bug has not been fixed, we are likely to send you a patch and ask you to tell us whether it works.

In order for a bug report to serve its purpose, you must include the information that makes for fixing the bug.

  • Criteria Have you really found a bug?
  • Where Where to send your bug report.
  • Reporting How to report a bug effectively.
  • Patches How to send a patch for GCC.
  • Known Known problems.
  • Help Where to ask for help.

  • PREV UP NEXT Bookshelf Using and Porting the GNU Compiler Collection (GCC)

    Packaging copyright © 1988-2000 OAR Corporation
    Context copyright by each document's author. See Free Software Foundation for information.