This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: target/8366: sparc-sun-solaris2.7 C testsuite failure w/-m64 -fpic -O in execute/loop-2d.c
- From: Joe Buck <jbuck at synopsys dot com>
- To: ghazi at caip dot rutgers dot edu (Kaveh R. Ghazi)
- Cc: davem at redhat dot com, gcc-bugs at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org, jakub at redhat dot com, Joe dot Buck at synopsys dot COM, mark at codesourcery dot com, rth at redhat dot com
- Date: Mon, 28 Oct 2002 19:00:11 -0800 (PST)
- Subject: Re: target/8366: sparc-sun-solaris2.7 C testsuite failure w/-m64 -fpic -O in execute/loop-2d.c
I wrote:
> > Do we have any reports of this testcase working for 64-bit sparc
> > and any release?
Kaveh writes:
> 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.
Fixing a non-regression in 3.2.1 would violate the release criteria for
point releases. I wouldn't object to an exception if we had a fix in
hand, but with 18 release-critical bugs we need to start getting real, and
looking at what to drop. And it's the release manager's decision, not the
sparc maintainer's decision.
If it were me, I'd punt this one to 3.3 and look for others to punt as
well.