From: David Faust <david.faust@oracle.com>
To: gcc-patches@gcc.gnu.org
Cc: indu.bhagat@oracle.com, jose.marchesi@oracle.com
Subject: [PATCH 0/3] btf: fix BTF for extern items [PR106773]
Date: Wed, 7 Dec 2022 12:57:31 -0800 [thread overview]
Message-ID: <20221207205734.9287-1-david.faust@oracle.com> (raw)
Hi,
This series fixes the issues reported in target/PR106773. I decided to
split it into three commits, as there are ultimately three distinct
issues and fixes. See each patch for details.
Tested on bpf-unknown-none and x86_64-linux-gnu, no known regressions.
OK to push?
Thanks.
David Faust (3):
btf: add 'extern' linkage for variables [PR106773]
btf: fix 'extern const void' variables [PR106773]
btf: correct generation for extern funcs [PR106773]
gcc/btfout.cc | 182 +++++++++++++-----
.../gcc.dg/debug/btf/btf-datasec-2.c | 28 +++
.../gcc.dg/debug/btf/btf-function-6.c | 19 ++
gcc/testsuite/gcc.dg/debug/btf/btf-pr106773.c | 25 +++
.../gcc.dg/debug/btf/btf-variables-4.c | 24 +++
include/btf.h | 11 +-
6 files changed, 237 insertions(+), 52 deletions(-)
create mode 100644 gcc/testsuite/gcc.dg/debug/btf/btf-datasec-2.c
create mode 100644 gcc/testsuite/gcc.dg/debug/btf/btf-function-6.c
create mode 100644 gcc/testsuite/gcc.dg/debug/btf/btf-pr106773.c
create mode 100644 gcc/testsuite/gcc.dg/debug/btf/btf-variables-4.c
--
2.38.1
next reply other threads:[~2022-12-07 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 20:57 David Faust [this message]
2022-12-07 20:57 ` [PATCH 1/3] btf: add 'extern' linkage for variables [PR106773] David Faust
2022-12-09 6:55 ` Indu Bhagat
2022-12-12 20:47 ` David Faust
2022-12-13 6:15 ` Indu Bhagat
2022-12-07 20:57 ` [PATCH 2/3] btf: fix 'extern const void' " David Faust
2022-12-09 7:34 ` Indu Bhagat
2022-12-12 20:59 ` David Faust
2022-12-13 6:11 ` Indu Bhagat
2022-12-07 20:57 ` [PATCH 3/3] btf: correct generation for extern funcs [PR106773] David Faust
2022-12-09 7:36 ` Indu Bhagat
2022-12-12 20:31 ` David Faust
2022-12-13 6:12 ` Indu Bhagat
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=20221207205734.9287-1-david.faust@oracle.com \
--to=david.faust@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=indu.bhagat@oracle.com \
--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).