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/88702] [8/9/10/11 regression] We do terrible job optimizing IsHTMLWhitespace from Firefox Date: Wed, 02 Dec 2020 07:21:26 +0000 [thread overview] Message-ID: <bug-88702-4-0yeDaCLdtP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88702-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88702 --- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:c961e94901eb793b1a18d431a1acf7f682eaf04f commit r11-5642-gc961e94901eb793b1a18d431a1acf7f682eaf04f Author: Martin Liska <mliska@suse.cz> Date: Tue Dec 1 12:18:46 2020 +0100 if-to-switch: Support chain with 2 BBs. As seen in the test-case, even 2 BBs can handle interesting cases covered by a jump table or a bit-test. gcc/ChangeLog: PR tree-optimization/88702 * gimple-if-to-switch.cc (pass_if_to_switch::execute): Require at least 2 BBs. * gimple-if-to-switch.cc (find_conditions): Require equal precision for low and high of a range. gcc/testsuite/ChangeLog: PR tree-optimization/88702 * gcc.dg/tree-ssa/if-to-switch-9.c: New test.
next prev parent reply other threads:[~2020-12-02 7:21 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88702-4@http.gcc.gnu.org/bugzilla/> 2020-12-01 10:47 ` [Bug ipa/88702] " cvs-commit at gcc dot gnu.org 2020-12-01 11:14 ` marxin at gcc dot gnu.org 2020-12-02 7:21 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-02 7:38 ` [Bug tree-optimization/88702] " marxin 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-88702-4-0yeDaCLdtP@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).