Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: New FAIL gdb.base/float128.exp on ppc64le  [Re: [RFC v2][2/2] Target FP: Make use of MPFR if available]
Date: Wed, 20 Jun 2018 12:50:00 -0000	[thread overview]
Message-ID: <20180620125031.GA1067098@host1.jankratochvil.net> (raw)
In-Reply-To: <20180620123330.A6938D80294@oc3748833570.ibm.com>

On Wed, 20 Jun 2018 14:33:30 +0200, Ulrich Weigand wrote:
> A result of "inf" instead of the large number is exactly the problem that
> is fixed by using MPFR.  So I'm wondering: is the GDB that shows the FAIL
> actually built against MPFR?  If at build time MPFR was not detected,
> then this failure is exactly what you'd expect ...

Thanks for the heads up, our GDB build was really missing this dependency.

Still maybe the testcase should contain such explanation of the FAIL.
Moreover maybe it could be an XFAIL.


Thanks,
Jan


  reply	other threads:[~2018-06-20 12:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 19:00 [RFC v2][2/2] Target FP: Make use of MPFR if available Ulrich Weigand
2017-11-29  0:37 ` John Baldwin
2017-11-29 17:55   ` Ulrich Weigand
2017-11-29 18:04     ` Pedro Alves
2017-11-30  0:27     ` John Baldwin
2017-12-10 15:10 ` Regression on i686 host: gdb.base/floatn.exp: " Jan Kratochvil
2017-12-10 15:13   ` Jan Kratochvil
2017-12-11 14:14     ` Ulrich Weigand
2017-12-11 14:30       ` Ulrich Weigand
2018-06-20  8:55 ` New FAIL gdb.base/float128.exp on ppc64le [Re: [RFC v2][2/2] Target FP: Make use of MPFR if available] Jan Kratochvil
2018-06-20 12:33   ` Ulrich Weigand
2018-06-20 12:50     ` Jan Kratochvil [this message]
2018-06-20 13:39       ` Ulrich Weigand
2018-06-20 13:47         ` Jan Kratochvil
2018-06-20 14:28           ` Ulrich Weigand

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=20180620125031.GA1067098@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.com \
    --cc=uweigand@de.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