From: Tom de Vries <Tom_deVries@mentor.com>
To: Tom de Vries <vries@codesourcery.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
Tom de Vries <tom@codesourcery.com>,
Paolo Bonzini <bonzini@gnu.org>, <gcc-patches@gcc.gnu.org>,
Bernd Schmidt <bernds@codesourcery.com>
Subject: Re: new sign/zero extension elimination pass
Date: Mon, 20 Aug 2012 13:40:00 -0000 [thread overview]
Message-ID: <50323E4B.7060303@mentor.com> (raw)
In-Reply-To: <4FFD55B4.6060500@codesourcery.com>
On 11/07/12 12:30, Tom de Vries wrote:
> On 13/11/10 10:50, Eric Botcazou wrote:
>>> I profiled the pass on spec2000:
>>>
>>> -mabi=32 -mabi=64
>>> ee-pass (usr time): 0.70 1.16
>>> total (usr time): 919.30 879.26
>>> ee-pass (%): 0.08 0.13
>>>
>>> The pass takes 0.13% or less of the total usr runtime.
>>
>> For how many hits? What are the numbers with --param ee-max-propagate=0?
>>
>>> Is it necessary to improve the runtime of this pass?
>>
>> I've already given my opinion about the implementation. The other passes in
>> the compiler try hard not to rescan everything when a single bit changes; as
>> currently written, yours doesn't.
>>
>
> Eric,
>
> I've done the following:
> - refactored the pass such that it now scans at most twice over all
> instructions.
> - updated the patch to be applicable to current trunk
> - updated the motivating example to a more applicable one (as discussed in
> this thread), and added that one as test-case.
> - added a part in the header comment illustrating the working of the pass
> on the motivating example.
>
> bootstrapped and reg-tested on x86_64 and i686.
>
> build and reg-tested on mips, mips64, and arm.
>
> OK for trunk?
>
Eric,
does the new patch meet your concerns related to rescanning?
If so, OK for trunk?
Thanks,
- Tom
> Thanks,
> - Tom
>
> 2012-07-10 Tom de Vries <tom@codesourcery.com>
>
> * ee.c: New file.
> * tree-pass.h (pass_ee): Declare.
> * opts.c ( default_options_table): Set flag_ee at -O2.
> * timevar.def (TV_EE): New timevar.
> * common.opt (fextension-elimination): New option.
> * Makefile.in (ee.o): New rule.
> * passes.c (pass_ee): Add it.
>
> * gcc.dg/extend-1.c: New test.
> * gcc.dg/extend-2.c: Same.
> * gcc.dg/extend-2-64.c: Same.
> * gcc.dg/extend-3.c: Same.
> * gcc.dg/extend-4.c: Same.
> * gcc.dg/extend-5.c: Same.
> * gcc.target/mips/octeon-bbit-2.c: Make test more robust.
>
next prev parent reply other threads:[~2012-08-20 13:40 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 15:54 Tom de Vries
2010-10-18 16:03 ` Andrew Pinski
2010-10-18 16:59 ` Richard Guenther
2010-10-21 10:06 ` Tom de Vries
2010-10-21 10:44 ` Paolo Bonzini
2010-10-21 11:00 ` Paolo Bonzini
2010-10-21 17:21 ` Paolo Bonzini
2010-10-22 9:05 ` Tom de Vries
2010-10-22 9:24 ` Paolo Bonzini
2010-10-22 9:15 ` Eric Botcazou
2010-10-28 20:45 ` Tom de Vries
2010-10-29 2:11 ` Paolo Bonzini
2010-10-29 2:42 ` Paolo Bonzini
2010-10-31 19:30 ` Tom de Vries
2010-10-31 20:58 ` Joseph S. Myers
2010-10-31 21:11 ` Paolo Bonzini
2010-11-03 18:49 ` Eric Botcazou
2010-10-29 1:04 ` Paolo Bonzini
2010-10-29 1:33 ` Paolo Bonzini
2010-11-03 18:50 ` Eric Botcazou
2010-11-08 21:29 ` Tom de Vries
2010-11-08 22:11 ` Paolo Bonzini
2010-11-12 8:29 ` Tom de Vries
2010-11-13 10:41 ` Eric Botcazou
2012-07-11 10:31 ` Tom de Vries
2012-07-11 11:42 ` Jakub Jelinek
2012-07-11 13:01 ` Tom de Vries
2012-07-12 1:52 ` Kenneth Zadeck
[not found] ` <4FFE2ADF.2060806@naturalbridge.com>
[not found] ` <4FFE9346.2070806@mentor.com>
2012-07-12 9:21 ` Tom de Vries
2012-07-12 12:05 ` Kenneth Zadeck
2012-07-13 7:54 ` Tom de Vries
2012-07-13 11:39 ` Kenneth Zadeck
2012-07-13 12:58 ` Tom de Vries
2012-07-17 15:17 ` Kenneth Zadeck
2012-07-20 18:41 ` Tom de Vries
2012-08-20 13:40 ` Tom de Vries [this message]
2010-10-28 20:55 ` Andrew Pinski
2010-10-28 21:00 ` Andrew Pinski
2010-10-28 21:12 ` Tom de Vries
2010-10-28 22:58 ` Andrew Pinski
2010-10-29 15:06 ` Tom de Vries
2010-10-29 0:34 ` Paolo Bonzini
2010-11-08 21:32 ` Andrew Pinski
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=50323E4B.7060303@mentor.com \
--to=tom_devries@mentor.com \
--cc=bernds@codesourcery.com \
--cc=bonzini@gnu.org \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tom@codesourcery.com \
--cc=vries@codesourcery.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).