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/genhooks-sphinx-v2)] Remove @deftypevrx. Date: Mon, 7 Jun 2021 13:44:28 +0000 (GMT) [thread overview] Message-ID: <20210607134428.C242A3886C4E@sourceware.org> (raw) https://gcc.gnu.org/g:540ad87049b19c07290516cd9360c2efb3cba06b commit 540ad87049b19c07290516cd9360c2efb3cba06b Author: Martin Liska <mliska@suse.cz> Date: Mon Jun 7 15:44:00 2021 +0200 Remove @deftypevrx. Diff: --- gcc/target.def | 16 +--------------- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/gcc/target.def b/gcc/target.def index ebe5803109b..edf36b1a652 100644 --- a/gcc/target.def +++ b/gcc/target.def @@ -44,21 +44,7 @@ DEFHOOKPODX (close_paren, const char *, ")") /* Assembler instructions for creating various kinds of integer object. */ DEFHOOKPOD (byte_op, - "@deftypevrx {Target Hook} {const char *} TARGET_ASM_ALIGNED_HI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_ALIGNED_PSI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_ALIGNED_SI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_ALIGNED_PDI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_ALIGNED_DI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_ALIGNED_PTI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_ALIGNED_TI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_UNALIGNED_HI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_UNALIGNED_PSI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_UNALIGNED_SI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_UNALIGNED_PDI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_UNALIGNED_DI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_UNALIGNED_PTI_OP\n\ -@deftypevrx {Target Hook} {const char *} TARGET_ASM_UNALIGNED_TI_OP\n\ -These hooks specify assembly directives for creating certain kinds\n\ + "These hooks specify assembly directives for creating certain kinds\n\ of integer object. The @code{TARGET_ASM_BYTE_OP} directive creates a\n\ byte-sized object, the @code{TARGET_ASM_ALIGNED_HI_OP} one creates an\n\ aligned two-byte object, and so on. Any of the hooks may be\n\
next reply other threads:[~2021-06-07 13:44 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-07 13:44 Martin Liska [this message] -- strict thread matches above, loose matches on Subject: below -- 2021-06-07 13:41 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=20210607134428.C242A3886C4E@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: linkBe 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).