From: Joseph Myers <joseph@codesourcery.com>
To: Tejas Joshi <tejasjoshi9673@gmail.com>
Cc: <gcc@gcc.gnu.org>, Martin Jambor <mjambor@suse.cz>, <hubicka@ucw.cz>
Subject: Re: [GSoC-19] Implementing narrowing functions like fadd
Date: Wed, 24 Jul 2019 16:23:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1907241618510.21103@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CACMrGjDh7tAz=UMqjcEUmNHmbwWN+F_4PTFR5hNjzV8K6jGAgA@mail.gmail.com>
On Tue, 23 Jul 2019, Tejas Joshi wrote:
> Also, CASE_MATHFN and CASE_MATHFN_FLOATN cases in builtins.c expand
> normal, F and L variants which are assigned to respective fcode
> built_in_function. This makes any function defined in builtins.def to
> have F and L variants mandatory. How these narrowing functions are
> supposed to be handled? Do we define another macro expansion like
> CASE_MATHFN or have a manual case handling in mathfn_built_in_2?
> Attached patch is what I have tried so far.
You'll need something different from CASE_MATHFN - these are a different
kind of functions that need handling in a different way, because they are
parametrized over certain *pairs* of types, rather than over a single
type.
(The main case for these being built-in is probably not folding for
constant arguments - it's generating appropriate instructions when
building with -fno-math-errno for processors that have appropriate
narrowing instructions, such as Power ISA 2.07 or later, which I think
means POWER8 or later.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-07-24 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 12:53 Tejas Joshi
2019-07-06 12:53 ` Tejas Joshi
2019-07-10 11:28 ` Tejas Joshi
2019-07-10 12:33 ` Richard Sandiford
2019-07-23 17:05 ` Tejas Joshi
2019-07-24 16:23 ` Joseph Myers [this message]
[not found] ` <ri68ssk1znm.fsf@suse.cz>
2019-07-27 6:16 ` Tejas Joshi
2019-07-29 17:17 ` Martin Jambor
2019-07-31 6:30 ` Tejas Joshi
2019-08-02 10:34 ` Tejas Joshi
2019-08-06 15:40 ` Tejas Joshi
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=alpine.DEB.2.21.1907241618510.21103@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mjambor@suse.cz \
--cc=tejasjoshi9673@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).