From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: Wang Xuerui <i@xen0n.name>, Chenghua Xu <xuchenghua@loongson.cn>,
Xiaolin Tang <tangxiaolin@loongson.cn>
Subject: Re: [PATCH v2 2/4] LoongArch: Add ftint{,rm,rp}.{w,l}.{s,d} instructions
Date: Thu, 10 Nov 2022 14:41:55 +0800 [thread overview]
Message-ID: <5c9131fe-4bcb-1713-6716-a3e9930d8580@loongson.cn> (raw)
In-Reply-To: <20221109135329.952128-3-xry111@xry111.site>
在 2022/11/9 下午9:53, Xi Ruoyao 写道:
> +;; Convert floating-point numbers to integers
> +(define_insn "<lrint_pattern><ANYF:mode><ANYFI:mode>2"
> + [(set (match_operand:ANYFI 0 "register_operand" "=f")
> + (unspec:ANYFI [(match_operand:ANYF 1 "register_operand" "f")]
> + LRINT))]
> + "TARGET_HARD_FLOAT &&
> + (<lrint_allow_inexact>
> + || flag_fp_int_builtin_inexact
> + || !flag_trapping_math)"
>
+ || !flag_trapping_math
I think this condition is backwards.
next prev parent reply other threads:[~2022-11-10 6:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 13:53 [PATCH v2 0/4] LoongArch: Add some floating-point operations Xi Ruoyao
2022-11-09 13:53 ` [PATCH v2 1/4] LoongArch: Rename frint_<fmt> to rint<mode>2 Xi Ruoyao
2022-11-10 8:15 ` Lulu Cheng
2022-11-09 13:53 ` [PATCH v2 2/4] LoongArch: Add ftint{,rm,rp}.{w,l}.{s,d} instructions Xi Ruoyao
2022-11-10 6:41 ` Lulu Cheng [this message]
2022-11-10 8:49 ` Xi Ruoyao
2022-11-11 0:07 ` Joseph Myers
2022-11-11 5:29 ` Xi Ruoyao
2022-11-12 1:58 ` Lulu Cheng
2022-11-09 13:53 ` [PATCH v2 3/4] LoongArch: Add fscaleb.{s,d} instructions as ldexp{sf,df}3 Xi Ruoyao
2022-11-12 3:54 ` Lulu Cheng
2022-11-12 4:40 ` Xi Ruoyao
2022-11-12 6:52 ` Lulu Cheng
2022-11-09 13:53 ` [PATCH v2 4/4] LoongArch: Add flogb.{s,d} instructions and expand logb{sf,df}2 Xi Ruoyao
2022-11-12 6:51 ` Lulu Cheng
2022-11-12 7:08 ` [PATCH v2 0/4] LoongArch: Add some floating-point operations Xi Ruoyao
2022-11-12 7:14 ` Lulu Cheng
2022-11-14 2:41 ` tangxiaolin
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=5c9131fe-4bcb-1713-6716-a3e9930d8580@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=tangxiaolin@loongson.cn \
--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).