From: Eli Zaretskii <eliz@gnu.org>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] btrace: indicate speculative execution
Date: Thu, 06 Aug 2015 14:46:00 -0000 [thread overview]
Message-ID: <83k2t8scg0.fsf@gnu.org> (raw)
In-Reply-To: <1438867238-28224-1-git-send-email-markus.t.metzger@intel.com>
> 2015-08-06 Markus Metzger <markus.t.metzger@intel.com>
>
> * btrace.c (btrace_compute_ftrace_bts): Clear insn flags.
> (pt_btrace_insn_flags): New.
> (ftrace_add_pt): Call pt_btrace_insn_flags.
> * btrace.h (btrace_insn_flag): New.
> (btrace_insn) <flags>: New.
> * record-btrace.c (btrace_insn_history): Print insn prefix.
> * NEWS: Announce it.
>
> doc/
> * gdb.texinfo (Process Record and Replay): Document it.
doc/ has a separate ChangeLog file, so you cannot say just "Document
it." and hope people will somehow read that right after the main log
entry.
> +Speculatively executed instructions are prefixed with @code{?}. This
Please use @samp here, not code, so that the question mark is quoted
in the printed manual as well.
The documentation parts are OK with those changes.
Thanks.
next prev parent reply other threads:[~2015-08-06 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 13:20 Markus Metzger
2015-08-06 14:46 ` Eli Zaretskii [this message]
2015-08-06 18:18 ` Pedro Alves
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=83k2t8scg0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.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