public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: <guerby@acm.org>
To: kenner@vlsi1.ultra.nyu.edu
Cc: gcc@gcc.gnu.org
Subject: Re: ACATS B tests
Date: Fri, 07 Dec 2001 04:55:00 -0000	[thread overview]
Message-ID: <200112071219.fB7CJEe10610@ulmo.localdomain> (raw)
In-Reply-To: <10112071215.AA06775@vlsi1.ultra.nyu.edu> (kenner@vlsi1.ultra.nyu.edu)

> OK, I give up.  Why is that?  Is it because the error was supposed to be
> on the *previous* line?

My rough estimate is that yes, about half of errors will be generated
not on the line flagged as ERROR, but I haven't looked at the whole B
tests, just enough to realize that it is a huge task.

> BTW, what is your plan with regard to macro substitutions?  I assume you'll
> remove the CE tests that need absolute filenames, right?

I believe the 3 CE tests doing smart things with filenames have been
removed, I have to recheck otherwise I won't bother with them.

I plan to commit with all macro substituted, most macro deal with the
testsuite being tailored to one special compiler, and we have only one
compiler out there :). GNAT handles platform specific stuff using
Standard'Attribute in a uniform source way, no need for target macros
as far as ACATS for GCC is concerned.

-- 
Laurent Guerby <guerby@acm.org>

  reply	other threads:[~2001-12-07 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07  4:29 Richard Kenner
2001-12-07  4:55 ` guerby [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-07 18:35 dewar
2001-12-07  3:18 ACATS legal status cleared by FSF Richard Kenner
2001-12-07  4:20 ` ACATS B tests guerby

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=200112071219.fB7CJEe10610@ulmo.localdomain \
    --to=guerby@acm.org \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).