public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107130] [13 Regression] wrong code with -Os -fno-tree-ccp -fno-tree-forwprop -fno-tree-fre since r13-2900-g001c60ccfeaf9a48 Date: Tue, 04 Oct 2022 04:28:44 +0000 [thread overview] Message-ID: <bug-107130-4-4B3wFOYfbU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107130-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107130 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>: https://gcc.gnu.org/g:f50d103183c551c7f9f9f20efaf2ebbf83d5e99f commit r13-3052-gf50d103183c551c7f9f9f20efaf2ebbf83d5e99f Author: Aldy Hernandez <aldyh@redhat.com> Date: Mon Oct 3 17:31:32 2022 +0200 [PR107130] range-ops: Separate out ffs and popcount optimizations. __builtin_popcount and __builtin_ffs were sharing the same range-ops entry, but the nonzero mask optimization is not valid for ffs. Separate them out into two entries. PR tree-optimization/107130 gcc/ChangeLog: * gimple-range-op.cc (class cfn_popcount): Call op_cfn_ffs. (class cfn_ffs): New. (gimple_range_op_handler::maybe_builtin_call): Separate out CASE_CFN_FFS into its own case. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/pr107130.c: New test.
next prev parent reply other threads:[~2022-10-04 4:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-03 11:26 [Bug tree-optimization/107130] New: [13 Regression] wrong code with -Os -fno-tree-ccp -fno-tree-forwprop -fno-tree-fre zsojka at seznam dot cz 2022-10-03 11:41 ` [Bug tree-optimization/107130] [13 Regression] wrong code with -Os -fno-tree-ccp -fno-tree-forwprop -fno-tree-fre since r13-2900-g001c60ccfeaf9a48 marxin at gcc dot gnu.org 2022-10-03 11:46 ` zsojka at seznam dot cz 2022-10-03 12:02 ` marxin at gcc dot gnu.org 2022-10-03 12:04 ` marxin at gcc dot gnu.org 2022-10-03 15:39 ` aldyh at gcc dot gnu.org 2022-10-03 15:40 ` aldyh at gcc dot gnu.org 2022-10-04 4:28 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-04 4:52 ` aldyh 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-107130-4-4B3wFOYfbU@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).