public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/8087: sparc-sun-solaris2.7 C testsuite failures in execute/20020720-1.c w/-m64 or on sparcv9/sparc64
Date: Mon, 07 Oct 2002 10:26:00 -0000 [thread overview]
Message-ID: <20021007172600.18078.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/8087; it has been noted by GNATS.
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: davem@gcc.gnu.org, davem@redhat.com, gcc-bugs@gcc.gnu.org,
gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, jakub@redhat.com,
roger@eyesopen.com, rth@redhat.com
Cc:
Subject: Re: target/8087: sparc-sun-solaris2.7 C testsuite failures in execute/20020720-1.c w/-m64 or on sparcv9/sparc64
Date: Mon, 7 Oct 2002 13:16:05 -0400 (EDT)
BTW, I think there are two problems with the XFAIL code that was
recently added. With the first hunk, you set torture_execute_xfail
and I believe the testcase fails to *compile* on those targets. (You
get the link failure when the opt doesn't occur right?) If the
testcase compiles you should never expect an execute failure.
I came to this conclusion via visual inspection not any direct
testing, but I believe you need to set torture_compile_xfail there
instead.
The second hunk for sparc -m64 looks correct, but it doesn't work for
me for some reason. See:
http://gcc.gnu.org/ml/gcc-testresults/2002-10/msg00194.html
I'm not sure why, perhaps that one only looks for execute failures,
not compile failures? Not sure. Can you reproduce it?
--Kaveh
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu
next reply other threads:[~2002-10-07 17:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 10:26 Kaveh R. Ghazi [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-07 11:46 Richard Henderson
2002-10-07 11:46 Roger Sayle
2002-10-07 11:36 David S. Miller
2002-10-07 11:26 Roger Sayle
2002-10-07 9:26 Roger Sayle
2002-10-07 9:26 David S. Miller
2002-10-07 9:16 Roger Sayle
2002-10-07 9:16 David S. Miller
2002-10-07 0:22 davem
2002-10-03 8:06 Kaveh R. Ghazi
2002-10-02 17:26 David S. Miller
2002-10-02 7:56 Kaveh R. Ghazi
2002-09-30 17:26 Roger Sayle
2002-09-30 16:56 Richard Henderson
2002-09-30 16:36 David S. Miller
2002-09-30 16:26 Richard Henderson
2002-09-30 15:52 davem
2002-09-28 21:46 ghazi
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=20021007172600.18078.qmail@sources.redhat.com \
--to=ghazi@caip.rutgers.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).