From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 0/6] Handle split functions in call site chains
Date: Mon, 28 Mar 2022 13:54:42 -0600 [thread overview]
Message-ID: <878rst26pp.fsf@tromey.com> (raw)
In-Reply-To: <87tucilu0x.fsf@tromey.com> (Tom Tromey via Gdb-patches's message of "Mon, 28 Feb 2022 11:34:38 -0700")
Tom> This series fixes a bug in DW_OP_entry_value handling.
Tom> A large customer program that is compiled with optimization has a
Tom> function that is split into hot and cold parts. The DWARF uses
Tom> DW_AT_ranges to represent this.
Tom> [...]
Tom> Patch #4 could use an extra examination, both because I convert
Tom> explicit state management to recursion (IMO ok because these call
Tom> chains tend to be short); but also because I think I found a bug in
Tom> the current code.
> I think at this point I will delay this until after the 12.1 branch is
> made. Then I will probably check it in.
I'm checking this in now. I've rebased it, which only required minor
changes. I've also regression tested it on x86-64 Fedora 34.
Tom
prev parent reply other threads:[~2022-03-28 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 22:04 Tom Tromey
2021-12-01 22:04 ` [PATCH 1/6] Change call_site_target to use custom type and enum Tom Tromey
2021-12-01 22:04 ` [PATCH 2/6] Make call_site_target members private Tom Tromey
2021-12-01 22:04 ` [PATCH 3/6] Constify chain_candidate Tom Tromey
2021-12-01 22:04 ` [PATCH 4/6] Change call_site_find_chain_1 to work recursively Tom Tromey
2021-12-01 22:04 ` [PATCH 5/6] Change call_site_target to iterate over addresses Tom Tromey
2021-12-01 22:04 ` [PATCH 6/6] Handle multiple addresses in call_site_target Tom Tromey
2022-02-28 18:34 ` [PATCH 0/6] Handle split functions in call site chains Tom Tromey
2022-03-28 19:54 ` Tom Tromey [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=878rst26pp.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.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).