From: Nick Alcock <nick.alcock@oracle.com>
To: "H.J. Lu via Binutils" <binutils@sourceware.org>
Cc: Nick Alcock <nick.alcock@oracle.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
weimin.pan@oracle.com
Subject: Re: [PATCH 00/13] CTF dumper improvements, a lookup testsuite, and bugfixes
Date: Tue, 05 Jan 2021 19:05:27 +0000 [thread overview]
Message-ID: <87a6tnnr0o.fsf@esperi.org.uk> (raw)
In-Reply-To: <CAMe9rOrzCV6yZ0diqFWqcUcSUGi3-iR030We85Yk46ASoWjWeA@mail.gmail.com> (H. J. Lu via Binutils's message of "Tue, 5 Jan 2021 10:52:18 -0800")
On 5 Jan 2021, H. J. Lu via Binutils uttered the following:
> Can you verify and check in the check_ctf_available change first to
> unbreak cross binutils?
This is all the same change: check_ctf_available crashes without all the
other stuff :(
But yes, I'm verifying now. (I presume you see it not only in cross
builds but in any build with a non-ctf-capable compiler.)
next prev parent reply other threads:[~2021-01-05 19:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 19:51 Nick Alcock
2020-12-18 19:51 ` [PATCH 01/13] libctf: do not print array declarators backwards Nick Alcock
2020-12-18 19:51 ` [PATCH 02/13] libctf, ld: CTF dumper changes for consistency Nick Alcock
2020-12-18 19:51 ` [PATCH 03/13] libctf, ld: more dumper improvements Nick Alcock
2020-12-18 19:51 ` [PATCH 04/13] libctf, ld: prohibit doing things with forwards prohibited in C Nick Alcock
2020-12-27 17:43 ` Nick Alcock
2020-12-28 2:04 ` Nick Alcock
2020-12-29 11:52 ` [PATCH v2] libctf, ld: prohibit getting the size or alignment of forwards Nick Alcock
2020-12-18 19:51 ` [PATCH 05/13] libctf, ld: dump enums: generally improve dump formatting Nick Alcock
2020-12-18 19:51 ` [PATCH REVIEW 06/13] libctf: rip out BFD_DEPENDENCIES / BFD_LIBADD Nick Alcock
2020-12-18 19:51 ` [PATCH REVIEW 07/13] libctf: new testsuite Nick Alcock
2020-12-29 11:52 ` [PATCH v2] " Nick Alcock
2020-12-18 19:51 ` [PATCH 08/13] libctf: new test of enum lookups with the _next iterator Nick Alcock
2020-12-18 19:51 ` [PATCH 09/13] libctf: warn about information loss because of unreleased format changes Nick Alcock
2020-12-18 19:51 ` [PATCH 10/13] libctf, include: support unnamed structure members better Nick Alcock
2020-12-18 19:51 ` [PATCH 11/13] libctf: remove outdated comment about parent dict importing Nick Alcock
2020-12-18 19:51 ` [PATCH 12/13] libctf: fix lookups of pointers by name in parent dicts Nick Alcock
2020-12-18 19:51 ` [PATCH 13/13] libctf, ld: fix formatting of forwards to unions and enums Nick Alcock
2020-12-30 4:14 ` [PATCH 00/13] CTF dumper improvements, a lookup testsuite, and bugfixes Alan Modra
2020-12-31 13:00 ` Nick Alcock
2021-01-02 4:55 ` Alan Modra
2021-01-05 15:18 ` Nick Alcock
2021-01-05 15:53 ` H.J. Lu
2021-01-05 17:13 ` Nick Alcock
2021-01-05 18:52 ` H.J. Lu
2021-01-05 19:05 ` Nick Alcock [this message]
2021-01-05 19:09 ` H.J. Lu
2021-01-05 19:32 ` Nick Alcock
2021-01-05 19:56 ` 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=87a6tnnr0o.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=weimin.pan@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).