From: "Gopalasubramanian, Ganesh" <Ganesh.Gopalasubramanian@amd.com>
To: Uros Bizjak <ubizjak@gmail.com>, Richard Biener <rguenther@suse.de>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] Fix bdverN vector cost of cond_[not_]taken_branch_cost
Date: Wed, 08 Apr 2015 06:39:00 -0000 [thread overview]
Message-ID: <EB4625145972F94C9680D8CADD65161578FD1FE8@SATLEXDAG02.amd.com> (raw)
In-Reply-To: <CAFULd4Y-a6B19vq2k1+CfqJEFfQuqWfKN2rKg_sAXO+zP5=1dw@mail.gmail.com>
> I have added a person from AMD to comment on the decision.
> Otherwise, the patch looks OK, but please wait a couple of days for possible comments.
Thank you Uros!
I am checking the changes with few tests and benchmarking them.
Please wait for a couple of days.
-Ganesh
next prev parent reply other threads:[~2015-04-08 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 8:19 Richard Biener
2015-04-07 11:20 ` Uros Bizjak
2015-04-08 6:39 ` Gopalasubramanian, Ganesh [this message]
2015-04-08 7:38 ` Richard Biener
2015-04-13 5:49 ` Gopalasubramanian, Ganesh
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=EB4625145972F94C9680D8CADD65161578FD1FE8@SATLEXDAG02.amd.com \
--to=ganesh.gopalasubramanian@amd.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=ubizjak@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).