From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Find tailcall frames before inline frames
Date: Tue, 03 Mar 2020 21:45:00 -0000 [thread overview]
Message-ID: <87sgip6rk9.fsf@tromey.com> (raw)
In-Reply-To: <20200220155820.22809-1-tromey@adacore.com> (Tom Tromey's message of "Thu, 20 Feb 2020 08:58:20 -0700")
Tom> gdb/ChangeLog
Tom> 2020-02-20 Tom Tromey <tromey@adacore.com>
Tom> * dwarf2/frame.c (struct dwarf2_frame_cache)
Tom> <checked_tailcall_bottom, entry_cfa_sp_offset,
Tom> entry_cfa_sp_offset_p> : Remove members.
Tom> (dwarf2_frame_cache): Call dwarf2_tailcall_sniffer_first.
Tom> (dwarf2_frame_prev_register): Don't call
Tom> dwarf2_tailcall_sniffer_first.
Tom> (dwarf2_append_unwinders): Don't append tailcall unwinder.
Tom> * frame-unwind.c (add_unwinder): New fuction.
Tom> (frame_unwind_init): Use it. Add tailcall unwinder.
I'm going to check this in now.
Tom
next prev parent reply other threads:[~2020-03-03 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 15:58 Tom Tromey
2020-03-03 21:45 ` Tom Tromey [this message]
2020-03-05 10:21 ` Luis Machado
2020-03-05 16:56 ` Tom Tromey
2020-03-09 17:55 ` Luis Machado
2020-03-12 21:34 ` Tom Tromey
2020-03-13 13:31 ` Luis Machado
2020-03-24 21:24 ` Luis Machado
2020-03-26 1:59 ` Tom Tromey
2020-03-26 2:47 ` Luis Machado
2020-06-18 18:25 ` Andrew Burgess
2020-06-18 21:07 ` Tom Tromey
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=87sgip6rk9.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).