From: Eric Botcazou <ebotcazou@adacore.com>
To: Bernd Schmidt <bernds_cb1@t-online.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: regrename speedup
Date: Thu, 19 Nov 2009 19:28:00 -0000 [thread overview]
Message-ID: <200911191951.14160.ebotcazou@adacore.com> (raw)
In-Reply-To: <4AFC548E.8000506@t-online.de>
> The following patch cures the problem entirely. The initial scanning
> phase of the renamer is rewritten to keep track of conflicts between
> chains, as well as recording lifetimes of hard registers. This removes
> the need for merge_overlapping_regs to rescan the basic block every time.
What's the effect on the memory consumption, e.g. for the testcase of PR38582?
> I've bootstrapped and regression tested this patch on i686-linux with
> another small patch to force flag_rename_registers to 1.
>
> Ok (and for which stage)?
I think we should consider installing it now, given that the option is only
activated on demand or through -funroll-loops and -fpeel-loops.
I have a request though: can you split the patch into 2 parts, the first one
containing only the cleaning and refactoring work? That is to say, primarily
the hide_operands/restore_operands thing. But could you also add the removal
of the unused earlyclobber machinery? Your patch won't use it either and the
combined result is a little confusing. Thanks in advance.
--
Eric Botcazou
next prev parent reply other threads:[~2009-11-19 18:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 14:46 Bernd Schmidt
2009-10-22 13:09 ` Eric Botcazou
2009-11-12 18:31 ` Bernd Schmidt
2009-11-28 1:39 ` H.J. Lu
2009-11-28 8:55 ` Eric Botcazou
2009-11-30 11:55 ` Bernd Schmidt
2009-11-30 12:19 ` Eric Botcazou
2009-11-30 13:27 ` Bernd Schmidt
2009-12-02 13:13 ` Bernd Schmidt
2009-12-02 18:22 ` Eric Botcazou
2009-12-03 13:08 ` Bernd Schmidt
2009-11-12 18:32 ` Bernd Schmidt
2009-11-19 19:28 ` Eric Botcazou [this message]
2009-11-20 1:36 ` Bernd Schmidt
2009-11-20 7:58 ` Eric Botcazou
2009-11-20 21:31 ` Bernd Schmidt
2009-11-22 22:26 ` Eric Botcazou
2009-11-24 11:55 ` Bernd Schmidt
2009-11-24 12:30 ` Eric Botcazou
2009-11-26 12:27 ` Eric Botcazou
2009-11-26 16:50 ` Bernd Schmidt
2009-11-26 17:46 ` Eric Botcazou
2009-11-26 23:19 ` Bernd Schmidt
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=200911191951.14160.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=bernds_cb1@t-online.de \
--cc=gcc-patches@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).