public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
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 19:06:00 -0000 [thread overview]
Message-ID: <20021029030601.13440.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/8366; it has been noted by GNATS.
From: Joe Buck <jbuck@synopsys.com>
To: ghazi@caip.rutgers.edu (Kaveh R. Ghazi)
Cc: davem@redhat.com, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
jakub@redhat.com, Joe.Buck@synopsys.COM, mark@codesourcery.com,
rth@redhat.com
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:00:11 -0800 (PST)
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.
next reply other threads:[~2002-10-29 3:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 19:06 Joe Buck [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 16:36 Kaveh R. Ghazi
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=20021029030601.13440.qmail@sources.redhat.com \
--to=jbuck@synopsys.com \
--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).