public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH] doc: Update -falign-functions/-falign-loops/-falign-jumps
@ 2020-03-28 21:34 H.J. Lu
  2020-03-29 22:04 ` Sandra Loosemore
  0 siblings, 1 reply; 2+ messages in thread
From: H.J. Lu @ 2020-03-28 21:34 UTC (permalink / raw)
  To: gcc-patches

Change -falign-functions=N to

    Align the start of functions to the next power-of-two greater than
    or equal to N.

Add

    If '-falign-labels' is greater than this value, then its value is
    used instead.

to -falign-loops=N and -falign-jumps=N.

OK for master?

H.J.
--
	PR driver/94381
	* doc/invoke.texi: Update -falign-functions, -falign-loops and
	-falign-jumps documentation.
---
 gcc/doc/invoke.texi | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index c2053a3804f..412750c1fc9 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -10939,9 +10939,9 @@ The @option{-fstrict-aliasing} option is enabled at levels
 @itemx -falign-functions=@var{n}:@var{m}:@var{n2}
 @itemx -falign-functions=@var{n}:@var{m}:@var{n2}:@var{m2}
 @opindex falign-functions
-Align the start of functions to the next power-of-two greater than
-@var{n}, skipping up to @var{m}-1 bytes.  This ensures that at least
-the first @var{m} bytes of the function can be fetched by the CPU
+Align the start of functions to the next power-of-two greater than or
+equal to @var{n}, skipping up to @var{m}-1 bytes.  This ensures that at
+least the first @var{m} bytes of the function can be fetched by the CPU
 without crossing an @var{n}-byte alignment boundary.
 
 If @var{m} is not specified, it defaults to @var{n}.
@@ -11007,6 +11007,9 @@ Align loops to a power-of-two boundary.  If the loops are executed
 many times, this makes up for any execution of the dummy padding
 instructions.
 
+If @option{-falign-labels} is greater than this value, then its value
+is used instead.
+
 Parameters of this option are analogous to the @option{-falign-functions} option.
 @option{-fno-align-loops} and @option{-falign-loops=1} are
 equivalent and mean that loops are not aligned.
@@ -11026,6 +11029,9 @@ Align branch targets to a power-of-two boundary, for branch targets
 where the targets can only be reached by jumping.  In this case,
 no dummy operations need be executed.
 
+If @option{-falign-labels} is greater than this value, then its value
+is used instead.
+
 Parameters of this option are analogous to the @option{-falign-functions} option.
 @option{-fno-align-jumps} and @option{-falign-jumps=1} are
 equivalent and mean that loops are not aligned.
-- 
2.25.1


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

* Re: [PATCH] doc: Update -falign-functions/-falign-loops/-falign-jumps
  2020-03-28 21:34 [PATCH] doc: Update -falign-functions/-falign-loops/-falign-jumps H.J. Lu
@ 2020-03-29 22:04 ` Sandra Loosemore
  0 siblings, 0 replies; 2+ messages in thread
From: Sandra Loosemore @ 2020-03-29 22:04 UTC (permalink / raw)
  To: H.J. Lu, gcc-patches

On 3/28/20 3:34 PM, H.J. Lu via Gcc-patches wrote:
> Change -falign-functions=N to
> 
>      Align the start of functions to the next power-of-two greater than
>      or equal to N.
> 
> Add
> 
>      If '-falign-labels' is greater than this value, then its value is
>      used instead.
> 
> to -falign-loops=N and -falign-jumps=N.
> 
> OK for master?
> 
> H.J.
> --
> 	PR driver/94381
> 	* doc/invoke.texi: Update -falign-functions, -falign-loops and
> 	-falign-jumps documentation.

OK.

-Sandra

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

end of thread, other threads:[~2020-03-29 22:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-28 21:34 [PATCH] doc: Update -falign-functions/-falign-loops/-falign-jumps H.J. Lu
2020-03-29 22:04 ` Sandra Loosemore

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).