public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/marxin/heads/sphinx-v2)] Move back hooks defined in deftypevrx.
Date: Wed, 23 Jun 2021 11:30:08 +0000 (GMT) [thread overview]
Message-ID: <20210623113008.13BB13984C16@sourceware.org> (raw)
https://gcc.gnu.org/g:1bd1ccf77319a7f4ad3e44a2661327881b69097a
commit 1bd1ccf77319a7f4ad3e44a2661327881b69097a
Author: Martin Liska <mliska@suse.cz>
Date: Wed Jun 23 13:27:32 2021 +0200
Move back hooks defined in deftypevrx.
Diff:
---
.../output-of-data.rst | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/gcc/doc/gccint/target-macros/defining-the-output-assembler-language/output-of-data.rst b/gcc/doc/gccint/target-macros/defining-the-output-assembler-language/output-of-data.rst
index 24a5d4fb095..456e86dc275 100644
--- a/gcc/doc/gccint/target-macros/defining-the-output-assembler-language/output-of-data.rst
+++ b/gcc/doc/gccint/target-macros/defining-the-output-assembler-language/output-of-data.rst
@@ -8,6 +8,22 @@
Output of Data
^^^^^^^^^^^^^^
+.. c:var:: const char * TARGET_ASM_ALIGNED_HI_OP
+.. c:var:: const char * TARGET_ASM_ALIGNED_HI_OP
+.. c:var:: const char * TARGET_ASM_ALIGNED_PSI_OP
+.. c:var:: const char * TARGET_ASM_ALIGNED_SI_OP
+.. c:var:: const char * TARGET_ASM_ALIGNED_PDI_OP
+.. c:var:: const char * TARGET_ASM_ALIGNED_DI_OP
+.. c:var:: const char * TARGET_ASM_ALIGNED_PTI_OP
+.. c:var:: const char * TARGET_ASM_ALIGNED_TI_OP
+.. c:var:: const char * TARGET_ASM_UNALIGNED_HI_OP
+.. c:var:: const char * TARGET_ASM_UNALIGNED_PSI_OP
+.. c:var:: const char * TARGET_ASM_UNALIGNED_SI_OP
+.. c:var:: const char * TARGET_ASM_UNALIGNED_PDI_OP
+.. c:var:: const char * TARGET_ASM_UNALIGNED_DI_OP
+.. c:var:: const char * TARGET_ASM_UNALIGNED_PTI_OP
+.. c:var:: const char * TARGET_ASM_UNALIGNED_TI_OP
+
.. include:: ../tm.rst.in
:start-after: [TARGET_ASM_BYTE_OP]
:end-before: [TARGET_ASM_BYTE_OP]
@@ -150,4 +166,4 @@ of ``ASM_OUTPUT_DOUBLE`` and the like:
The array element values are designed so that you can print them out
using ``fprintf`` in the order they should appear in the target
- machine's memory.
\ No newline at end of file
+ machine's memory.
next reply other threads:[~2021-06-23 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 11:30 Martin Liska [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-24 14:06 Martin Liska
2021-06-23 11:51 Martin Liska
2021-06-23 11:30 Martin Liska
2021-06-23 11:28 Martin Liska
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=20210623113008.13BB13984C16@sourceware.org \
--to=marxin@gcc.gnu.org \
--cc=gcc-cvs@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).