From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <law@redhat.com>
Cc: "Martin Liška" <mliska@suse.cz>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gdbinit: add a new command and fix one
Date: Wed, 29 May 2019 18:27:00 -0000 [thread overview]
Message-ID: <20190529181836.GT31586@gate.crashing.org> (raw)
In-Reply-To: <7d2e12f5-e866-72d6-31f2-315c36dcc217@redhat.com>
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. Not that that one is likely very
useful for debugging GCC, but still... Please check before overriding
commands.
Segher
next prev parent reply other threads:[~2019-05-29 18:18 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 [this message]
2019-05-30 8:06 ` Martin Liška
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=20190529181836.GT31586@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=mliska@suse.cz \
/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).