public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Umesh Kalappa <umesh.kalappa0@gmail.com>
To: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>, gcc@gcc.gnu.org, nd <nd@arm.com>
Subject: Re: Subnormal float support in armv7(with -msoft-float) for intrinsics
Date: Tue, 17 Jul 2018 10:31:00 -0000	[thread overview]
Message-ID: <CAGfacvQo8r8Moo53xjw1fDgq7+A0bRioUCMZmz8paPHuk68=ow@mail.gmail.com> (raw)
In-Reply-To: <CAJA7tRay+WZQyq3FrNb4Y070pQ51xqS1M_3kO6sKcafp4N5+YQ@mail.gmail.com>

Will do, thanks.
Thanks

On Tue, Jul 17, 2018, 3:24 PM Ramana Radhakrishnan <
ramana.gcc@googlemail.com> wrote:

> On Tue, Jul 17, 2018 at 10:41 AM, Umesh Kalappa
> <umesh.kalappa0@gmail.com> wrote:
> > Hi Nagy,
> >
> > Please  help us with your comments on the attached patch for the issue
> > (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86512)
> >
> > Thank you and waiting for your inputs on the same.
>
>
> Patches should be sent to gcc-patches@gcc.gnu.org with a clear
> description of what the patch hopes to
> achieve and why this is correct, how was it tested and if a regression
> test needs to be added - add one please.
> Please read https://gcc.gnu.org/contribute.html before sending a patch.
>
> This is the wrong list to send patches to.
>
> regards
> Ramana
> > ~Umesh
> >
> > On Fri, Jul 13, 2018 at 1:22 PM, Umesh Kalappa <umesh.kalappa0@gmail.com>
> wrote:
> >> Thank you and issue  raised at
> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86512
> >>
> >> ~Umesh
> >>
> >> On Thu, Jul 12, 2018 at 9:33 PM, Szabolcs Nagy <szabolcs.nagy@arm.com>
> wrote:
> >>> On 12/07/18 16:20, Umesh Kalappa wrote:
> >>>>
> >>>> Hi everyone,
> >>>>
> >>>> we have our source base ,that was compiled for armv7 on gcc8.1 with
> >>>> soft-float and for following input
> >>>>
> >>>> a=0x0010000000000000
> >>>> b=0x0000000000000001
> >>>>
> >>>>   result = a - b ;
> >>>>
> >>>> we are getting the result as "0x000ffffffffffffe" and with
> >>>> -mhard-float (disabled the flush to zero mode ) we are getting the
> >>>> result as ""0x000fffffffffffff" as expected.
> >>>>
> >>>
> >>> please submit it as a bug report to bugzilla
> >>>
> >>>
> >>>> while debugging the soft-float code,we see that ,the compiler calls
> >>>> the intrinsic "__aeabi_dsub" with arm calling conventions i.e passing
> >>>> "a" in r0 and r1 registers and respectively for "b".
> >>>>
> >>>> we are investigating the routine "__aeabi_dsub" that comes from libgcc
> >>>> for incorrect result  and meanwhile we would like to know that
> >>>>
> >>>> a)do libgcc routines/intrinsic for float operations support or
> >>>> consider the subnormal values ? ,if so how we can enable the same.
> >>>>
> >>>> Thank you
> >>>> ~Umesh
> >>>>
> >>>
>

      reply	other threads:[~2018-07-17 10:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12 15:20 Umesh Kalappa
2018-07-12 16:03 ` Szabolcs Nagy
2018-07-13  7:53   ` Umesh Kalappa
2018-07-17  9:42     ` Umesh Kalappa
2018-07-17  9:54       ` Ramana Radhakrishnan
2018-07-17 10:31         ` Umesh Kalappa [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='CAGfacvQo8r8Moo53xjw1fDgq7+A0bRioUCMZmz8paPHuk68=ow@mail.gmail.com' \
    --to=umesh.kalappa0@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=nd@arm.com \
    --cc=ramana.gcc@googlemail.com \
    --cc=szabolcs.nagy@arm.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).