From: "Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>
To: Benedikt Huber <benedikt.huber@theobroma-systems.com>
Cc: "pinskia@gmail.com" <pinskia@gmail.com>,
"Dr. Philipp Tomsich" <philipp.tomsich@theobroma-systems.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] [aarch64] Implemented reciprocal square root (rsqrt) estimation in -ffast-math
Date: Mon, 29 Jun 2015 17:44:00 -0000 [thread overview]
Message-ID: <7794A52CE4D579448B959EED7DD0A4723DD10BC1@satlexdag06.amd.com> (raw)
In-Reply-To: <9A025B39-E723-4AEE-8AEF-12F156161C38@theobroma-systems.com>
Hi,
> -----Original Message-----
> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-
> owner@gcc.gnu.org] On Behalf Of Benedikt Huber
> Sent: Monday, June 29, 2015 11:04 PM
> To: Kumar, Venkataramanan
> Cc: pinskia@gmail.com; Dr. Philipp Tomsich; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] [aarch64] Implemented reciprocal square root (rsqrt)
> estimation in -ffast-math
>
> >
> > Benedikt , I have ICE for 444.namd with your patch, not sure if something
> wrong in my local tree.
>
> Venkat, now I could reproduce it.
> Strangely it does not happen with -flto.
> I will try to find out the reason for that.
>
Sure, I kind of remember that RTX for target in builtin rsqrt was 0. But not sure if we need to create reg rtx in such cases.
> Thank you for the catch,
> Benedikt
prev parent reply other threads:[~2015-06-29 17:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 11:57 Benedikt Huber
2015-06-18 12:03 ` [PATCH] 2015-06-15 Benedikt Huber <benedikt.huber@theobroma-systems.com> Benedikt Huber
2015-06-27 8:12 ` Andrew Pinski
2015-06-18 12:36 ` [PATCH] [aarch64] Implemented reciprocal square root (rsqrt) estimation in -ffast-math Kumar, Venkataramanan
2015-06-24 16:49 ` Evandro Menezes
2015-06-24 16:55 ` Dr. Philipp Tomsich
2015-06-24 17:16 ` Benedikt Huber
2015-06-24 18:37 ` Evandro Menezes
2015-06-24 20:11 ` Dr. Philipp Tomsich
2015-06-24 20:54 ` Evandro Menezes
2015-06-25 11:52 ` Benedikt Huber
2015-06-25 7:01 ` Kumar, Venkataramanan
2015-06-25 7:03 ` pinskia
2015-06-25 9:43 ` Ramana Radhakrishnan
2015-06-27 2:01 ` Andrew Pinski
2015-06-25 11:07 ` Benedikt Huber
2015-06-25 13:27 ` Michael Matz
2015-06-25 15:43 ` Kumar, Venkataramanan
2015-06-25 15:52 ` Dr. Philipp Tomsich
2015-06-25 16:47 ` Kumar, Venkataramanan
2015-06-28 15:13 ` pinskia
2015-06-29 8:30 ` Kumar, Venkataramanan
2015-06-29 9:07 ` Dr. Philipp Tomsich
2015-06-29 9:22 ` Kumar, Venkataramanan
2015-06-29 11:44 ` James Greenhalgh
2015-06-29 11:56 ` Dr. Philipp Tomsich
2015-06-29 16:57 ` pinskia
2015-06-29 19:07 ` Kumar, Venkataramanan
2015-07-14 22:26 ` Evandro Menezes
2015-07-20 9:46 ` Kumar, Venkataramanan
2015-07-20 15:58 ` Evandro Menezes
2015-07-13 19:09 ` Evandro Menezes
2015-07-14 22:20 ` Evandro Menezes
2015-06-29 14:20 ` Benedikt Huber
2015-06-29 17:35 ` Benedikt Huber
2015-06-29 17:44 ` Kumar, Venkataramanan [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=7794A52CE4D579448B959EED7DD0A4723DD10BC1@satlexdag06.amd.com \
--to=venkataramanan.kumar@amd.com \
--cc=benedikt.huber@theobroma-systems.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=pinskia@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).