From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org,
libffi-discuss@sourceware.org,
Andreas Tobler <andreast@gcc.gnu.org>
Subject: Re: [testsuite, libffi] XFAIL libffi.call/cls_{,long}double_va.c on IRIX 6.5 (PR libffi/46660)
Date: Wed, 29 Jun 2011 13:43:00 -0000 [thread overview]
Message-ID: <yddei2c3g8r.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <BANLkTi=_+uGjc7kVDDh-cH+53Ff=fFKq0w@mail.gmail.com> (H. J. Lu's message of "Wed, 29 Jun 2011 06:41:25 -0700")
"H.J. Lu" <hjl.tools@gmail.com> writes:
>> Index: libffi/testsuite/libffi.call/cls_double_va.c
>> ===================================================================
>> --- libffi/testsuite/libffi.call/cls_double_va.c (revision 175618)
>> +++ libffi/testsuite/libffi.call/cls_double_va.c (working copy)
>> @@ -6,7 +6,7 @@
>>
>> /* { dg-do run { xfail strongarm*-*-* xscale*-*-* } } */
>> /* { dg-output "" { xfail avr32*-*-* } } */
>> -/* { dg-output "PR libffi/46660" { xfail mips-sgi-irix6* } } */
>> +/* { dg-output "" { xfail mips-sgi-irix6* } } PR libffi/46660 */
>> /* { dg-skip-if "" arm*-*-* { "-mfloat-abi=hard" } { "" } } */
>>
>
> Why not just add mips-sgi-irix6* to avr32*-*-*?
So the corresponding PR can be noted. If you list it without
attribution, you'd have to search all of them to find which one is for
IRIX.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2011-06-29 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 8:27 Rainer Orth
2011-06-29 12:40 ` Richard Guenther
2011-06-29 12:53 ` Rainer Orth
2011-06-29 13:41 ` H.J. Lu
2011-06-29 13:43 ` Rainer Orth [this message]
2011-06-29 13:52 ` David Gilbert
2011-06-29 13:54 ` Rainer Orth
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=yddei2c3g8r.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=andreast@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=java-patches@gcc.gnu.org \
--cc=libffi-discuss@sourceware.org \
--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).