From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Markus Metzger <markus.t.metzger@intel.com>,
Pedro Alves <palves@redhat.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [rfc] btrace: change record instruction-history /m
Date: Fri, 14 Aug 2015 17:06:00 -0000 [thread overview]
Message-ID: <CADPb22S36oWzWagvHLHvc4aEnQCG1ddV5f1TbK6ddLY-DEHt2A@mail.gmail.com> (raw)
In-Reply-To: <83bneanfvb.fsf@gnu.org>
On Fri, Aug 14, 2015 at 6:45 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Markus Metzger <markus.t.metzger@intel.com>
>> Cc: gdb-patches@sourceware.org, dje@google.com
>> Date: Fri, 14 Aug 2015 13:37:52 +0200
>>
>> Change record instruction-history /m to use its own simple source interleaving
>> algorithm. The most important part is that instructions are printed in
>> the order in which they were executed.
>
> What does "order in which they were executed" mean with today's
> multi-core and multi-execution unit CPUs?
>
> Thanks.
"multi-core" doesn't enter into the picture here.
The context is a single thread of control.
And "multi-execution unit" doesn't either because
that's just an underlying implementation detail
of the CPU - the program must behave "as if"
each instruction is executed serially
(or as otherwise defined by the ISA).
next prev parent reply other threads:[~2015-08-14 17:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 11:37 Markus Metzger
2015-08-14 13:45 ` Eli Zaretskii
2015-08-14 17:06 ` Doug Evans [this message]
2015-08-14 20:32 ` Eli Zaretskii
2015-08-17 7:16 ` Metzger, Markus T
2015-08-17 15:10 ` Eli Zaretskii
2015-08-18 6:30 ` Metzger, Markus T
2015-08-18 14:22 ` Eli Zaretskii
2015-08-14 17:02 ` Doug Evans
2015-08-14 17:44 ` Doug Evans
2015-08-17 7:23 ` Metzger, Markus T
2015-08-18 14:57 ` Pedro Alves
2015-08-19 14:45 ` Marc Khouzam
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=CADPb22S36oWzWagvHLHvc4aEnQCG1ddV5f1TbK6ddLY-DEHt2A@mail.gmail.com \
--to=dje@google.com \
--cc=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