public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110490] tree-ssa/clz-* and tree-ssa/ctz-* fail on s390x with arch14 Date: Thu, 29 Jun 2023 21:19:59 +0000 [thread overview] Message-ID: <bug-110490-4-IQVq9oNKD5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110490-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110490 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|testsuite |tree-optimization Ever confirmed|0 |1 Last reconfirmed| |2023-06-29 Keywords| |missed-optimization Status|UNCONFIRMED |NEW --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So the problem is a missing optimization. In this case, arch14 (which enables TARGET_EXTIMM) only defines a clzdi2 and not a clzsi2 so the code in build_cltz_expr does not realize that it could still support clzsi2 ...
next prev parent reply other threads:[~2023-06-29 21:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-29 20:25 [Bug testsuite/110490] New: " mpolacek at gcc dot gnu.org 2023-06-29 20:42 ` [Bug testsuite/110490] " pinskia at gcc dot gnu.org 2023-06-29 21:19 ` pinskia at gcc dot gnu.org [this message] 2023-06-29 21:48 ` [Bug tree-optimization/110490] " pinskia at gcc dot gnu.org 2024-04-26 15:29 ` [Bug tree-optimization/110490] tree-ssa/clz-* and tree-ssa/ctz-* fail on s390x with arch14 (expression_expensive_p not handling if there is wider clz/ctz/popcount optab) stefansf at gcc dot gnu.org 2024-05-07 12:13 ` cvs-commit at gcc dot gnu.org 2024-05-08 8:17 ` stefansf 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-110490-4-IQVq9oNKD5@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).