public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
		Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
Subject: Re: [PATCH, rs6000, testsuite] Skip gfortran.dg/round_4.f90 for PowerPC Linux
Date: Mon, 30 Jun 2014 15:28:00 -0000	[thread overview]
Message-ID: <CAGWvnyk6u0wBr=bPVK1G_WtOGPDszPDBvZM9MJyatfrTpxFf2g@mail.gmail.com> (raw)
In-Reply-To: <1404092897.3097.9.camel@gnopaine>

On Sun, Jun 29, 2014 at 9:48 PM, Bill Schmidt
<wschmidt@linux.vnet.ibm.com> wrote:
> Hi,
>
> The test in gfortran.dg/round_4.f90, introduced in GCC 4.9, checks for
> correct behavior of different rounding modes.  However, for
> quad-precision floating-point, it requires that the number
> 0.10000000000000000000000000000000000481 be exactly represented.  Since
> the PowerPC long double implementation (double-double) only guarantees
> 31 bits of precision, the test fails for the real(qp) portions of the
> test.  Thus this patch marks the test invalid for PowerPC Linux for now.
> (We may want to also do this for other subtargets; let me know if so.)
>
> At such time as IEEE 128-bit floating-point is supported by the PowerPC
> port, we should revisit this.
>
> Is this ok for trunk and 4.9?
>
> Thanks,
> Bill
>
>
> 2014-06-29  Bill Schmidt  <wschmidt@linux.vnet.ibm.com>
>
>         * gfortran.dg/round_4.f90: Skip for powerpc*-*-linux* since the
>         test requires greater precision than the current PowerPC long
>         double implementation supports.

Okay.

I wonder if this is passing on AIX because AIX defaults to double?

Thanks, David

  reply	other threads:[~2014-06-30 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30  1:48 Bill Schmidt
2014-06-30 15:28 ` David Edelsohn [this message]
2014-06-30 16:16 ` Mike Stump
2014-06-30  9:57 Tobias Burnus

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='CAGWvnyk6u0wBr=bPVK1G_WtOGPDszPDBvZM9MJyatfrTpxFf2g@mail.gmail.com' \
    --to=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tobias.burnus@physik.fu-berlin.de \
    --cc=wschmidt@linux.vnet.ibm.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).