public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
	"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: gprofng testing
Date: Wed, 10 May 2023 12:20:30 +0100	[thread overview]
Message-ID: <993188ec-0507-1f4d-0adc-cffe3dc7119f@redhat.com> (raw)
In-Reply-To: <3b4cae18-3c42-d8e1-517d-09463c270d4d@oracle.com>

Hi Vladimir,

> I want to add more tests for gprofng.

That would be most appreciated.

> These tests use pre-existing experiments and binaries.
> Each test has a golden file which we compare against the new gprofng output.
> 
> We never rebuilt the experiments and binaries. But sometimes we changed the golden file.
> The size of experiments can be big.
> The size of gold files is usually small.
> 
> How to make such tests public?

With difficulty.  The size of the experiment files will be an obstacle
I expect.  Is it possible to instead provide a source file and have the
test compile it first instead ?

Assuming that the answer to that question is no, then is it possible
to create smaller test cases, or to compress the test files files and
then decompress them when they are being used ?

My best suggestion would be to create lots of small tests rather than
several large tests.  If that is possible.

> PS.
> I see that the old gprof doesn't have tests inside binutils-gdb.git. How do we test gprof?

We don't. :-(

Gprof is very old and was added to the binutils long ago.  Long before
testsuites were invented.  OK, so that is not quite true, testsuites
have been around for as along as code has been around, but the gprof
sources were added to the binutils without a testsuite and noone has
seen fit to create one since.  Of course if you are volunteering, I
will not say "no"...

Cheers
   Nick



  reply	other threads:[~2023-05-10 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 22:32 Vladimir Mezentsev
2023-05-10 11:20 ` Nick Clifton [this message]
2023-05-11  0:51   ` Vladimir Mezentsev
2023-05-17 13:40     ` Nick Clifton

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=993188ec-0507-1f4d-0adc-cffe3dc7119f@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=vladimir.mezentsev@oracle.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).