From: Richard Biener <richard.guenther@gmail.com>
To: Indu Bhagat <indu.bhagat@oracle.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/3] Fix PR debug/105089
Date: Fri, 8 Apr 2022 08:37:48 +0200 [thread overview]
Message-ID: <CAFiYyc1Vqt6QT+rk46F1dDgxwZDdvRPK2JgmfOF=2bbsffsH9w@mail.gmail.com> (raw)
In-Reply-To: <787914a7-b950-cbd2-5c72-bbef4510ef67@oracle.com>
On Thu, Apr 7, 2022 at 9:42 PM Indu Bhagat via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> ping
The series is OK
> On 3/30/22 4:31 PM, Indu Bhagat wrote:
> > Hello,
> >
> > This patch set fixes PR debug/105089.
> >
> > [PS: The first patch in the series "ctfc: get rid of the static variable in
> > ctf_list_add_ctf_vars" is unrelated to the PR and is combined here only for
> > ease of review.]
> >
> > As noted in the PR debug/105089, gcc is emitting two CTF variable records
> > where it sees an extern variable with declaration and definition in the same
> > compilation unit.
> >
> > The CTF format format does not distinguish between the non-defining decl vs.
> > the defining decl, so the correct behaviour wrt the compiler generating the
> > type for such extern variables is to simply emit the type of the defining
> > declaration.
> >
> > Testing Notes:
> > -- bootstrapped and reg tested on x86_64 and aarch64
> > -- built binutils package with -gctf (with CTF-capable linker) on x86_64, no
> > CTF errors reported.
> >
> > Thanks,
> >
> > Indu Bhagat (3):
> > ctfc: get rid of the static variable in ctf_list_add_ctf_vars ()
> > CTF for extern variable fix [PR105089]
> > Refactor and update CTF testcases [PR105089]
> >
> > gcc/ctfc.cc | 62 ++++++++++++++++++-
> > gcc/ctfc.h | 8 ++-
> > gcc/ctfout.cc | 28 ++++++---
> > gcc/dwarf2ctf.cc | 18 +++++-
> > gcc/testsuite/gcc.dg/debug/ctf/ctf-array-2.c | 22 +++----
> > gcc/testsuite/gcc.dg/debug/ctf/ctf-array-5.c | 17 +++++
> > .../gcc.dg/debug/ctf/ctf-variables-3.c | 22 +++++++
> > 7 files changed, 147 insertions(+), 30 deletions(-)
> > create mode 100644 gcc/testsuite/gcc.dg/debug/ctf/ctf-array-5.c
> > create mode 100644 gcc/testsuite/gcc.dg/debug/ctf/ctf-variables-3.c
> >
>
prev parent reply other threads:[~2022-04-08 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 23:31 Indu Bhagat
2022-03-30 23:31 ` [PATCH 1/3] ctfc: get rid of the static variable in ctf_list_add_ctf_vars () Indu Bhagat
2022-03-30 23:31 ` [PATCH 2/3] CTF for extern variable fix [PR105089] Indu Bhagat
2022-03-30 23:31 ` [PATCH 3/3] Refactor and update CTF testcases [PR105089] Indu Bhagat
2022-04-07 20:04 ` [PATCH 0/3] Fix PR debug/105089 Indu Bhagat
2022-04-08 6:37 ` 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='CAFiYyc1Vqt6QT+rk46F1dDgxwZDdvRPK2JgmfOF=2bbsffsH9w@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=indu.bhagat@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).