public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: richard.guenther@gmail.com, hubicka@ucw.cz, gcc-patches@gcc.gnu.org
Cc: Palmer Dabbelt <palmer@rivosinc.com>
Subject: [PATCH v2 1/3] doc: -falign-functions doesn't override the __attribute__((align(N)))
Date: Tue, 11 Oct 2022 14:01:54 -0700	[thread overview]
Message-ID: <20221011210156.7710-2-palmer@rivosinc.com> (raw)
In-Reply-To: <20221011210156.7710-1-palmer@rivosinc.com>

I found this when reading the documentation for Kito's recent patch.
From the discussion it sounds like this is the desired behavior, so
let's document it.

gcc/doc/ChangeLog

	* invoke.texi (-falign-functions): Mention __align__
---
 gcc/doc/invoke.texi | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 2a9ea3455f6..8326a60dcf1 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -13136,7 +13136,9 @@ effective only in combination with @option{-fstrict-aliasing}.
 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.
+without crossing an @var{n}-byte alignment boundary.  This does not override
+functions that otherwise specify their own alignment constraints, such as via
+an alignment attribute.
 
 If @var{m} is not specified, it defaults to @var{n}.
 
-- 
2.34.1


  reply	other threads:[~2022-10-11 21:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 21:01 [PATCH v2 0/3] doc: -falign-functions improvements Palmer Dabbelt
2022-10-11 21:01 ` Palmer Dabbelt [this message]
2022-11-14 14:54   ` [PATCH v2 1/3] doc: -falign-functions doesn't override the __attribute__((align(N))) Richard Biener
2022-10-11 21:01 ` [PATCH v2 2/3] doc: -falign-functions is ignored under -Os Palmer Dabbelt
2022-10-11 22:15   ` Eric Gallager
2022-10-12  7:24   ` Jan Hubicka
2022-10-11 21:01 ` [PATCH v2 3/3] doc: -falign-functions is ignored for cold/size-optimized functions Palmer Dabbelt
2022-11-14 14:54   ` Richard Biener

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221011210156.7710-2-palmer@rivosinc.com \
    --to=palmer@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=richard.guenther@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).