From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [commit] [patch 04/12] entryval#3: Virtual tail call frames
Date: Sun, 09 Oct 2011 19:27:00 -0000 [thread overview]
Message-ID: <20111009192712.GD12651@host1.jankratochvil.net> (raw)
In-Reply-To: <20110929194925.GE26579@host1.jankratochvil.net>
On Thu, 29 Sep 2011 21:49:25 +0200, Jan Kratochvil wrote:
> gdb/
> 2011-09-13 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Recognize virtual tail call frames.
> * Makefile.in (SFILES): Add dwarf2-frame-tailcall.c.
> (HFILES_NO_SRCDIR): Add dwarf2-frame-tailcall.h.
> (COMMON_OBS): Add dwarf2-frame-tailcall.o.
> * dwarf2-frame-tailcall.c: New file.
> * dwarf2-frame-tailcall.h: New file.
> * dwarf2-frame.c: Include dwarf2-frame-tailcall.h.
> (execute_cfa_program): New function comment. Return INSN_PTR. Reset
> REGS.PREV only after CIE execution.
> (struct dwarf2_frame_cache): New field tailcall_cache.
> (dwarf2_frame_cache): New variables entry_pc, entry_cfa_sp_offset,
> entry_cfa_sp_offset_p and instr. Execute FDE instructions in two
> parts, try to find entry_cfa_sp_offset. Call
> dwarf2_tailcall_sniffer_first.
> (dwarf2_frame_prev_register): Call dwarf2_tailcall_prev_register_first
> when appropriate.
> (dwarf2_frame_dealloc_cache): New function.
> (dwarf2_frame_sniffer): Preinitialize cache by dwarf2_frame_cache.
> (dwarf2_frame_unwind): Install dwarf2_frame_dealloc_cache.
> (dwarf2_signal_frame_unwind): Do not install dwarf2_frame_dealloc_cache.
> (dwarf2_append_unwinders): Add dwarf2_tailcall_frame_unwind.
> (dwarf2_frame_cfa): Support also dwarf2_tailcall_frame_unwind.
> * dwarf2loc.c (func_addr_to_tail_call_list)
> (tailcall_dump, call_sitep, VEC (call_sitep), chain_candidate)
> (call_site_find_chain_1, call_site_find_chain): New.
> * dwarf2loc.h (struct call_site_chain): New.
> (call_site_find_chain): New declaration.
> * frame.c (get_frame_address_in_block): Support also TAILCALL_FRAME.
> * frame.h (enum frame_type): New entry TAILCALL_FRAME.
> * python/py-frame.c (gdbpy_initialize_frames): Add TAILCALL_FRAME.
> * stack.c (frame_info): Support also TAILCALL_FRAME.
>
> gdb/doc/
> 2011-07-18 Jan Kratochvil <jan.kratochvil@redhat.com>
> Eli Zaretskii <eliz@gnu.org>
>
> Recognize virtual tail call frames.
> * gdb.texinfo (Optimized Code): Add reference to Tail Call Frames.
> (Tail Call Frames): New node.
> (Frames In Python): Add gdb.TAILCALL_FRAME.
>
> gdb/testsuite/
> 2011-07-18 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Recognize virtual tail call frames.
> * gdb.arch/amd64-entry-value.cc (c, a, b, amb_z, amb_y, amb_x, amb)
> (amb_b, amb_a): New.
> (main): Call a and b.
> * gdb.arch/amd64-entry-value.exp (tailcall: breakhere, tailcall: bt)
> (tailcall: p i, tailcall: p j, set $sp0=$sp, up, p $sp0 == $sp, frame 3)
> (p $sp0 + sizeof (void *) == $sp, ambiguous: breakhere, ambiguous: bt):
> New tests.
Checked in:
http://sourceware.org/ml/gdb-cvs/2011-10/msg00059.html
Thanks,
Jan
next prev parent reply other threads:[~2011-10-09 19:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 19:50 Jan Kratochvil
2011-10-09 19:27 ` Jan Kratochvil [this message]
2011-10-09 20:23 ` [commit] " Jan Kratochvil
2011-10-10 13:40 ` doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames) Ulrich Weigand
2011-10-10 13:54 ` Eli Zaretskii
2011-10-10 13:58 ` Ulrich Weigand
2011-10-10 14:58 ` [patch] New test+use texinfo @click - @HAVE_MAKEINFO_CLICK@ [Re: doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames)] Jan Kratochvil
2011-10-10 15:16 ` Pedro Alves
2011-10-10 15:31 ` Jan Kratochvil
2011-10-10 15:51 ` Pedro Alves
2011-10-10 18:47 ` Jan Kratochvil
2011-10-10 19:11 ` Eli Zaretskii
2011-10-10 21:56 ` Pedro Alves
2011-10-10 22:19 ` Andreas Schwab
2011-10-11 23:34 ` Jan Kratochvil
2011-10-12 15:26 ` Pedro Alves
2011-10-12 15:56 ` Jan Kratochvil
2011-10-25 14:35 ` Joel Brobecker
2011-10-25 14:47 ` Jan Kratochvil
2011-10-25 16:09 ` Joel Brobecker
2011-10-10 16:10 ` Eli Zaretskii
2011-10-10 16:15 ` Jan Kratochvil
2011-10-10 16:09 ` Eli Zaretskii
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=20111009192712.GD12651@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.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