From: Robin Dapp <rdapp@linux.ibm.com>
To: gcc-patches@gcc.gnu.org, vmakarov@redhat.com, richard.sandiford@arm.com
Subject: Re: [PATCH 5/6] ira: Consider modelling caller-save allocations as loop spills
Date: Tue, 11 Jan 2022 13:47:46 +0100 [thread overview]
Message-ID: <e8bf01d2-2445-ab4b-fb4e-3cb695995447@linux.ibm.com> (raw)
In-Reply-To: <mptiluqvelj.fsf@arm.com>
> Could you try the attached?
The series with the patch is OK from a testsuite point of view. The
other problem appears later.
Regards
Robin
next prev parent reply other threads:[~2022-01-11 12:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 14:45 [PATCH 0/6] ira: Fix performance regression in exchange2 [PR98782] Richard Sandiford
2022-01-06 14:46 ` [PATCH 1/6] ira: Add a ira_loop_border_costs class Richard Sandiford
2022-01-06 15:08 ` Jan Hubicka
2022-01-07 11:12 ` Richard Sandiford
2022-01-07 14:38 ` Vladimir Makarov
2022-01-06 14:46 ` [PATCH 2/6] ira: Add comments and fix move_spill_restore calculation Richard Sandiford
2022-01-07 14:39 ` Vladimir Makarov
2022-01-06 14:47 ` [PATCH 3/6] ira: Add ira_subloop_allocnos_can_differ_p Richard Sandiford
2022-01-07 14:40 ` Vladimir Makarov
2022-01-06 14:47 ` [PATCH 4/6] ira: Try to avoid propagating conflicts Richard Sandiford
2022-01-10 13:51 ` Vladimir Makarov
2022-01-10 14:49 ` Richard Sandiford
2022-01-06 14:48 ` [PATCH 5/6] ira: Consider modelling caller-save allocations as loop spills Richard Sandiford
2022-01-10 13:51 ` Vladimir Makarov
2022-01-11 4:21 ` Hans-Peter Nilsson
2022-01-11 8:38 ` Robin Dapp
2022-01-11 8:52 ` Richard Sandiford
2022-01-11 11:31 ` Robin Dapp
2022-01-11 12:43 ` Martin Liška
2022-01-11 12:47 ` Robin Dapp [this message]
2022-01-11 12:49 ` Richard Sandiford
2022-01-06 14:48 ` [PATCH 6/6] ira: Handle "soft" conflicts between cap and non-cap allocnos Richard Sandiford
2022-01-10 13:52 ` Vladimir Makarov
2022-01-07 14:38 ` [PATCH 0/6] ira: Fix performance regression in exchange2 [PR98782] Vladimir Makarov
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=e8bf01d2-2445-ab4b-fb4e-3cb695995447@linux.ibm.com \
--to=rdapp@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
--cc=vmakarov@redhat.com \
/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).