From: Janis Johnson <janis187@us.ibm.com>
To: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>
Cc: Janis Johnson <janis187@us.ibm.com>,
Richard Guenther <richard.guenther@gmail.com>,
gcc-patches@gcc.gnu.org, Joe.Buck@synopsys.com
Subject: Re: [PATCH]: PR middle-end/30250, use MPFR for lgamma_r/gamma_r
Date: Thu, 24 May 2007 22:43:00 -0000 [thread overview]
Message-ID: <20070524222822.GA6801@us.ibm.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0705241658320.9124@caipclassic.rutgers.edu>
On Thu, May 24, 2007 at 05:09:11PM -0400, Kaveh R. GHAZI wrote:
> On Thu, 24 May 2007, Janis Johnson wrote:
>
> > On Thu, May 24, 2007 at 10:15:22AM +0200, Richard Guenther wrote:
> > > On 5/24/07, Richard Guenther <richard.guenther@gmail.com> wrote:
> > > >On 5/24/07, Kaveh R. GHAZI <ghazi@caip.rutgers.edu> wrote:
> > > >> On Wed, 23 May 2007, Richard Guenther wrote:
> > > >>
> > > >> > This:
> > > >> >
> > > >> > /* Expect failures at least until mpfr-2.3.0 is released. */
> > > >> > /* { dg-xfail-if "mpfr-2.3.0" { *-*-* } } */
> > > >> >
> > > >> > doesn't work. Or did you forget a testsuite/lib patch?
> >
> > This should be:
> > /* { dg-xfail-if "mpfr-2.3.0" { *-*-* } { "*" } { "" } } */
> > The "mpfr-2.3.0" is a comment. The lists of included and excluded
> > options are not optional; I'm surprised it works.
> > > Updating to dejagnu 1.4.4 fixed it. Luckily that still works with old tcl
> > > ;)
> > Magic.
> > Janis
>
> Oh okay, I thought those flags were optional because I saw it like that
> somewhere else (and of course it passed my own testing). Search, search,
> search... ah, here's one: gcc.dg/Warray-bounds.c.
>
> Anyway, I'm happy to fix the one I introduced. I also made the comment
> more verbose to clarify that it is in fact a comment and not some magic
> pattern search for an mpfr version.
>
> Tested via "make check" using mpfr-2.2.1 and mpfr-2.3.0-svn. I still get
> XFAIL and XPASS respectively as desired.
>
> Okay for mainline?
Yes, thanks.
Janis
next prev parent reply other threads:[~2007-05-24 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 16:04 Kaveh R. GHAZI
2007-05-17 10:15 ` Richard Guenther
2007-05-19 4:23 ` Kaveh R. GHAZI
2007-05-23 21:53 ` Richard Guenther
2007-05-23 22:57 ` Kaveh R. GHAZI
2007-05-24 8:15 ` Richard Guenther
2007-05-24 10:16 ` Richard Guenther
2007-05-24 16:59 ` Janis Johnson
2007-05-24 21:09 ` Kaveh R. GHAZI
2007-05-24 22:43 ` Janis Johnson [this message]
2007-05-24 16:46 ` Joe Buck
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=20070524222822.GA6801@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=Joe.Buck@synopsys.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
--cc=richard.guenther@gmail.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).