public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: phil@jaj.com
Cc: bkoz@redhat.com, gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org,
	gdr@integrable-solutions.net, libstdc++@gcc.gnu.org
Subject: Re: Analysis of solaris2 27_io/istream_extractor_arith.cc failures
Date: Sun, 05 Jan 2003 19:36:00 -0000	[thread overview]
Message-ID: <200301051851.NAA11376@caip.rutgers.edu> (raw)
In-Reply-To: <20030105054404.A24241@disaster.jaj.com>

 > From: Phil Edwards <phil@jaj.com>
 > 
 > On Sun, Jan 05, 2003 at 01:16:24AM -0500, Kaveh R. Ghazi wrote:
 > > Ok, but does pushing files down one directory level require hacking
 > > the test framework or will it "just work" merely by splitting and
 > > moving the files?  If the former, would you please point me at the
 > > .exp file that needs updating?
 > 
 > lib/libstdc++-v3-dg.exp:
 >     proc libstdc++-v3-init, location of the .txt and .tst files
 >     proc libstdc++-v3-list-sourcefiles, building the list of .cc files


Thanks, that's exactly what I needed.  I've got something testing now.

--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu

  reply	other threads:[~2003-01-05 18:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-26 17:51 Kaveh R. Ghazi
2002-12-26 19:16 ` Gabriel Dos Reis
2002-12-26 21:56   ` Kaveh R. Ghazi
2003-01-04 14:56     ` Kaveh R. Ghazi
2003-01-05  1:55     ` Benjamin Kosnik
2003-01-05  2:18       ` Gabriel Dos Reis
2003-01-05  4:57         ` Benjamin Kosnik
2003-01-05  6:31       ` Kaveh R. Ghazi
2003-01-05 11:19         ` Phil Edwards
2003-01-05 19:36           ` Kaveh R. Ghazi [this message]
2003-01-06  4:38           ` Kaveh R. Ghazi
2003-01-06  5:18             ` Benjamin Kosnik

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=200301051851.NAA11376@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=bkoz@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=libstdc++@gcc.gnu.org \
    --cc=phil@jaj.com \
    /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).