public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: echristo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/6203: Failure of test gcc.c-torture/execute/20010122-1.c on irix6
Date: Tue, 09 Apr 2002 07:06:00 -0000	[thread overview]
Message-ID: <20020409140602.5580.qmail@sources.redhat.com> (raw)

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

From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: David.Billinghurst@riotinto.com, echristo@gcc.gnu.org,
        gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        mark@codesourcery.com, nobody@gcc.gnu.org
Cc:  
Subject: Re: c/6203: Failure of test gcc.c-torture/execute/20010122-1.c on irix6
Date: Tue, 9 Apr 2002 10:05:07 -0400 (EDT)

  > From: echristo@gcc.gnu.org
  > 
  > Synopsis: Failure of test gcc.c-torture/execute/20010122-1.c on irix6
  > 
  > Responsible-Changed-From-To: unassigned->echristo
  > Responsible-Changed-By: echristo
  > Responsible-Changed-When: Tue Apr  9 01:03:22 2002
  > Responsible-Changed-Why:
  >     mine
  > State-Changed-From-To: open->feedback
  > State-Changed-By: echristo
  > State-Changed-When: Tue Apr  9 01:03:22 2002
  > State-Changed-Why:
  >     This bug should be fixed in mainline, but is not a regression from the previous release so I doubt the bug will be fixed for 3.1.
  > 
  > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6203
 
 Can you please identify the patch which fixed it on the mainline so we
 can evaluate how risky it is?  If it's not a candidate for 3.1.0, it
 may be appropriate for 3.1.1.
 
 		Thanks,
 		--Kaveh
 --
 Kaveh R. Ghazi			Director of Systems Architecture
 ghazi@caip.rutgers.edu		Qwest Global Services


             reply	other threads:[~2002-04-09 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09  7:06 Kaveh R. Ghazi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-16 17:23 ghazi
2002-04-09  1:03 echristo
2002-04-06  3:46 David.Billinghurst

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=20020409140602.5580.qmail@sources.redhat.com \
    --to=ghazi@caip.rutgers.edu \
    --cc=echristo@gcc.gnu.org \
    --cc=gcc-prs@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).