From: Vladimir Makarov <vmakarov@redhat.com>
To: Igor Zamyatin <izamyatin@gmail.com>
Cc: "Zamyatin, Igor" <igor.zamyatin@intel.com>,
"enkovich.gnu@gmail.com" <enkovich.gnu@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: FW: patch to fix PR21617
Date: Wed, 25 Jan 2012 16:45:00 -0000 [thread overview]
Message-ID: <4F20317A.6060608@redhat.com> (raw)
In-Reply-To: <CAKdSQZkhMjGqz0TEPw3hGjzffHk9cRQR4fgLrvJwRMtz9h8D0w@mail.gmail.com>
On 01/23/2012 06:32 AM, Igor Zamyatin wrote:
> Unfortunately patch doesn't help neither for separate EEMBC_2_0 tests
> nor for the whole benchmark.
>
> Do you want me to do some debugging here?
>
For now I am out of ideas how to fix the PR in alternative way without
some performance degradation on SPEC or EEMBC.
Any reduced test case from EEMBC where I can see performance degradation
might help me too.
prev parent reply other threads:[~2012-01-25 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0EFAB2BDD0F67E4FB6CCC8B9F87D75690EC81F@IRSMSX101.ger.corp.intel.com>
2011-12-29 11:59 ` Igor Zamyatin
2012-01-10 17:44 ` Vladimir Makarov
[not found] ` <0EFAB2BDD0F67E4FB6CCC8B9F87D756910D3FD@IRSMSX101.ger.corp.intel.com>
2012-01-19 20:53 ` Vladimir Makarov
2012-01-20 18:15 ` Vladimir Makarov
2012-01-23 11:32 ` Igor Zamyatin
2012-01-25 16:45 ` Vladimir Makarov [this message]
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=4F20317A.6060608@redhat.com \
--to=vmakarov@redhat.com \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=igor.zamyatin@intel.com \
--cc=izamyatin@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).