From: Nick Clifton <nickc@redhat.com>
To: Indu Bhagat <indu.bhagat@oracle.com>, binutils@sourceware.org
Subject: Re: Testing patches before push to trunk
Date: Wed, 2 Nov 2022 11:53:22 +0000 [thread overview]
Message-ID: <a92b1741-2219-f03d-e9c7-9aaa118461d0@redhat.com> (raw)
In-Reply-To: <531f662f-f994-405d-7560-9b022041e382@oracle.com>
Hi Indu,
> Is there a way I can test the patch series on a wider set of
> platforms/environments and weed out the issues before the
> patch set is integrated ?
You can always cross-build to more targets. This is probably
not very useful however unless the patch you are checking is
to generic code.
You can build and test with a toolchain enabled for all targets.
ie:
<path-to-binutils-sources>/configure --enable-targets=all --enable-64-bit-bfd
> If not, what other tests are recommended ?
Running the gold testsuite is generally a good idea, although
in the particular case of your sframe patch series I doubt if
this will show up any regressions.
If you want to be really thorough then building gdb from the
patched sources and then runnings its testsuite would also be
wise. Just in case there is a problem with gdb's use of the
BFD library.
Cheers
Nick
prev parent reply other threads:[~2022-11-02 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 7:05 Indu Bhagat
2022-11-02 11:49 ` Mark Wielaard
2022-11-03 1:39 ` Hans-Peter Nilsson
2022-11-02 11:53 ` Nick Clifton [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=a92b1741-2219-f03d-e9c7-9aaa118461d0@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=indu.bhagat@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).