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/8366: sparc-sun-solaris2.7 C testsuite failure w/-m64 -fpic -O in execute/loop-2d.c
Date: Mon, 28 Oct 2002 16:36:00 -0000 [thread overview]
Message-ID: <20021029003601.8218.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/8366; it has been noted by GNATS.
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: davem@redhat.com, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
jakub@redhat.com, jbuck@synopsys.com, mark@codesourcery.com,
rth@redhat.com
Cc:
Subject: Re: target/8366: sparc-sun-solaris2.7 C testsuite failure w/-m64 -fpic -O in execute/loop-2d.c
Date: Mon, 28 Oct 2002 19:28:08 -0500 (EST)
> From: Joe Buck <jbuck@synopsys.com>
>
> Do we have any reports of this testcase working for 64-bit sparc
> and any release?
In addition to the 3.2 and 3.1.1 releases, I also just tried GCC 3.0.4
on sparcv9 and still got the error. (Regular sparc bi-arch is
disabled in 3.0.4, so I couldn't try plain sparc with -m64.) I also
tried 2.95 but couldn't get sparcv9 to build there.
I'm content with this PR not being a "regression" and thus getting
less attention. However our release criteria state that we will test
with PIC flags too. See http://gcc.gnu.org/gcc-3.1/criteria.html
under "Regresstion Tests". I offer the report and the sparc
maintainers can decide if it warrants pursuing in 3.2.x or later on
the trunk. I'm fine with whatever they decide.
--Kaveh
PS: Minor note, we don't have any updated 3.2.x or 3.3 criteria AFAICT.
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu
next reply other threads:[~2002-10-29 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 16:36 Kaveh R. Ghazi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-21 11:36 target/8366: [sparc-sun-solaris2.7] " ebotcazou
2003-03-08 11:53 ebotcazou
2002-10-29 9:56 target/8366: sparc-sun-solaris2.7 " Joe Buck
2002-10-28 19:06 Joe Buck
2002-10-28 11:16 Joe Buck
2002-10-26 9: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=20021029003601.8218.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).