public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Ulf Samuelsson <binutils@emagii.com>, binutils@sourceware.org
Subject: Re: [PATCH v4 2/5] CRC64 testsuite
Date: Thu, 23 Feb 2023 10:10:23 +0000	[thread overview]
Message-ID: <e361db21-95a6-c818-0ca0-84db3ca5c8d6@redhat.com> (raw)
In-Reply-To: <1b334d25-10ee-cd05-b2d8-20143ee118a5@emagii.com>

Hi Ulf,


>> Did you actually try running these new tests ?
>>
> No, I am yet to learn how to do the tests
> so I hoped that copying the the resulting text segment
> would be sufficient, and if not, someone would tell me.
> 
> Is there any documentation on how to run the tests?

Just run "make check".  (In the top level directory where
you built the binutils).

Or if you only want to run one specific testsuite, eg the
linker testsuite then change into the relevant directory and
run "make check"

Or, if you only want to run a sub-set of a specific testsuite
then use the RUNTESTFLAGS option to specify the test script
you want to run.  For example if you only want to run the
linker script tests then:

   % cd <binutils-build-dir>/ld
   & make check RUNTESTFLAGS="ld-scripts/script.exp"

Note - when you are creating a patch that affects generic
binutils code, such as your CRC64 patch series, it is a good
idea to test multiple versions of the binutils each built for
a different target architecture.  At a minimum I would suggest
using builds configure with:

   --target=x86_64-pc-linux-gnu
   --target=x86_64-w64-mingw32
   --target=aarch64-linux-gnu
   --target=powerpc64-linux-gnu
   --target=mips-elf
   --enable-targets=all --enable-64-bit-bfd

Cheers
   Nick



  reply	other threads:[~2023-02-23 10:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-19 19:45 [PATCH v4 0/5 Add support for CRC64 generation in linker binutils
2023-02-19 19:45 ` [PATCH v4 1/5] CRC64 commands documentation binutils
2023-02-19 19:50   ` [PATCH v4 0/5] Add support for CRC64 generation in linker Ulf Samuelsson
2023-02-21 12:02     ` Nick Clifton
2023-02-21 13:10       ` Ulf Samuelsson
2023-02-21 13:30       ` Ulf Samuelsson
2023-02-21 12:53   ` [PATCH v4 1/5] CRC64 commands documentation Nick Clifton
2023-02-21 13:24     ` Ulf Samuelsson
2023-02-19 19:45 ` [PATCH v4 2/5] CRC64 testsuite binutils
2023-02-21 12:42   ` Nick Clifton
2023-02-21 15:13     ` Ulf Samuelsson
2023-02-23 10:10       ` Nick Clifton [this message]
2023-02-23 10:53         ` Ulf Samuelsson
2023-02-23 11:01           ` Nick Clifton
2023-02-28 11:11         ` Ulf Samuelsson
2023-02-28 12:37           ` Nick Clifton
2023-02-28 13:01             ` Ulf Samuelsson
2023-02-28 13:06               ` Nick Clifton
2023-02-28 14:24                 ` Ulf Samuelsson
2023-02-28 13:45             ` Ulf Samuelsson
2023-02-19 19:45 ` [PATCH v4 3/5] ldlex.l: CRC64 binutils
2023-02-19 19:45 ` [PATCH v4 4/5] ldgram.y: CRC64 binutils
2023-02-19 19:45 ` [PATCH v4 5/5] Calculate CRC64 over the .text area binutils
2023-02-21 13:26   ` Nick Clifton
2023-02-23  8:36     ` Ulf Samuelsson

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=e361db21-95a6-c818-0ca0-84db3ca5c8d6@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@emagii.com \
    --cc=binutils@sourceware.org \
    /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).