public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [[PATCH V9] 7/7] libiberty: copy over .BTF section when using LTO
Date: Mon, 21 Jun 2021 15:53:58 +0200	[thread overview]
Message-ID: <CAFiYyc3RNgPNF08X8tdyLYgg7FDr7ZDt_9T85UQQociqouKucA@mail.gmail.com> (raw)
In-Reply-To: <20210531165802.5686-8-jose.marchesi@oracle.com>

On Mon, May 31, 2021 at 7:19 PM Jose E. Marchesi via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> libiberty/ChangeLog:

OK.  You can apply this separately.

I still believe LTO support is kind-of broken, but well ;)

Richard.

>         * 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
>

  reply	other threads:[~2021-06-21 13:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 16:57 [[PATCH V9] 0/7] Support for the CTF and BTF debug formats Jose E. Marchesi
2021-05-31 16:57 ` [[PATCH V9] 1/7] dwarf: add a dwarf2int.h internal interface Jose E. Marchesi
2021-06-22 20:05   ` Jason Merrill
2021-06-24 13:52     ` Jose E. Marchesi
2021-06-24 14:41       ` Jason Merrill
2021-06-24 15:13         ` Jose E. Marchesi
2021-06-24 15:30           ` Jason Merrill
2021-06-25  7:47             ` Richard Biener
2021-05-31 16:57 ` [[PATCH V9] 2/7] dejagnu: modularize gcc-dg-debug-runtest a bit Jose E. Marchesi
2021-06-21 13:47   ` Richard Biener
2021-05-31 16:57 ` [[PATCH V9] 3/7] CTF/BTF debug formats Jose E. Marchesi
2021-06-21 14:10   ` Richard Biener
2021-06-21 15:33     ` Jose E. Marchesi
2021-06-22 20:21   ` Jason Merrill
2021-05-31 16:57 ` [[PATCH V9] 4/7] CTF/BTF testsuites Jose E. Marchesi
2021-06-21 14:02   ` Richard Biener
2021-05-31 16:58 ` [[PATCH V9] 5/7] CTF/BTF documentation Jose E. Marchesi
2021-06-21 13:51   ` Richard Biener
2021-05-31 16:58 ` [[PATCH V9] 6/7] Enable BTF generation in the BPF backend Jose E. Marchesi
2021-06-21 13:53   ` Richard Biener
2021-05-31 16:58 ` [[PATCH V9] 7/7] libiberty: copy over .BTF section when using LTO Jose E. Marchesi
2021-06-21 13:53   ` Richard Biener [this message]
2021-06-14 15:25 ` [[PATCH V9] 0/7] Support for the CTF and BTF debug formats Jose E. Marchesi
2021-06-21 14:01 ` Richard Biener
2021-06-22 15:30   ` Indu Bhagat
2021-06-22 20:22   ` Jason Merrill

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=CAFiYyc3RNgPNF08X8tdyLYgg7FDr7ZDt_9T85UQQociqouKucA@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jose.marchesi@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).