From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Patrick McGehearty <patrick.mcgehearty@oracle.com>,
libc-alpha@sourceware.org
Cc: nd@arm.com
Subject: Re: [PATCH] improves exp() and expf() performance on Sparc.
Date: Mon, 04 Sep 2017 11:43:00 -0000 [thread overview]
Message-ID: <59AD3C67.3070203@arm.com> (raw)
In-Reply-To: <1504306749-46787-1-git-send-email-patrick.mcgehearty@oracle.com>
On 01/09/17 23:59, Patrick McGehearty wrote:
> --- /dev/null
> +++ b/sysdeps/sparc/fpu/libm_endian.h
is this header useful?
> +#define XBIASED_EXP(x) ((((int *)&x)[HIXWORD] & 0x7fffffff) >> 16)
> +#define ISZEROL(x) (((((int *)&x)[0] & ~XSGNMSK) | ((int *)&x)[1] | \
> + ((int *)&x)[2] | ((int *)&x)[3]) == 0)
i don't see these used and such aliasing violation
is not acceptable anyway.
next prev parent reply other threads:[~2017-09-04 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 22:59 Patrick McGehearty
2017-09-01 23:14 ` Joseph Myers
2017-09-06 20:34 ` Patrick McGehearty
2017-09-06 21:01 ` Joseph Myers
2017-09-07 20:42 ` Patrick McGehearty
2017-09-07 21:05 ` Joseph Myers
2017-09-07 23:53 ` Patrick McGehearty
2017-09-04 11:43 ` Szabolcs Nagy [this message]
2017-09-06 20:31 ` Patrick McGehearty
2017-09-11 18:50 Wilco Dijkstra
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=59AD3C67.3070203@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=patrick.mcgehearty@oracle.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).