From: Segher Boessenkool <segher@kernel.crashing.org>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: Andreas Schwab <schwab@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/2] gdbinit.in: fix wrong reference to function argument
Date: Wed, 13 Nov 2019 11:39:00 -0000 [thread overview]
Message-ID: <20191113113239.GE16031@gate.crashing.org> (raw)
In-Reply-To: <1573564637.2541.6@yandex.ru>
On Tue, Nov 12, 2019 at 04:17:17PM +0300, Konstantin Kharlamov wrote:
> On ÐÑ, Ð½Ð¾Ñ 12, 2019 at 14:08, Andreas Schwab <schwab@suse.de>
> wrote:
> >On Nov 12 2019, Konstantin Kharlamov wrote:
> >> I'm definitely missing something. Who are these users, and how can
> >>they
> >> make anything useful of these functions if they don't even pass an
> >> argument?
> >
> >By printing the desired value.
>
> Hah, okay. Well, in this case their workflow now gonna be 2 times
> simpler since they don't have to type in two commands, but only one :)
Do we have to type parentheses now? That more than undoes that gain :-/
> Besides, I suspect, the number of actual users of this gdbinit is
> around zero, otherwise someone would have noticed the warning that gdb
> prints on every usage of these functions while the PATCH 1/2 is not
> applied.
There are users. There are users who have been used to this behaviour
for many many many years.
People just do (say I have an "rtx insn"):
p insn
pr
A new version where you just say
pr insn
would be nice; something that requires
pr(insn)
is less nice.
It would be great if you could come up with something that keeps the
old syntax working as well, especially since many of us have to work
with older versions of the gdbinit as well, for years to come. People
can adjust their work habits of course, but that causes a lot of
friction ;-)
Segher
next prev parent reply other threads:[~2019-11-13 11:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 11:47 [PATCH 0/2] gdbinit.in fixes Konstantin Kharlamov
2019-11-12 11:47 ` [PATCH 1/2] gdbinit.in: call a function with "call", not "set" Konstantin Kharlamov
2019-11-13 11:22 ` Segher Boessenkool
2019-11-13 20:03 ` Jeff Law
2019-11-12 12:07 ` [PATCH 2/2] gdbinit.in: fix wrong reference to function argument Konstantin Kharlamov
2019-11-12 12:57 ` Andreas Schwab
2019-11-12 13:03 ` Konstantin Kharlamov
2019-11-12 13:15 ` Andreas Schwab
2019-11-12 13:27 ` Konstantin Kharlamov
2019-11-12 13:40 ` Andreas Schwab
2019-11-13 11:39 ` Segher Boessenkool [this message]
2019-11-13 15:24 ` Jason Merrill
2019-11-14 7:01 ` Konstantin Kharlamov
2019-11-14 11:57 ` Segher Boessenkool
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=20191113113239.GE16031@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hi-angel@yandex.ru \
--cc=schwab@suse.de \
/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).