From: Pedro Alves <pedro@palves.net>
To: Lancelot SIX <lancelot.six@amd.com>, gdb-patches@sourceware.org
Cc: lsix@lancelotsix.com
Subject: Re: [PATCH v2 2/2] gdb: Add support for DW_LNS_set_prologue_end in line-table
Date: Thu, 31 Mar 2022 11:17:09 +0100 [thread overview]
Message-ID: <fd6fd7d8-e403-546c-1b10-e015c5705625@palves.net> (raw)
In-Reply-To: <20220330093458.148497-3-lancelot.six@amd.com>
On 2022-03-30 10:34, Lancelot SIX via Gdb-patches wrote:
> This commit proposes to add support for the prologue_end flag in the
> line-program processing.
>
> The processing of this prologue_end flag is made in skip_prologue_sal,
> before it calls gdbarch_skip_prologue_noexcept. The intent is that if
> the compiler gave information on where the prologue ends, we should use
> this information and not try to rely on architecture dependent logic to
> guess it.
There's risk that this runs into compiler bugs, making the experience
worse than if we use the existing code path. I wonder whether we should have
a "maint set foo" knob for this. It's still early in the release cycle,
so I'm OK with waiting a bit to see if we really need it, though. OTOH,
having such a switch regardless would be useful for force-testing the prologue
scanners. Hmm.
>
> The testsuite have been executed using this patch on GNU/Linux x86_64.
> Testcases have been combiled with both gcc/g++ and clang/clang++ since
combiled -> compiled
> GCC does not set the prologue_end marker. No regression have been
> observed with GCC or Clang. Note that when using Clang, this patch
> fixes a failure in gdb.opt/inline-small-func.exp.
Please mention GCC and Clang versions, for the record.
> \f
> diff --git a/gdb/buildsym.h b/gdb/buildsym.h
> index 09c2d563ec9..252bad187dc 100644
> --- a/gdb/buildsym.h
> +++ b/gdb/buildsym.h
> @@ -115,6 +115,7 @@ struct context_stack
> enum linetable_entry_flag : unsigned
> {
> LEF_IS_STMT = 1 << 1,
> + LEF_PROLOGUE_END = 1 << 2,
Please document this enumerator too.
> +
> + const struct symtab_and_line prologue_sal = find_pc_line (start_pc, 0);
> + if (prologue_sal.symtab != nullptr
> + && prologue_sal.symtab->language () != language_asm)
> + {
> + struct linetable *linetable = prologue_sal.symtab->linetable ();
> +
> + auto it = std::lower_bound
> + (linetable->item, linetable->item + linetable->nitems, start_pc,
> + [] (const linetable_entry <e, CORE_ADDR pc) -> bool
> + { return lte.pc < pc; });
> +
> + for (;
> + it < linetable->item + linetable->nitems && it->pc <= end_pc ;
> + it++)
> + if (it->prologue_end)
> + return {it->pc};
> + }
Space/tab mismatch, I guess, since { and } don't align here in the patch.
> +
> + return {};
> +}
Otherwise LGTM.
prev parent reply other threads:[~2022-03-31 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 9:34 [PATCH v2 0/2] Add support for DWARF's prologue_end flag " Lancelot SIX
2022-03-30 9:34 ` [PATCH v2 1/2] gdb/buildsym: Line record use a record flag Lancelot SIX
2022-03-31 9:57 ` Pedro Alves
2022-03-31 10:18 ` Pedro Alves
2022-03-31 10:04 ` Pedro Alves
2022-03-30 9:34 ` [PATCH v2 2/2] gdb: Add support for DW_LNS_set_prologue_end in line-table Lancelot SIX
2022-03-30 12:26 ` Eli Zaretskii
2022-03-30 12:54 ` Lancelot SIX
2022-03-31 10:17 ` Pedro Alves [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=fd6fd7d8-e403-546c-1b10-e015c5705625@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--cc=lsix@lancelotsix.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).