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/107946] [13 Regression] 507.cactuBSSN_r regresses by ~9% on znver3 with PGO since r13-3875-g9e11ceef165bc0 Date: Fri, 02 Dec 2022 07:04:28 +0000 [thread overview] Message-ID: <bug-107946-4-ZIugW30iSG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107946-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107946 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:5b50850c3c6f2eceb8012dcc8d3cd5ddd94fac6c commit r13-4458-g5b50850c3c6f2eceb8012dcc8d3cd5ddd94fac6c Author: Richard Biener <rguenther@suse.de> Date: Thu Dec 1 16:14:14 2022 +0100 Add --param max-unswitch-depth The following adds a --param to limit the depth of unswitched loop nests. One can use --param max-unswitch-depth=1 to disable unswitching of outer loops (the innermost loop will then be unswitched). PR tree-optimization/107946 * params.opt (-param=max-unswitch-depth=): New. * doc/invoke.texi (--param=max-unswitch-depth): Document. * tree-ssa-loop-unswitch.cc (init_loop_unswitch_info): Honor --param=max-unswitch-depth
next prev parent reply other threads:[~2022-12-02 7:04 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-01 13:40 [Bug tree-optimization/107946] New: " marxin at gcc dot gnu.org 2022-12-01 15:19 ` [Bug tree-optimization/107946] " rguenth at gcc dot gnu.org 2022-12-01 15:45 ` rguenth at gcc dot gnu.org 2022-12-02 7:04 ` cvs-commit at gcc dot gnu.org [this message] 2022-12-02 14:40 ` rguenth at gcc dot gnu.org 2023-04-26 6:57 ` [Bug tree-optimization/107946] [13/14 " rguenth at gcc dot gnu.org 2023-07-27 9:24 ` rguenth at gcc dot gnu.org 2024-01-26 18:06 ` jamborm at gcc dot gnu.org 2024-03-08 15:40 ` law at gcc dot gnu.org 2024-05-21 9:13 ` [Bug tree-optimization/107946] [13/14/15 " jakub 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-107946-4-ZIugW30iSG@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).