public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99531] [11 Regression] Performance regression since gcc 9 (argument passing / register allocation)
Date: Mon, 20 May 2024 23:14:57 +0000 [thread overview]
Message-ID: <bug-99531-4-U7dZ7DaAD3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99531-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99531
Oleg Endo <olegendo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |olegendo at gcc dot gnu.org
--- Comment #11 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to GCC Commits from comment #5)
> The master branch has been updated by Vladimir Makarov
> <vmakarov@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:a7acb6dca941db2b1c135107dac3a34a20650d5c
>
> commit r12-5944-ga7acb6dca941db2b1c135107dac3a34a20650d5c
> Author: Vladimir N. Makarov <vmakarov@redhat.com>
> Date: Mon Dec 13 13:48:12 2021 -0500
>
> [PR99531] Modify pseudo class cost calculation when processing move
> involving the pseudo and a hard register
>
> Pseudo class calculated on the 1st iteration should not have a
> special treatment in cost calculation when processing move involving
> the pseudo and a hard register.
>
> gcc/ChangeLog:
>
> PR target/99531
> * ira-costs.c (record_operand_costs): Do not take pseudo class
> calculated on the 1st iteration into account when processing move
> involving the pseudo and a hard register.
>
> gcc/testsuite/ChangeLog:
>
> PR target/99531
> * gcc.target/i386/pr99531.c: New test.
This caused PR 115148
next prev parent reply other threads:[~2024-05-20 23:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 22:36 [Bug target/99531] New: " stefanrin at gmail dot com
2021-03-11 8:32 ` [Bug target/99531] " rguenth at gcc dot gnu.org
2021-03-11 8:32 ` [Bug target/99531] [9/10/11 Regression] " rguenth at gcc dot gnu.org
2021-03-11 9:35 ` marxin at gcc dot gnu.org
2021-04-08 13:05 ` rguenth at gcc dot gnu.org
2021-06-01 8:19 ` [Bug target/99531] [9/10/11/12 " rguenth at gcc dot gnu.org
2021-12-07 13:48 ` vmakarov at gcc dot gnu.org
2021-12-13 19:11 ` cvs-commit at gcc dot gnu.org
2021-12-14 15:04 ` cvs-commit at gcc dot gnu.org
2022-05-27 9:44 ` [Bug target/99531] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-01-12 23:36 ` [Bug target/99531] [10/11 " roger at nextmovesoftware dot com
2023-07-07 10:39 ` [Bug target/99531] [11 " rguenth at gcc dot gnu.org
2024-05-20 23:14 ` olegendo at gcc dot gnu.org [this message]
2024-05-22 0:05 ` olegendo 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-99531-4-U7dZ7DaAD3@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).