public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pan2.li at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111720] RISC-V: Ugly codegen in RVV Date: Wed, 18 Oct 2023 03:29:10 +0000 [thread overview] Message-ID: <bug-111720-4-YWATNmGlTK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111720-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111720 --- Comment #14 from Li Pan <pan2.li at intel dot com> --- Looks like option -fmerge-all-constants doesn't work for this case, as well as RISC-V. For RISC-V, the CLOBBER exists after tree gimple. void test (vuint8m1_t *out) { uint8_t arr[32] = {1, 2, 7, 1, 3, 4, 5, 3, 1, 0, 1, 2, 4, 4, 9, 9, 1, 2, 7, 1, 3, 4, 5, 3, 1, 0, 1, 2, 4, 4, 9, 9}; *out = *(vuint8m1_t *)arr; } void test (vuint8m1_t * out) { uint8_t arr[32]; try { arr = "\x01\x02\x07\x01\x03\x04\x05\x03\x01\x00\x01\x02\x04\x04\t\t\x01\x02\x07\x01\x03\x04\x05\x03\x01\x00\x01\x02\x04\x04\t\t"; arr.0_1 = &arr; _2 = MEM[(vuint8m1_t *)arr.0_1]; *out = _2; } finally { arr = {CLOBBER(eol)}; } }
next prev parent reply other threads:[~2023-10-18 3:29 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-07 22:28 [Bug c/111720] New: " juzhe.zhong at rivai dot ai 2023-10-07 22:34 ` [Bug target/111720] " juzhe.zhong at rivai dot ai 2023-10-07 22:36 ` pinskia at gcc dot gnu.org 2023-10-07 22:38 ` juzhe.zhong at rivai dot ai 2023-10-07 22:41 ` juzhe.zhong at rivai dot ai 2023-10-07 22:43 ` juzhe.zhong at rivai dot ai 2023-10-07 22:44 ` pinskia at gcc dot gnu.org 2023-10-07 22:44 ` pinskia at gcc dot gnu.org 2023-10-07 22:47 ` juzhe.zhong at rivai dot ai 2023-10-07 22:49 ` juzhe.zhong at rivai dot ai 2023-10-07 22:51 ` pinskia at gcc dot gnu.org 2023-10-07 22:55 ` juzhe.zhong at rivai dot ai 2023-10-07 23:09 ` juzhe.zhong at rivai dot ai 2023-10-17 8:26 ` juzhe.zhong at rivai dot ai 2023-10-18 3:29 ` pan2.li at intel dot com [this message] 2023-10-19 2:07 ` juzhe.zhong at rivai dot ai 2023-10-19 6:37 ` rguenth at gcc dot gnu.org 2023-10-19 7:45 ` juzhe.zhong at rivai dot ai 2023-10-19 11:16 ` rguenth at gcc dot gnu.org 2023-10-19 11:30 ` juzhe.zhong at rivai dot ai 2023-10-19 11:34 ` rguenther at suse dot de 2023-10-19 11:58 ` juzhe.zhong at rivai dot ai 2023-10-19 12:02 ` rguenther at suse dot de 2023-10-19 12:08 ` juzhe.zhong at rivai dot ai 2023-10-19 12:20 ` rguenther at suse dot de 2023-10-19 12:38 ` juzhe.zhong at rivai dot ai 2023-10-19 13:30 ` rguenther at suse dot de 2023-11-01 7:33 ` pan2.li at intel dot com 2023-11-06 10:27 ` rguenth at gcc dot gnu.org 2023-11-06 10:44 ` juzhe.zhong at rivai dot ai 2023-11-23 1:20 ` cvs-commit at gcc dot gnu.org 2023-11-23 1:29 ` pan2.li at intel dot com
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-111720-4-YWATNmGlTK@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).