From: Hans-Peter Nilsson <hp@axis.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [PATCH 2/3] doc: Document testsuite check_effective_target_tail_call
Date: Mon, 6 Mar 2023 19:47:35 +0100 [thread overview]
Message-ID: <20230306184735.03643203D7@pchp3.se.axis.com> (raw)
In-Reply-To: <20230306184542.0517B20405@pchp3.se.axis.com> (message from Hans-Peter Nilsson on Mon, 6 Mar 2023 19:45:42 +0100)
Will commit as obvious, when the 1/3 tail_call is applied.
-- >8 --
Spot-checked the PDF output for sanity.
* doc/sourcebuild.texi: Document check_effective_target_tail_call.
---
gcc/doc/sourcebuild.texi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi
index c348a1e47cc3..80bef7f0a0e2 100644
--- a/gcc/doc/sourcebuild.texi
+++ b/gcc/doc/sourcebuild.texi
@@ -2844,6 +2844,9 @@ Target supports named sections.
Target uses natural alignment (aligned to type size) for types of
32 bits or less.
+@item tail_call
+Target supports tail-call optimizations.
+
@item target_natural_alignment_64
Target uses natural alignment (aligned to type size) for types of
64 bits or less.
--
2.30.2
next prev parent reply other threads:[~2023-03-06 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 18:45 [PATCH 1/3] testsuite: Add tail_call effective target Hans-Peter Nilsson
2023-03-06 18:47 ` Hans-Peter Nilsson [this message]
2023-03-06 18:50 ` [PATCH 3/3] testsuite: Gate gcc.dg/plugin/must-tail-call-1.c and -2.c on tail_call Hans-Peter Nilsson
2023-03-06 18:52 ` [PATCH] testsuite: Support scanning tree-dumps Hans-Peter Nilsson
2023-03-06 21:17 ` Mike Stump
2023-03-06 21:14 ` [PATCH 1/3] testsuite: Add tail_call effective target Mike Stump
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=20230306184735.03643203D7@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=gcc-patches@gcc.gnu.org \
/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).