public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Segher Boessenkool <segher@kernel.crashing.org>,
	Jeff Law <law@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gdbinit: add a new command and fix one
Date: Thu, 30 May 2019 08:06:00 -0000	[thread overview]
Message-ID: <551ffab8-898c-f87a-b3ce-ab0986258059@suse.cz> (raw)
In-Reply-To: <20190529181836.GT31586@gate.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

On 5/29/19 8:18 PM, Segher Boessenkool wrote:
> On Wed, May 29, 2019 at 10:14:58AM -0600, Jeff Law wrote:
>> On 5/29/19 3:46 AM, Martin Liška wrote:
>>> Hi.
>>>
>>> The patch is about a small change in .gdbinit file.
>>>
>>> Ready for trunk?
>>> Martin
>>>
>>> gcc/ChangeLog:
>>>
>>> 2019-05-29  Martin Liska  <mliska@suse.cz>
>>>
>>> 	* gdbinit.in: Fix 'ptc' command.  Add tt
>>> 	that prints TREE_TYPE($).
>>> ---
>>>  gcc/gdbinit.in | 10 +++++++++-
>>>  1 file changed, 9 insertions(+), 1 deletion(-)
> 
> There already *is* a "tt" command. 

Oops. I'm renaming that to trt and I'm going to install that.

Martin

> Not that that one is likely very
> useful for debugging GCC, but still...  Please check before overriding
> commands.
> 
> 
> Segher
> 


[-- Attachment #2: 0001-gdbinit-add-a-new-command-and-fix-one.patch --]
[-- Type: text/x-patch, Size: 963 bytes --]

From 5e49f23ecedcc5278f14278a6bccd6d003b5cc60 Mon Sep 17 00:00:00 2001
From: Martin Liska <mliska@suse.cz>
Date: Wed, 29 May 2019 11:45:07 +0200
Subject: [PATCH] gdbinit: add a new command and fix one

gcc/ChangeLog:

2019-05-29  Martin Liska  <mliska@suse.cz>

	* gdbinit.in: Fix 'ptc' command.  Add trt
	that prints TREE_TYPE($).
---
 gcc/gdbinit.in | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/gcc/gdbinit.in b/gcc/gdbinit.in
index e16c3c8ef87..440fd2586f1 100644
--- a/gcc/gdbinit.in
+++ b/gcc/gdbinit.in
@@ -113,7 +113,7 @@ Works only when an inferior is executing.
 end
 
 define ptc
-output (enum tree_code) $.common.code
+output (enum tree_code) $.base.code
 echo \n
 end
 
@@ -201,6 +201,14 @@ document pcfun
 Print current function.
 end
 
+define trt
+print ($.typed.type)
+end
+
+document trt
+Print TREE_TYPE of the tree node that is $
+end
+
 define break-on-diagnostic
 break diagnostic_show_locus
 end
-- 
2.21.0


      reply	other threads:[~2019-05-30  7:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29  9:54 Martin Liška
2019-05-29 16:20 ` Jeff Law
2019-05-29 18:27   ` Segher Boessenkool
2019-05-30  8:06     ` Martin Liška [this message]

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=551ffab8-898c-f87a-b3ce-ab0986258059@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=segher@kernel.crashing.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).