From: Nick Alcock <nick.alcock@oracle.com>
To: binutils@sourceware.org
Subject: [PATCH 0/3] libctf: small fixes
Date: Fri, 25 Jun 2021 17:12:40 +0100 [thread overview]
Message-ID: <20210625161243.4747-1-nick.alcock@oracle.com> (raw)
This patch series is small stuff confined to libctf/ and not needing
review: problems with the relink at install time picking up the wrong
libbfd (PR libctf/27360), problems with backward-compatibility code to
handle symtypetab sections emitted by obsolete pre-upstreaming
CTF-capable GCCs; and some warnings causing spurious test failures on
some platforms.
No review needed unless people really want to.
Nick Alcock (3):
libctf: link against libiberty before linking in libbfd or
libctf-nobfd
libctf: fix handling of CTF symtypetab sections emitted by older GCC
libctf, testsuite: fix various warnings in tests
libctf/Makefile.am | 6 +++++-
libctf/Makefile.in | 7 ++++++-
libctf/ctf-open.c | 7 ++++---
libctf/testsuite/libctf-lookup/conflicting-type-syms.c | 3 ---
libctf/testsuite/libctf-lookup/enum-symbol.c | 3 ---
.../libctf-regression/nonstatic-var-section-ld-r.c | 4 ++--
.../testsuite/libctf-regression/nonstatic-var-section-ld.c | 4 ++--
.../libctf-regression/nonstatic-var-section-ld.lk | 2 +-
libctf/testsuite/libctf-regression/pptrtab.c | 1 -
.../testsuite/libctf-regression/type-add-unnamed-struct.c | 2 --
libctf/testsuite/libctf-writable/pptrtab.c | 2 +-
.../libctf-writable/reserialize-strtab-corruption.c | 1 -
.../libctf-writable/symtypetab-nonlinker-writeout.c | 6 ++++--
13 files changed, 25 insertions(+), 23 deletions(-)
--
2.32.0.255.gd9b1d14a2a
next reply other threads:[~2021-06-25 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 16:12 Nick Alcock [this message]
2021-06-25 16:12 ` [PATCH 1/3] libctf: link against libiberty before linking in libbfd or libctf-nobfd Nick Alcock
2021-06-25 16:12 ` [PATCH 2/3] libctf: fix handling of CTF symtypetab sections emitted by older GCC Nick Alcock
2021-06-25 16:12 ` [PATCH 3/3] libctf, testsuite: fix various warnings in tests Nick Alcock
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=20210625161243.4747-1-nick.alcock@oracle.com \
--to=nick.alcock@oracle.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).