public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/32258] Testsuite reports - FAIL: gcc.dg/torture/builtin-pow-mpfr-1.c
Date: Sun, 17 Jun 2007 14:07:00 -0000	[thread overview]
Message-ID: <20070617140748.1276.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32258-13830@http.gcc.gnu.org/bugzilla/>



------- Comment #17 from rob1weld at aol dot com  2007-06-17 14:07 -------
Due to the bugs in mpfr ( http://www.mpfr.org/mpfr-2.2.1/#bugs ) we should
probably _require_ a recent version. 

It would be kind of someone else to make that patch - I am kinda busy at the
moment. The section "File: mpfr.info,  Node: Miscellaneous Functions" provides
the macros. Mpfr p5 may have bugs in it but it is the newest available so we
should require that version at least.

Using an old version (without an expect script to print a "WARNING:" line in
the testsuite) will drive people buggy trying to find out why their code is
broken when in fact it is the user's library that is needing fixing.

Applying these changes can clean a few errors off the testsuite and put us a
step closer to a release. Please don't prefer patching the testsuite to skip
tests on the basis that the user has an old unsupported version of mpfr.

The lines in configure that need changes are:
#if MPFR_VERSION < MPFR_VERSION_NUM(2,2,0)
#if MPFR_VERSION < MPFR_VERSION_NUM(2,2,1)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32258


  parent reply	other threads:[~2007-06-17 14:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 16:32 [Bug c/32258] New: " rob1weld at aol dot com
2007-06-08 17:14 ` [Bug c/32258] " kargl at gcc dot gnu dot org
2007-06-09  3:17 ` rob1weld at aol dot com
2007-06-09 17:06 ` kargl at gcc dot gnu dot org
2007-06-11 17:00 ` [Bug middle-end/32258] " rob1weld at aol dot com
2007-06-11 18:47 ` rob1weld at aol dot com
2007-06-12  4:56 ` rob1weld at aol dot com
2007-06-12  5:00 ` pinskia at gcc dot gnu dot org
2007-06-12 10:53 ` rob1weld at aol dot com
2007-06-12 15:15 ` rguenth at gcc dot gnu dot org
2007-06-12 15:31 ` pinskia at gcc dot gnu dot org
2007-06-13  8:06 ` rob1weld at aol dot com
2007-06-13  9:32 ` rob1weld at aol dot com
2007-06-13  9:39 ` rob1weld at aol dot com
2007-06-13 12:09 ` rguenth at gcc dot gnu dot org
2007-06-13 23:39 ` rob1weld at aol dot com
2007-06-14  7:41 ` rob1weld at aol dot com
2007-06-17 14:07 ` rob1weld at aol dot com [this message]
2007-06-17 20:46 ` rob1weld at aol dot com
2007-06-20  5:09 ` rob1weld at aol dot com
2007-06-23  9:30 ` rob1weld at aol dot com
2009-02-28 14:10 ` rob1weld at aol dot com

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=20070617140748.1276.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).