public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kito at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106585] New: RISC-V: Mis-optimized code gen for zbs Date: Thu, 11 Aug 2022 15:36:00 +0000 [thread overview] Message-ID: <bug-106585-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106585 Bug ID: 106585 Summary: RISC-V: Mis-optimized code gen for zbs Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: kito at gcc dot gnu.org Target Milestone: --- Target: riscv Command: $ riscv64-unknown-elf-gcc foo.c -o - -S -O3 -march=rv64imafdc_zbb_zbs ```c int foo(int rs1, int rs2) { return (rs1 & ~(1<<rs2)); } ``` Current code gen: ```asm foo: li a5,1 sllw a5,a5,a1 andn a0,a0,a5 sext.w a0,a0 ret ``` And even worth if compile without zbb ```asm foo: li a5,1 sllw a5,a5,a1 andn a0,a0,a5 sext.w a0,a0 ret ``` clang code gen: ``` foo: bclr a0, a0, a1 sext.w a0, a0 ret ```
next reply other threads:[~2022-08-11 15:36 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-11 15:36 kito at gcc dot gnu.org [this message] 2022-08-11 15:45 ` [Bug target/106585] " pinskia at gcc dot gnu.org 2022-08-11 15:46 ` pinskia at gcc dot gnu.org 2022-08-11 15:52 ` pinskia at gcc dot gnu.org 2022-08-11 15:54 ` pinskia at gcc dot gnu.org 2022-08-11 16:10 ` kito at gcc dot gnu.org 2022-08-11 16:23 ` kito at gcc dot gnu.org 2022-08-11 16:27 ` pinskia at gcc dot gnu.org 2022-12-07 22:45 ` law at gcc dot gnu.org 2022-12-08 5:02 ` palmer at gcc dot gnu.org 2022-12-08 6:25 ` Andrew Waterman 2022-12-08 6:25 ` andrew at sifive dot com 2022-12-08 16:16 ` palmer at gcc dot gnu.org 2023-04-28 22:46 ` law 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-106585-4@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).