public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibhagat at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/112849] btf: wrong BTF_KIND_DATSEC entries for extern variables without known section
Date: Tue, 05 Dec 2023 22:07:20 +0000	[thread overview]
Message-ID: <bug-112849-4-zHTfXq7jEv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112849-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112849

--- Comment #2 from Indu Bhagat <ibhagat at gcc dot gnu.org> ---
I think its also a good idea to propose a patch to btf.rst upstream to clearly
state something to the like of:

  - What variables have an associated BTF_KIND_DATASEC entry 
  - In "2.2.15 BTF_KIND_DATASEC"
    "struct btf_type" encoding requirement:
    * "name_off": offset to a valid name associated with a variable or
                  one of .data/.bss/.rodata
    --> change to -->
    * "name_off": offset to a valid section name associated with a variable 
                  or one of .data/.bss/.rodata

  parent reply	other threads:[~2023-12-05 22:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 21:12 [Bug debug/112849] New: " david.faust at oracle dot com
2023-12-04 21:14 ` [Bug debug/112849] " david.faust at oracle dot com
2023-12-05 22:07 ` ibhagat at gcc dot gnu.org [this message]
2023-12-05 22:08 ` cvs-commit at gcc dot gnu.org

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=bug-112849-4-zHTfXq7jEv@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).