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/114269] [14 Regression] Multiple 3-27% exec time regressions of 434.zeusmp since r14-9193-ga0b1798042d033
Date: Fri, 08 Mar 2024 13:41:06 +0000	[thread overview]
Message-ID: <bug-114269-4-AZcrWMgovz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114269-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114269

--- Comment #5 from GCC 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:018ddc86b928514d7dfee024dcdeb204d5dcdd61

commit r14-9391-g018ddc86b928514d7dfee024dcdeb204d5dcdd61
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Mar 8 13:27:12 2024 +0100

    tree-optimization/114269 - 434.zeusmp regression after SCEV analysis fix

    The following addresses a performance regression caused by the recent
    SCEV analysis fix with regard to folding multiplications and undefined
    behavior on overflow.  We do not handle (T) { a, +, b } * c but can
    treat sign-conversions from unsigned by performing the multiplication
    in the unsigned type.  That's what we already do for additions (but
    that misses one case that turns out important).

    This fixes the 434.zeusmp regression for me.

            PR tree-optimization/114269
            PR tree-optimization/114074
            * tree-chrec.cc (chrec_fold_plus_1): Handle sign-conversions
            in the third CASE_CONVERT case as well.
            (chrec_fold_multiply): Handle sign-conversions from unsigned
            by performing the operation in the unsigned type.

  parent reply	other threads:[~2024-03-08 13:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 15:30 [Bug tree-optimization/114269] New: " pheeck at gcc dot gnu.org
2024-03-08  8:18 ` [Bug tree-optimization/114269] " rguenth at gcc dot gnu.org
2024-03-08 10:08 ` xry111 at gcc dot gnu.org
2024-03-08 10:25 ` rguenth at gcc dot gnu.org
2024-03-08 12:23 ` rguenth at gcc dot gnu.org
2024-03-08 13:41 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-08 13:41 ` rguenth at gcc dot gnu.org
2024-03-12 12:48 ` [Bug tree-optimization/114269] [14 Regression] Multiple 3-6% " pheeck at gcc dot gnu.org
2024-03-15 15:01 ` law at gcc dot gnu.org
2024-03-19 12:12 ` cvs-commit at gcc dot gnu.org
2024-03-19 12:15 ` rguenth 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-114269-4-AZcrWMgovz@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: link
Be 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).