From: Richard Biener <richard.guenther@gmail.com>
To: Roger Sayle <roger@nextmovesoftware.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Synchronize include/ctf.h with upstream binutils/libctf.
Date: Fri, 28 Apr 2023 08:16:11 +0200 [thread overview]
Message-ID: <CAFiYyc3x=GRd7Vk7b=YGwAkHJzUTg0cJWDNC3UdDobPXx0qv4w@mail.gmail.com> (raw)
In-Reply-To: <002001d9791b$0d55b960$28012c20$@nextmovesoftware.com>
On Thu, Apr 27, 2023 at 5:15 PM Roger Sayle <roger@nextmovesoftware.com> wrote:
>
>
> This patch updates include/ctf.h to match the current libctf version in
> binutils' include/. I recently attempted to build a uber tree (following
> some notes that are so old they used CVS) and noticed that binutils won't
> build with GCC's top-level include, due to CTF_F_IDXSORTED not being
> defined in ctf.h. There was also a discrepancy with ansidecl.h but
> I'm unsure how (best) to resolve that issue.
>
> This patch was tested on x86_64-pc-linux-gnu with a make bootstrap and
> make -k check, both with and without --target_board=unix{-m32}, with
> no new failures, to confirm that the usage of ctf.h in ctfout.cc and
> dwarf2ctf.cc is compatible with the new version. Ok for mainline?
OK.
>
> 2023-04-27 Roger Sayle <roger@nextmovesoftware.com>
>
> include/ChangeLog
> * ctf.h: Import latest version from binutils/libctf.
>
>
> Thanks in advance,
> Roger
> --
>
prev parent reply other threads:[~2023-04-28 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 15:15 Roger Sayle
2023-04-28 6:16 ` Richard Biener [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='CAFiYyc3x=GRd7Vk7b=YGwAkHJzUTg0cJWDNC3UdDobPXx0qv4w@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=roger@nextmovesoftware.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).