OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

gcc.texi: More changes related to list conversion.

Browse Source 
* gcc.texi: More changes related to list conversion.
        * invoke.texi: Likewise.

From-SVN: r28250
This commit is contained in:
Jeffrey A Law 1999-07-26 03:59:19 +00:00 committed by Jeff Law
parent 0e8b618835
commit 1e1ec63328
3 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -1,3 +1,8 @@
Sun Jul 25 21:40:33 1999 Jeffrey A Law (law@cygnus.com)
* gcc.texi: More changes related to list conversion.
* invoke.texi: Likewise.
Sun Jul 25 18:15:39 1999 Richard Henderson <rth@cygnus.com>
* builtins.c (expand_builtin_saveregs): Remove static, remove exp

4
gcc/gcc.texi
View File

@ -2674,13 +2674,13 @@ GNU CC distribution.
If you would like to help pretest GNU CC releases to assure they work
well, or if you would like to work on improving GNU CC, please contact
the maintainers at @code{egcs@@egcs.cygnus.com}. A pretester should
the maintainers at @code{gcc@@gcc.gnu.org}. A pretester should
be willing to try to investigate bugs as well as report them.
If you'd like to work on improvements, please ask for suggested projects
or suggest your own ideas. If you have already written an improvement,
please tell us about it. If you have not yet started work, it is useful
to contact @code{egcs@@egcs.cygnus.com} before you start; the
to contact @code{gcc@@gcc.gnu.org} before you start; the
maintainers may be able to suggest ways to make your extension fit in
better with the rest of GNU CC and with other development plans.

2
gcc/invoke.texi
View File

@ -2503,7 +2503,7 @@ These two options are intended to be removed someday, once
they have helped determine the efficacy of various
approaches to improving loop optimizations.
Please let us (@code{egcs@@egcs.cygnus.com} and @code{fortran@@gnu.org})
Please let us (@code{gcc@@gcc.gnu.org} and @code{fortran@@gnu.org})
know how use of these options affects
the performance of your production code.
We're very interested in code that runs @emph{slower}