This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 2/2] gdbinit.in: fix wrong reference to function argument


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]