public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Dmitry Selyutin <ghostmansd@gmail.com>
To: binutils@sourceware.org
Cc: Alan Modra <amodra@gmail.com>, Luke Leighton <luke.leighton@gmail.com>
Subject: Re: Are big tests allowed in binutils?
Date: Fri, 17 Jun 2022 09:19:37 +0300	[thread overview]
Message-ID: <CAMqzjevMWXu_EEanfRJQ53HZo3-0AjwyZ1zNSte0sSQxfp5RoQ@mail.gmail.com> (raw)
In-Reply-To: <CAMqzjesC5j-XrC6TfSD7toZ+5yG6Ks5+c_44HPPMfgKwxf9UsQ@mail.gmail.com>

On Fri, Jun 17, 2022 at 8:11 AM Dmitry Selyutin <ghostmansd@gmail.com> wrote:
> However, I'd like to cover various possible
> cases, so I generated a test to cover many different operands; this
> makes tests quite big.

I forgot to mention another option. Since I generated these tests
anyway, perhaps I could generate them in binutils instead? I used
Python, but can rewrite it to some other language if necessary. Does
binutils testing suite possess a way to generate tests? Perhaps we
could use it. This would take some time upon $(make check), but not a
critical (it's simply a bunch of nested for loops).
An obvious option would be editing some Makefile to generate the test;
if there's an option for ppc.exp to force such generation, I'd be more
than happy to do that (this'd be a better alternative).

  reply	other threads:[~2022-06-17  6:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  5:11 Dmitry Selyutin
2022-06-17  6:19 ` Dmitry Selyutin [this message]
2022-06-20 10:42   ` Nick Alcock
2022-06-20 11:31     ` lkcl
2022-06-21 13:43       ` Nick Alcock
2022-06-21 17:26         ` lkcl
2022-06-21 17:29           ` Dmitry Selyutin
2022-06-21 19:23             ` lkcl
2022-06-17  9:14 ` Andreas Schwab
2022-06-21 15:32 ` Richard Earnshaw
2022-06-21 16:28   ` Dmitry Selyutin
2022-06-22  6:55     ` Jan Beulich

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=CAMqzjevMWXu_EEanfRJQ53HZo3-0AjwyZ1zNSte0sSQxfp5RoQ@mail.gmail.com \
    --to=ghostmansd@gmail.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=luke.leighton@gmail.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).