public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97005] [nvptx] FAIL: c-c++-common/torture/builtin-arith-overflow-15.c -O0 execution test Date: Mon, 07 Feb 2022 08:48:23 +0000 [thread overview] Message-ID: <bug-97005-4-jENnTizLRD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97005-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97005 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- What about u16.u8, u32.u8 and u64.u8 zero extensions? If it is just hi -> {si,di} zext, then we could take HImode out of the (define_insn "zero_extend<mode>si2" [(set (match_operand:SI 0 "nvptx_register_operand" "=R,R") (zero_extend:SI (match_operand:QHIM 1 "nvptx_nonimmediate_operand" "R,m")))] "" "@ %.\\tcvt.u32.u%T1\\t%0, %1; %.\\tld%A1.u%T1\\t%0, %1;" [(set_attr "subregs_ok" "true")]) (define_insn "zero_extend<mode>di2" [(set (match_operand:DI 0 "nvptx_register_operand" "=R,R") (zero_extend:DI (match_operand:QHSIM 1 "nvptx_nonimmediate_operand" "R,m")))] "" "@ %.\\tcvt.u64.u%T1\\t%0, %1; %.\\tld%A1%u1\\t%0, %1;" [(set_attr "subregs_ok" "true")]) iterators and add patterns for the hisi and hidi that would do the and afterwards for the cvt case.
next prev parent reply other threads:[~2022-02-07 8:48 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-09 23:38 [Bug target/97005] New: " vries at gcc dot gnu.org 2022-02-06 8:04 ` [Bug target/97005] " vries at gcc dot gnu.org 2022-02-06 8:42 ` vries at gcc dot gnu.org 2022-02-06 10:41 ` jakub at gcc dot gnu.org 2022-02-07 8:43 ` vries at gcc dot gnu.org 2022-02-07 8:48 ` jakub at gcc dot gnu.org [this message] 2022-02-07 8:52 ` vries at gcc dot gnu.org 2022-02-07 8:57 ` vries at gcc dot gnu.org 2022-02-07 11:49 ` vries at gcc dot gnu.org 2022-02-10 8:52 ` cvs-commit at gcc dot gnu.org 2022-02-10 8:55 ` vries at gcc dot gnu.org 2022-02-24 20:07 ` vries at gcc dot gnu.org
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=bug-97005-4-jENnTizLRD@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).