public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH] Clarify documentation for -fpie and -fPIE
@ 2018-04-30 13:17 Jonathan Wakely
  2018-04-30 16:05 ` Jeff Law
  0 siblings, 1 reply; 2+ messages in thread
From: Jonathan Wakely @ 2018-04-30 13:17 UTC (permalink / raw)
  To: gcc-patches

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

I noticed a couple of missing definite articles in the description of
-fpie and -fPIE, and found the last sentence unclear. This clarifies
that it means you should use these options during compilation if you
plan to use -pie during linking (rather than implying you use these
during linking as well).

I also added a hyphen to "position independent" but maybe that part
should wait for a decision on
https://gcc.gnu.org/ml/gcc/2018-04/msg00196.html


	* doc/invoke.texi (-fpie, -fPIE): Fix grammar and clarify
	interaction with -pie.

OK for trunk?


[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1130 bytes --]

commit 169e8c617d502eae8ef37ea60cd199286d318863
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Apr 30 13:26:10 2018 +0100

    Clarify documentation for -fpie and -fPIE
    
            * doc/invoke.texi (-fpie, -fPIE): Fix grammar and clarify
            interaction with -pie.

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 606e9152cfc..efe66e37901 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -13094,10 +13094,10 @@ are defined to 2.
 @itemx -fPIE
 @opindex fpie
 @opindex fPIE
-These options are similar to @option{-fpic} and @option{-fPIC}, but
-generated position independent code can be only linked into executables.
-Usually these options are used when @option{-pie} GCC option is
-used during linking.
+These options are similar to @option{-fpic} and @option{-fPIC}, but the
+generated position-independent code can be only linked into executables.
+Usually these options are used to compile code that will be linked using
+the @option{-pie} GCC option.
 
 @option{-fpie} and @option{-fPIE} both define the macros
 @code{__pie__} and @code{__PIE__}.  The macros have the value 1

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH] Clarify documentation for -fpie and -fPIE
  2018-04-30 13:17 [PATCH] Clarify documentation for -fpie and -fPIE Jonathan Wakely
@ 2018-04-30 16:05 ` Jeff Law
  0 siblings, 0 replies; 2+ messages in thread
From: Jeff Law @ 2018-04-30 16:05 UTC (permalink / raw)
  To: Jonathan Wakely, gcc-patches

On 04/30/2018 06:51 AM, Jonathan Wakely wrote:
> I noticed a couple of missing definite articles in the description of
> -fpie and -fPIE, and found the last sentence unclear. This clarifies
> that it means you should use these options during compilation if you
> plan to use -pie during linking (rather than implying you use these
> during linking as well).
> 
> I also added a hyphen to "position independent" but maybe that part
> should wait for a decision on
> https://gcc.gnu.org/ml/gcc/2018-04/msg00196.html
> 
> 
>     * doc/invoke.texi (-fpie, -fPIE): Fix grammar and clarify
>     interaction with -pie.
> 
> OK for trunk?
> 
OK
jeff

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-04-30 15:53 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-30 13:17 [PATCH] Clarify documentation for -fpie and -fPIE Jonathan Wakely
2018-04-30 16:05 ` Jeff Law

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).