From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/9] Use htab_up in more places
Date: Thu, 17 Sep 2020 11:58:39 -0600 [thread overview]
Message-ID: <878sd870a8.fsf@tromey.com> (raw)
In-Reply-To: <20200718172915.6811-1-tom@tromey.com> (Tom Tromey's message of "Sat, 18 Jul 2020 11:29:06 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> This series changes various spots in gdb to use htab_up rather than
Tom> explicitly managing the hash table. Not every spot can be changed,
Tom> but many can; and in several cases this results in a code
Tom> simplification.
I'm checking this in now.
Tom
prev parent reply other threads:[~2020-09-17 17:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 17:29 Tom Tromey
2020-07-18 17:29 ` [PATCH 1/9] Use htab_up in auto-load.c Tom Tromey
2020-07-20 1:38 ` Simon Marchi
2020-09-17 17:48 ` Tom Tromey
2020-07-18 17:29 ` [PATCH 2/9] Use htab_up in breakpoint.c Tom Tromey
2020-07-18 17:29 ` [PATCH 3/9] Use htab_up in completion_tracker Tom Tromey
2020-07-18 17:29 ` [PATCH 4/9] Use htab_up in filename_seen_cache Tom Tromey
2020-07-20 1:41 ` Simon Marchi
2020-07-18 17:29 ` [PATCH 5/9] Use htab_up in linespec.c Tom Tromey
2020-07-20 1:47 ` Simon Marchi
2020-07-21 0:55 ` Tom Tromey
2020-07-18 17:29 ` [PATCH 6/9] Use htab_up in target-descriptions.c Tom Tromey
2020-07-18 17:29 ` [PATCH 7/9] Use htab_up in typedef_hash_table Tom Tromey
2020-07-18 17:29 ` [PATCH 8/9] Use htab_up in type copying Tom Tromey
2020-09-18 17:32 ` Andrew Burgess
2020-09-18 18:03 ` Tom Tromey
2020-09-18 18:20 ` Andrew Burgess
2020-07-18 17:29 ` [PATCH 9/9] Use htab_up in dwarf2/read.c Tom Tromey
2020-09-17 17:58 ` Tom Tromey [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=878sd870a8.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.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).