diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2018-09-18 15:19:55 +0100 |
|---|---|---|
| committer | Jonathan Wakely <redi@gcc.gnu.org> | 2018-09-18 15:19:55 +0100 |
| commit | 5e594075c8e0f05741b3c961959bf3a4c1f42e9b (patch) | |
| tree | a1fbc9ae619b7e1e00d5f301cd1067a470445957 | |
| parent | 538d2d7e7ff408c15c89d0fe2c6ef812e7f951a7 (diff) | |
| download | gcc-5e594075c8e0f05741b3c961959bf3a4c1f42e9b.zip gcc-5e594075c8e0f05741b3c961959bf3a4c1f42e9b.tar.gz gcc-5e594075c8e0f05741b3c961959bf3a4c1f42e9b.tar.bz2 | |
PR other/87353 fix formatting and grammar in manual
The changes to invoke.texi in r242433 left some unwanted spaces that
texi2pod.pl interprets as verbatim formatting. There are also some
grammatical errors due to the removal of references to GCJ, where the
G++ driver is referred to in the plural.
PR other/87353
* doc/invoke.texi (Link Options): Fix formatting and grammar.
From-SVN: r264395
| -rw-r--r-- | gcc/ChangeLog | 5 | ||||
| -rw-r--r-- | gcc/doc/invoke.texi | 9 |
2 files changed, 9 insertions, 5 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 324a89b..33cc32f 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2018-09-18 Jonathan Wakely <jwakely@redhat.com> + + PR other/87353 + * doc/invoke.texi (Link Options): Fix formatting and grammar. + 2018-09-18 Richard Biener <rguenther@suse.de> PR middle-end/63155 diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 94304c3..685c211 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -12625,9 +12625,9 @@ of these is when the application wishes to throw and catch exceptions across different shared libraries. In that case, each of the libraries as well as the application itself should use the shared @file{libgcc}. -Therefore, the G++ and driver automatically adds @option{-shared-libgcc} - whenever you build a shared library or a main executable, because C++ - programs typically use exceptions, so this is the right thing to do. +Therefore, the G++ driver automatically adds @option{-shared-libgcc} +whenever you build a shared library or a main executable, because C++ +programs typically use exceptions, so this is the right thing to do. If, instead, you use the GCC driver to create shared libraries, you may find that they are not always linked with the shared @file{libgcc}. @@ -12641,8 +12641,7 @@ propagate through such shared libraries, without incurring relocation costs at library load time. However, if a library or main executable is supposed to throw or catch -exceptions, you must link it using the G++ driver, as appropriate -for the languages used in the program, or using the option +exceptions, you must link it using the G++ driver, or using the option @option{-shared-libgcc}, such that it is linked with the shared @file{libgcc}. |