From: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: Joel Brobecker <brobecker@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: two agent expression nits (one line each)
Date: Tue, 03 Feb 2015 21:58:00 -0000 [thread overview]
Message-ID: <18513.1423000644@usendtaylorx2l> (raw)
In-Reply-To: <20141220171955.GG12884@adacore.com>
Joel Brobecker <brobecker@adacore.com> wrote:
> Hi David,
[...]
> Since you understand what should be done, would you mind sending
> a patch in for Stan to review?
>
> --
> Joel
Joel,
Sorry for the delay. Here's the patch. Also, I haven't forgotten that
I owe you an updated patch for bad structure offsets. And I have some
others in the queue to finish up and post, as well.
Stan,
Here's the ChangeLog entries:
gdb:
2015-02-03 David Taylor <dtaylor@emc.com>
* common/ax.def (setv): Fix consumed entry in setv DEFOP.
gdb/doc:
2015-02-03 David Taylor <dtaylor@emc.com>
* agentexpr.texi (Bytecode Descriptions): Fix summary line for setv.
and patch, as requested by Joel:
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 351ccdd..0118d7d 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2015-02-03 David Taylor <dtaylor@emc.com>
+
+ * common/ax.def (setv): Fix consumed entry in setv DEFOP.
+
2015-02-02 Joel Brobecker <brobecker@adacore.com>
* dwarf2loc.c (dwarf2_evaluate_property): Add i18n marker.
diff --git a/gdb/common/ax.def b/gdb/common/ax.def
index 8b27725..27c97cc 100644
--- a/gdb/common/ax.def
+++ b/gdb/common/ax.def
@@ -83,7 +83,7 @@ DEFOP (pop, 0, 0, 1, 0, 0x29)
DEFOP (zero_ext, 1, 0, 1, 1, 0x2a)
DEFOP (swap, 0, 0, 2, 2, 0x2b)
DEFOP (getv, 2, 0, 0, 1, 0x2c)
-DEFOP (setv, 2, 0, 0, 1, 0x2d)
+DEFOP (setv, 2, 0, 1, 1, 0x2d)
DEFOP (tracev, 2, 0, 0, 1, 0x2e)
DEFOP (tracenz, 0, 0, 2, 0, 0x2f)
DEFOP (trace16, 2, 0, 1, 1, 0x30)
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 9c12d9a..34fee48 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2015-02-03 David Taylor <dtaylor@emc.com>
+
+ * agentexpr.texi (Bytecode Descriptions): Fix summary line for setv.
+
2015-01-31 Gary Benson <gbenson@redhat.com>
Doug Evans <dje@google.com>
diff --git a/gdb/doc/agentexpr.texi b/gdb/doc/agentexpr.texi
index 788de1c..297cd5e 100644
--- a/gdb/doc/agentexpr.texi
+++ b/gdb/doc/agentexpr.texi
@@ -461,7 +461,7 @@ alignment within the bytecode stream; thus, on machines where fetching a
16-bit on an unaligned address raises an exception, you should fetch the
register number one byte at a time.
-@item @code{setv} (0x2d) @var{n}: @result{} @var{v}
+@item @code{setv} (0x2d) @var{n}: @var{v} @result{} @var{v}
Set trace state variable number @var{n} to the value found on the top
of the stack. The stack is unchanged, so that the value is readily
available if the assignment is part of a larger expression. The
next prev parent reply other threads:[~2015-02-03 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 17:54 David Taylor
2014-11-23 3:27 ` Joel Brobecker
2014-12-02 20:45 ` Stan Shebs
2014-12-13 13:44 ` Joel Brobecker
2014-12-15 15:41 ` David Taylor
2014-12-20 17:19 ` Joel Brobecker
2015-02-03 21:58 ` David Taylor [this message]
2015-02-11 7:49 ` Joel Brobecker
2015-02-11 17:28 ` Stan Shebs
2015-02-13 19:21 ` David Taylor
2015-02-20 3:05 ` pushed (master+branch): " Joel Brobecker
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=18513.1423000644@usendtaylorx2l \
--to=dtaylor@usendtaylorx2l.lss.emc.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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).