From: Jeffrey A Law <law@cygnus.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: egcs@cygnus.com
Subject: Re: seeking primer on adding testsuite entries ...
Date: Sat, 31 Oct 1998 16:39:00 -0000 [thread overview]
Message-ID: <12548.909880715@hurl.cygnus.com> (raw)
In-Reply-To: <199810311548.KAA01250@caip.rutgers.edu>
In message < 199810311548.KAA01250@caip.rutgers.edu >you write:
> I'd like to create some testsuite entries for gcc warnings,
> (i.e, testing if the warnings DTRT.)
>
> Would someone please let me know which docs are most appropriate
> to read on how to put this together? Eg, things like how to pass special
> flags to tests and how to specify expected output. Or just point out
> examples from the existing testsuite. (I'm willing to RTFM, I just
> don't know which FM to read.)
>
> Also where should tests I create go? Should I create a new
> directory?
For the gcc testsuite you'll want to use the "dg" framework. Examples
can be found in gcc.dg
lib/gcc-dg.exp and dg.exp in the dejagnu dist should have information on using
the dg framework.
jeff
prev parent reply other threads:[~1998-10-31 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-31 7:48 Kaveh R. Ghazi
1998-10-31 16:39 ` Jeffrey A Law [this message]
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=12548.909880715@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.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).