public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Dmitry Selyutin via Binutils <binutils@sourceware.org>
Cc: Dmitry Selyutin <ghostmansd@gmail.com>,
	 Luke Leighton <luke.leighton@gmail.com>
Subject: Re: Are big tests allowed in binutils?
Date: Fri, 17 Jun 2022 11:14:53 +0200	[thread overview]
Message-ID: <878rpvslbm.fsf@igel.home> (raw)
In-Reply-To: <CAMqzjesC5j-XrC6TfSD7toZ+5yG6Ks5+c_44HPPMfgKwxf9UsQ@mail.gmail.com> (Dmitry Selyutin via Binutils's message of "Fri, 17 Jun 2022 08:11:12 +0300")

On Jun 17 2022, Dmitry Selyutin via Binutils wrote:

> For example, the assembly listing for a new
> svremap instruction takes 10240 lines, and etalon dump takes a bit
> more lines. So, questions:
> 1. Is it OK at all to have tests that large? Time-wise they're fast,

The biggest test so far is gas/testsuite/gas/tic54x/all-opcodes.s, with
124668 lines.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  parent reply	other threads:[~2022-06-17  9:15 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
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 [this message]
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=878rpvslbm.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=binutils@sourceware.org \
    --cc=ghostmansd@gmail.com \
    --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).