From: Tejas Joshi <tejasjoshi9673@gmail.com>
To: gcc@gcc.gnu.org
Cc: Martin Jambor <mjambor@suse.cz>, hubicka@ucw.cz, joseph@codesourcery.com
Subject: Re: Expanding roundeven (Was: Re: About GSOC.)
Date: Mon, 17 Jun 2019 07:50:00 -0000 [thread overview]
Message-ID: <CACMrGjAtTNDZ8GPbgMXp2iVjO5UBMORwbSQZcHwvkF1zA4z4pA@mail.gmail.com> (raw)
In-Reply-To: <ri6woho2huu.fsf@suse.cz>
Hello.
Looking at machine description of functions like ceil/floor and I
think specifically:
(define_expand "<rounding_insn><mode>2"
Roundeven should be described as define_expand (or within this
alongside ceil and floor?) with expand functions to emit instructions
in i386-builtins.c?
Referring to <www.info.univ-angers.fr/pub/richer/ens/l3info/ao/intel_sse4.pdf>,
operands of these instructions work with xmm registers, memory and
imm8 for rounding mode.
> existing ROUND_NO_EXC definition in GCC. A new definition will need
> adding alongside ROUND_FLOOR, ROUND_CEIL and ROUND_TRUNC to correspond to
> rounding to nearest with ties to even, evaluating to 0.)
So (ROUND_ROUNDEVEN 0x0) be declared for rounding towards nearest
even for rounding mode argument? But reference says that RC field
should end up as 00B for rounding ties to even? I am also much
confused about machine-type flags used as C conditions. How do we
determine which ones to check and does it depends on exceptions and
conditions described in the reference? Also, do ROUNDEVEN needs to be
defined as (how):
(define_int_attr rounding_insn
[(UNSPEC_FRNDINT_FLOOR "floor")
Thanks,
--Tejas
On Fri, 14 Jun 2019 at 23:02, Martin Jambor <mjambor@suse.cz> wrote:
>
> Hi,
>
> On Fri, Jun 14 2019, Tejas Joshi wrote:
> >> Of course the instruction is not present there, that is the next step in
> >> your project :-)
> >
> > Yes, of course, but what I meant was that instructions for existing
> > round/ceil functions and not roundeven. If inlining for these
> > functions is available, how can I inspect such instructions getting
> > inlined maybe in a *.s file?
>
> Make sure you compile to a target that has the rounding instruction,
> i.e. by using an appropriate -march or -mavx) and also specify
> -ffast-math on the command line. I have not double checked, but I
> assume the latter is necessary (mainly) because it implies
> -fno-math-errno and most of the math builtin expansion into instructions
> is guarded by check for !flag_errno_math.
>
> So e.g. my test input:
>
> double
> callplusone (double d)
> {
> return __builtin_round (d) + 1;
> }
>
> has vroundsd instruction in the output of:
>
> ~/gcc/trunk/inst/bin/gcc -O2 -S expand_example.c -mavx -ffast-math
>
> >
> > Also, I am trying to find appropriate places to introduce changes for
> > roundeven to be inlined. Attached patch is what I have tried so far to
> > find the places.
>
> So far I only quickly glanced over it but it seems to be going in the
> right direction. I'll try to answer the rest of your questions as soon
> as I can but I also have to look a bit into the machine descriptions
> myself first.
>
> Martin
>
>
> > ix86_expand_roundeven have dummy code for the sake of time.
> >
> > In i386.md:
> > 1. How should roundeven be defined at certain places where existing
> > floor is defined as:
> > (define_int_attr rounding_insn
> > [(UNSPEC_FRNDINT_FLOOR "floor")
> >
> > 2. Also, can roundeven be handled like round_floor is handled by:
> > (define_expand "<rounding_insn><mode>2"
> > but definitely with certain changes of flags, options and macros.
> >
> > Thanks,
> > --Tejas
next prev parent reply other threads:[~2019-06-17 7:50 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACMrGjCeaZ7EoYqjLYiAJXjOtOfpJNo9zcbWhfarfkiLMN8YYA@mail.gmail.com>
2018-10-13 4:43 ` About GSOC Tejas Joshi
2018-10-23 10:47 ` Martin Jambor
2018-10-23 16:51 ` Joseph Myers
2018-11-16 16:50 ` Tejas Joshi
2018-11-16 19:00 ` Joseph Myers
2019-01-21 19:13 ` Tejas Joshi
2019-01-21 23:03 ` Joseph Myers
2019-01-23 2:55 ` Tejas Joshi
2019-01-23 4:00 ` Tejas Joshi
2019-01-23 17:37 ` Joseph Myers
2019-01-25 19:52 ` Tejas Joshi
2019-01-25 21:32 ` Joseph Myers
2019-01-28 17:00 ` Tejas Joshi
2019-02-04 14:39 ` Tejas Joshi
2019-02-04 15:06 ` Prathamesh Kulkarni
2019-02-04 15:56 ` Tejas Joshi
2019-02-04 16:44 ` Prathamesh Kulkarni
2019-02-04 17:22 ` Tejas Joshi
2019-02-24 12:05 ` Tejas Joshi
2019-03-30 11:24 ` Tejas Joshi
2019-04-01 19:53 ` Joseph Myers
2019-04-04 13:04 ` Tejas Joshi
2019-05-04 11:20 ` Tejas Joshi
2019-05-07 17:18 ` Joseph Myers
2019-05-07 19:38 ` Tejas Joshi
2019-05-07 21:01 ` Joseph Myers
2019-05-08 3:27 ` Tejas Joshi
2019-05-08 7:30 ` Tejas Joshi
2019-05-08 14:21 ` Tejas Joshi
2019-05-09 17:01 ` Joseph Myers
2019-05-09 16:55 ` Joseph Myers
2019-05-20 15:49 ` Martin Jambor
2019-05-20 21:48 ` Joseph Myers
2019-05-29 11:21 ` Tejas Joshi
2019-05-29 18:45 ` Tejas Joshi
2019-05-30 17:08 ` Martin Jambor
2019-05-30 21:38 ` Segher Boessenkool
2019-05-31 10:11 ` Martin Jambor
2019-05-31 10:28 ` Tejas Joshi
2019-06-03 16:38 ` Joseph Myers
2019-06-04 7:03 ` Tejas Joshi
2019-06-05 12:19 ` Tejas Joshi
2019-06-06 16:43 ` Joseph Myers
2019-06-09 4:48 ` Tejas Joshi
2019-06-10 20:26 ` Joseph Myers
2019-06-12 18:52 ` Tejas Joshi
2019-06-13 12:33 ` Tejas Joshi
2019-06-13 17:19 ` Expanding roundeven (Was: Re: About GSOC.) Martin Jambor
2019-06-13 21:16 ` Joseph Myers
2019-06-14 12:49 ` Tejas Joshi
2019-06-14 17:32 ` Martin Jambor
2019-06-17 7:50 ` Tejas Joshi [this message]
2019-06-17 17:15 ` Joseph Myers
2019-06-19 13:32 ` Tejas Joshi
2019-06-22 17:11 ` Tejas Joshi
2019-06-22 17:37 ` Jan Hubicka
2019-06-17 17:10 ` Joseph Myers
2019-05-31 11:13 ` About GSOC Segher Boessenkool
2019-05-31 11:16 ` Nathan Sidwell
2019-05-31 13:30 ` Eric Gallager
2019-06-03 9:37 ` Tejas Joshi
2019-06-06 16:56 ` Committing patches and other conventions (Was: Re: About GSOC) Martin Jambor
2019-06-09 4:57 ` Tejas Joshi
2019-06-12 13:48 ` Tejas Joshi
2019-06-13 17:02 ` 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=CACMrGjAtTNDZ8GPbgMXp2iVjO5UBMORwbSQZcHwvkF1zA4z4pA@mail.gmail.com \
--to=tejasjoshi9673@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=joseph@codesourcery.com \
--cc=mjambor@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).