From: Igor Zamyatin <izamyatin@gmail.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Atom: Scheduler improvements for better imul placement
Date: Thu, 12 Apr 2012 10:20:00 -0000 [thread overview]
Message-ID: <CAKdSQZkfoWY9tZbBtKerv8fY57fw-jp-pz56PK+tEiVkdUwWuA@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc1w-+brSp_qCm40V+iawbdjz5PT5=zC=D8LBVm38q8mxQ@mail.gmail.com>
On Wed, Apr 11, 2012 at 6:10 PM, Richard Guenther
<richard.guenther@gmail.com> wrote:
> On Wed, Apr 11, 2012 at 3:38 PM, Andi Kleen <andi@firstfloor.org> wrote:
>> Igor Zamyatin <izamyatin@gmail.com> writes:
>>
>>> Hi All!
>>>
>>> It is known that imul placement is rather critical for Atom processors
>>> and changes try to improve imul scheduling for Atom.
>>>
>>> This gives +5% performance on several tests from new OA 2.0 testsuite
>>> from EEMBC.
>>>
>>> Tested for i386 and x86-64, ok for trunk?
>>
>> Did you measure how much this slows down the compiler when compiling
>> for Atom? The new pass looks rather slow.
>
> Also please explain why adjusting the automaton for Atom is not a way to
> attack this issue.
If I understand the question correctly - it's a dynamic check and it's
not clear how to describe this adjusting statically in machine
description
>
> Richard.
>
>> -Andi
>>
>> --
>> ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2012-04-12 10:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 8:40 Igor Zamyatin
2012-04-11 13:38 ` Andi Kleen
2012-04-11 14:10 ` Richard Guenther
2012-04-12 10:20 ` Igor Zamyatin [this message]
2012-04-12 10:45 ` Richard Guenther
2012-04-12 12:00 ` Alexander Monakov
2012-04-12 12:24 ` Richard Guenther
2012-04-12 12:36 ` Igor Zamyatin
2012-04-12 12:38 ` Richard Guenther
2012-04-12 13:02 ` Andrey Belevantsev
2012-04-12 13:55 ` Richard Guenther
2012-04-12 14:03 ` Andrey Belevantsev
2012-04-12 14:22 ` Richard Guenther
2012-04-13 7:16 ` Andrey Belevantsev
2012-04-13 10:18 ` Igor Zamyatin
2012-04-13 11:00 ` Igor Zamyatin
2012-04-13 12:21 ` Andrey Belevantsev
2012-04-16 20:27 ` Igor Zamyatin
2012-04-20 12:05 ` Igor Zamyatin
2012-05-06 7:27 ` Igor Zamyatin
2012-05-28 20:20 ` Igor Zamyatin
2012-04-12 10:18 ` Igor Zamyatin
2012-05-28 21:41 Uros Bizjak
[not found] ` <0EFAB2BDD0F67E4FB6CCC8B9F87D756915E05C45@IRSMSX101.ger.corp.intel.com>
2012-05-29 19:01 ` Igor Zamyatin
2012-06-01 13:46 ` H.J. Lu
2012-06-01 17:48 ` Eric Botcazou
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=CAKdSQZkfoWY9tZbBtKerv8fY57fw-jp-pz56PK+tEiVkdUwWuA@mail.gmail.com \
--to=izamyatin@gmail.com \
--cc=andi@firstfloor.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).