public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: gcc-patches@gcc.gnu.org
Subject: [COMMITTED V10 7/7] libiberty: copy over .BTF section when using LTO
Date: Mon, 28 Jun 2021 19:35:23 +0200	[thread overview]
Message-ID: <20210628173523.29350-8-jose.marchesi@oracle.com> (raw)
In-Reply-To: <20210628173523.29350-1-jose.marchesi@oracle.com>

libiberty/ChangeLog:

	* simple-object.c (handle_lto_debug_sections): Copy over .BTF section.
---
 libiberty/simple-object.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/libiberty/simple-object.c b/libiberty/simple-object.c
index 909995dd166..facbf94fd09 100644
--- a/libiberty/simple-object.c
+++ b/libiberty/simple-object.c
@@ -307,6 +307,9 @@ handle_lto_debug_sections (const char *name, int rename)
   /* Copy over .ctf section under the same name if present.  */
   else if (strcmp (name, ".ctf") == 0)
     return strcpy (newname, name);
+  /* Copy over .BTF section under the same name if present.  */
+  else if (strcmp (name, ".BTF") == 0)
+    return strcpy (newname, name);
   free (newname);
   return NULL;
 }
-- 
2.25.0.2.g232378479e


      parent reply	other threads:[~2021-06-28 17:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 17:35 [COMMITTED V10 0/7] Support for the CTF and BTF debug formats Jose E. Marchesi
2021-06-28 17:35 ` [COMMITTED V10 1/7] dwarf: externalize some DWARF internals for needs of CTF/BTF Jose E. Marchesi
2021-06-28 17:35 ` [COMMITTED V10 2/7] dejagnu: modularize gcc-dg-debug-runtest a bit Jose E. Marchesi
2021-06-28 17:35 ` [COMMITTED V10 3/7] CTF/BTF debug formats Jose E. Marchesi
2021-06-28 17:35 ` [COMMITTED V10 4/7] CTF/BTF testsuites Jose E. Marchesi
2021-06-30 11:46   ` Christophe Lyon
2021-06-28 17:35 ` [COMMITTED V10 5/7] CTF/BTF documentation Jose E. Marchesi
2021-06-28 17:35 ` [COMMITTED V10 6/7] Enable BTF generation in the BPF backend Jose E. Marchesi
2021-06-28 17:35 ` Jose E. Marchesi [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=20210628173523.29350-8-jose.marchesi@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=gcc-patches@gcc.gnu.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).