diff options
| author | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2004-07-02 23:57:12 +0000 |
|---|---|---|
| committer | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2004-07-02 23:57:12 +0000 |
| commit | 153e79bc70f4750380851847e107ccff1f763fbe (patch) | |
| tree | 958b578b1dceccdb7246fb9f76df3bb9c636e4e2 /gcc/doc/bugreport.texi | |
| parent | f10ff0e0180ce8d4b427df5dbe7e21cd8dbfc6db (diff) | |
| download | gcc-153e79bc70f4750380851847e107ccff1f763fbe.tar.gz | |
* doc/bugreport.texi, doc/configterms.texi, doc/contrib.texi,
doc/contribute.texi, doc/cpp.texi, doc/cppinternals.texi,
doc/extend.texi, doc/install.texi, doc/invoke.texi, doc/md.texi,
doc/portability.texi, doc/tree-ssa.texi, doc/trouble.texi: Avoid
some first-person references and patronizing comments. Based on
printed manual.
* doc/invoke.texi: Don't reference fortran@gnu.org.
* doc/trouble.texi (Warning when a non-void function value is
ignored): Rewrite. From Russ Allbery and Chris Devers.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@84034 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc/bugreport.texi')
| -rw-r--r-- | gcc/doc/bugreport.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/gcc/doc/bugreport.texi b/gcc/doc/bugreport.texi index d9613ef6d1c..9e10af910dc 100644 --- a/gcc/doc/bugreport.texi +++ b/gcc/doc/bugreport.texi @@ -1,5 +1,5 @@ @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, -@c 1999, 2000, 2001, 2003 Free Software Foundation, Inc. +@c 1999, 2000, 2001, 2003, 2004 Free Software Foundation, Inc. @c This is part of the GCC manual. @c For copying conditions, see the file gcc.texi. @@ -76,8 +76,8 @@ compiler bug. @item If the compiler does not produce an error message for invalid input, that is a compiler bug. However, you should note that your idea of -``invalid input'' might be my idea of ``an extension'' or ``support -for traditional practice''. +``invalid input'' might be someone else's idea of ``an extension'' or +``support for traditional practice''. @item If you are an experienced user of one of the languages GCC supports, your @@ -88,7 +88,7 @@ suggestions for improvement of GCC are welcome in any case. @section How and where to Report Bugs @cindex compiler bugs, reporting -Bugs should be reported to our bug database. Please refer to +Bugs should be reported to the GCC bug database. Please refer to @uref{http://gcc.gnu.org/bugs.html} for up-to-date instructions how to submit bug reports. Copies of this file in HTML (@file{bugs.html}) and plain text (@file{BUGS}) are also part of GCC releases. |