From: Joseph Myers <joseph@codesourcery.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: <gcc@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>,
Martin Liska <mliska@suse.cz>, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: Google Summer of Code 2018: Call for mentors and ideas
Date: Wed, 17 Jan 2018 21:06:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1801172038520.3681@digraph.polyomino.org.uk> (raw)
In-Reply-To: <ri6efmoxtek.fsf@suse.cz>
On Wed, 17 Jan 2018, Martin Jambor wrote:
> 3?) Joseph Myers brought up idea to do "built-in functions for TS 18661
> floating-point functions - which has the feature that there are a
> lot of similar built-in functions for C99/C11 functions to serve as
> a guide for how to implement things)" ...Joseph, would you be
> willing to mentor it?
Yes, provided at least one other mentor is available as well as I may not
be around all the time during the GSoC period, including one of the
evaluation periods.
(The outline I put on the wiki page is:
GCC supports built-in functions for math.h and complex.h functions in
the C99/C11 standards (both folding calls for constant arguments, and
expanding inline when the processor supports appropriate functionality).
More such functions have been added in ISO/IEC TS 18661, supporting
features of IEEE 754-2008. It would be useful to have built-in functions
for those, both folding for constant arguments, and expanding inline
where appropriate (e.g. for roundeven and the functions rounding result
to narrower type, on some processors; roundeven can be inlined on x86
for SSE4.1 and later, and the narrowing functions on IA64 and POWER8,
for example). Existing built-in functions would provide a guide for how
to do this.
This project has the feature that there are lots of smaller subprojects
each of which would be a useful enhancement to GCC, so a student could
start off with e.g. roundeven built-in functions, closely following how
existing code handles round / floor / ceil / trunc, before going on to
more complicated functions such as the narrowing ones or the fromfp
functions - with scope for functions from TS 18661-3 and TS 18661-4 if
they run out of useful functions from TS 18661-1. If a student were
interested I could provide more detailed lists of possible subprojects.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-01-17 21:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:54 Martin Jambor
2018-01-17 21:06 ` Joseph Myers [this message]
2018-01-19 13:17 ` Martin Jambor
2018-01-19 16:34 ` Joseph Myers
2018-01-19 17:31 ` Richard Biener
2018-01-17 22:16 ` Joel Sherrill
2018-01-18 9:19 ` Martin Liška
2018-01-19 13:50 ` Martin Jambor
2018-01-18 9:41 ` Martin Liška
2018-01-19 14:09 ` Martin Jambor
2018-01-19 14:13 ` Martin Jambor
2018-01-22 15:10 ` Martin Liška
2018-01-22 15:40 ` Martin Liška
2018-01-18 19:51 ` Eric Gallager
2018-01-18 20:31 ` Joseph Myers
2018-01-19 14:17 ` Martin Jambor
2018-01-18 23:10 ` Andi Kleen
2018-01-19 14:24 ` Martin Jambor
2018-01-23 10:56 ` Martin Jambor
2018-01-23 11:08 ` Prathamesh Kulkarni
2018-01-23 15:49 ` Martin Liška
2018-01-23 23:11 ` Martin Jambor
2018-02-13 13:02 ` Martin Jambor
2018-02-14 22:10 ` Janus Weil
2018-02-15 9:20 ` Martin Jambor
2018-02-15 10:52 ` Christopher Dimech
2018-02-15 12:12 ` Janus Weil
2018-02-15 13:59 ` Martin Jambor
2018-03-29 15:37 ` Joseph Myers
2018-03-29 16:40 ` Joseph Myers
2018-03-29 17:07 ` Martin Jambor
2018-04-03 11:30 ` Peryt, Sebastian
2018-04-03 14:09 ` Martin Jambor
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.20.1801172038520.3681@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mjambor@suse.cz \
--cc=mliska@suse.cz \
/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).