From: chenglulu <chenglulu@loongson.cn>
To: chenxiaolong <chenxiaolong@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: xry111@xry111.site, i@xen0n.name, xuchenghua@loongson.cn, c@jia.je
Subject: Re: [pushed][PATCH v1] LoongArch: Fix builtin function prototypes for LASX in doc.
Date: Thu, 21 Dec 2023 17:46:40 +0800 [thread overview]
Message-ID: <ce5479bc-6c49-ce78-af6b-0c5a910ccb5a@loongson.cn> (raw)
In-Reply-To: <20231219084317.58579-1-chenxiaolong@loongson.cn>
Pushed to r14-6776.
在 2023/12/19 下午4:43, chenxiaolong 写道:
> gcc/ChangeLog:
>
> * doc/extend.texi:According to the documents submitted earlier,
> Two problems with function return types and using the actual types
> of parameters instead of variable names were found and fixed.
> ---
> gcc/doc/extend.texi | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
> index 61c560a1cd3..cce6862b82b 100644
> --- a/gcc/doc/extend.texi
> +++ b/gcc/doc/extend.texi
> @@ -18660,14 +18660,14 @@ __m256 __lasx_xvfnmsub_s (__m256, __m256, __m256);
> __m256d __lasx_xvfrecip_d (__m256d);
> __m256 __lasx_xvfrecip_s (__m256);
> __m256d __lasx_xvfrint_d (__m256d);
> -__m256i __lasx_xvfrintrm_d (__m256d);
> -__m256i __lasx_xvfrintrm_s (__m256);
> -__m256i __lasx_xvfrintrne_d (__m256d);
> -__m256i __lasx_xvfrintrne_s (__m256);
> -__m256i __lasx_xvfrintrp_d (__m256d);
> -__m256i __lasx_xvfrintrp_s (__m256);
> -__m256i __lasx_xvfrintrz_d (__m256d);
> -__m256i __lasx_xvfrintrz_s (__m256);
> +__m256d __lasx_xvfrintrm_d (__m256d);
> +__m256 __lasx_xvfrintrm_s (__m256);
> +__m256d __lasx_xvfrintrne_d (__m256d);
> +__m256 __lasx_xvfrintrne_s (__m256);
> +__m256d __lasx_xvfrintrp_d (__m256d);
> +__m256 __lasx_xvfrintrp_s (__m256);
> +__m256d __lasx_xvfrintrz_d (__m256d);
> +__m256 __lasx_xvfrintrz_s (__m256);
> __m256 __lasx_xvfrint_s (__m256);
> __m256d __lasx_xvfrsqrt_d (__m256d);
> __m256 __lasx_xvfrsqrt_s (__m256);
> @@ -19134,10 +19134,10 @@ __m256i __lasx_xvssub_hu (__m256i, __m256i);
> __m256i __lasx_xvssub_w (__m256i, __m256i);
> __m256i __lasx_xvssub_wu (__m256i, __m256i);
> void __lasx_xvst (__m256i, void *, imm_n2048_2047);
> -void __lasx_xvstelm_b (__m256i, void *, imm_n128_127, idx);
> -void __lasx_xvstelm_d (__m256i, void *, imm_n128_127, idx);
> -void __lasx_xvstelm_h (__m256i, void *, imm_n128_127, idx);
> -void __lasx_xvstelm_w (__m256i, void *, imm_n128_127, idx);
> +void __lasx_xvstelm_b (__m256i, void *, imm_n128_127, imm0_31);
> +void __lasx_xvstelm_d (__m256i, void *, imm_n128_127, imm0_3);
> +void __lasx_xvstelm_h (__m256i, void *, imm_n128_127, imm0_15);
> +void __lasx_xvstelm_w (__m256i, void *, imm_n128_127, imm0_7);
> void __lasx_xvstx (__m256i, void *, long int);
> __m256i __lasx_xvsub_b (__m256i, __m256i);
> __m256i __lasx_xvsub_d (__m256i, __m256i);
prev parent reply other threads:[~2023-12-21 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 8:43 [PATCH " chenxiaolong
2023-12-21 9:46 ` chenglulu [this message]
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=ce5479bc-6c49-ce78-af6b-0c5a910ccb5a@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=c@jia.je \
--cc=chenxiaolong@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=xry111@xry111.site \
--cc=xuchenghua@loongson.cn \
/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).