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/6299: sparcv9-sun-solaris2.7 gcc-3.1 C testsuite failure in execute/950511-1.c
Date: Mon, 15 Apr 2002 19:06:00 -0000	[thread overview]
Message-ID: <20020416020601.6383.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/6299; it has been noted by GNATS.

From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: rth@redhat.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: target/6299: sparcv9-sun-solaris2.7 gcc-3.1 C testsuite failure in execute/950511-1.c
Date: Mon, 15 Apr 2002 21:56:20 -0400 (EDT)

  > From: Richard Henderson <rth@redhat.com>
  > 
  > On Sun, Apr 14, 2002 at 04:03:24PM -0000, ghazi@caip.rutgers.edu wrote:
  > > It started as of a 4/12/2002 checkout:
  > > http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg00478.html
  > > 
  > > ***  This is a regression from 3.0.3 and 2.95.2.
  > 
  > Are you sure?  It actually "started" by config.guess starting
  > to generate v9 code by default.
  > r~
 
 Perhaps, but I look at it this way: I have a solaris box which happens
 to allow sparcv9 insns.  The older gcc's installed on that system out
 of the box run the testcase fine.  The current 3.1 snapshot out of the
 box doesn't.
 
 While the "guessed" configuration may have changed, from the user
 perspective its a regression because they don't know or care about the
 internal nuances of config.guess like we do.
 
 		--Kaveh
 --
 Kaveh R. Ghazi			Director of Systems Architecture
 ghazi@caip.rutgers.edu		Qwest Global Services


             reply	other threads:[~2002-04-16  2:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15 19:06 Kaveh R. Ghazi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-18  9:16 ghazi
2002-04-15 19:16 Richard Henderson
2002-04-15 18:26 Richard Henderson
2002-04-14  9:06 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=20020416020601.6383.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).