public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/7] gdb: option completion for 'save gdb-index' command
Date: Mon, 27 Nov 2023 22:20:49 +0000	[thread overview]
Message-ID: <87edgaq1mm.fsf@redhat.com> (raw)
In-Reply-To: <87a5qzf2g8.fsf@tromey.com>

Tom Tromey <tom@tromey.com> writes:

>>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:
>
> Andrew> Add proper support for option completion to the 'save gdb-index'
> Andrew> command.  Update save_gdb_index_command function to make use of the
> Andrew> new option_def data structures for parsing the '-dwarf-5' option.
>
> I thought there was some reason this was difficult... the reason the
> 'palves/filename-options' branch exists (maybe only in Pedro's github).

I've only skimmed that branch, but I think that branch is adding options
that are themselves filenames, e.g. '-option FILENAME', but that's not
the case here.  The '-dwarf-5' is the option, and that's separate from
FILENAME.

We already have two other commands that follow the same pattern as I'm
proposing here 'maint print c-tdesc' and 'compile file', admittedly,
neither of these are likely high usage commands, so maybe they are
broken in some subtle way that has never been spotted ...

... anyway, at least for the basic usage I've tested, everything still
seems fine with this change in place.

>
> However if it works then it seems like a good improvement to me.

Thanks,
Andrew


  reply	other threads:[~2023-11-27 22:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 17:55 [PATCH 0/7] Changes to gdb-index creation Andrew Burgess
2023-11-27 17:55 ` [PATCH 1/7] gdb: allow use of ~ in 'save gdb-index' command Andrew Burgess
2023-11-27 17:55 ` [PATCH 2/7] gdb: option completion for " Andrew Burgess
2023-11-27 18:58   ` Tom Tromey
2023-11-27 22:20     ` Andrew Burgess [this message]
2023-11-27 17:55 ` [PATCH 3/7] gdb/testsuite: small refactor in selftest-support.exp Andrew Burgess
2023-11-27 17:55 ` [PATCH 4/7] gdb: reduce size of generated gdb-index file Andrew Burgess
2023-11-27 17:55 ` [PATCH 5/7] gdb: C++-ify mapped_symtab from dwarf2/index-write.c Andrew Burgess
2023-11-27 19:01   ` Tom Tromey
2023-11-27 22:21     ` Andrew Burgess
2023-11-27 17:56 ` [PATCH 6/7] gdb: generate gdb-index identically regardless of work thread count Andrew Burgess
2023-11-27 17:56 ` [PATCH 7/7] gdb: generate dwarf-5 index identically as worker-thread count changes Andrew Burgess
2023-11-27 19:38 ` [PATCH 0/7] Changes to gdb-index creation Tom Tromey
2023-11-28 10:34   ` Andrew Burgess

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=87edgaq1mm.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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).