From: Doug Evans <dje@google.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] change gdbserver to use hashtab: list->table
Date: Sun, 26 Jan 2014 23:01:00 -0000 [thread overview]
Message-ID: <CADPb22Tho32=Pf_v4Gfqm=9Bq5Q6LiZiGM1poCyuRgGfUBuz2g@mail.gmail.com> (raw)
In-Reply-To: <52E3ADB8.60707@codesourcery.com>
On Sat, Jan 25, 2014 at 4:27 AM, Yao Qi <yao@codesourcery.com> wrote:
>> The patch is in 3 parts:
>>
>> 1) rename "list" to "table" throughout,
>> rename member "entry" in some structs to "head" (for consistency)
>>
>> 2) misc. prepatory cleanup, in particular while there are routines
>> to traverse the lists, some code traverses the list itself.
>> These need to be rewritten to always use the provided traversal
>> routines.
>>
>> 3) Add hashtable support.
>
> Where is patch 3/3? I don't see it in archive either.
Last minute second thoughts.
I'm working on a different implementation (which may itself not be the
final story ... baby steps).
next prev parent reply other threads:[~2014-01-26 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 1:12 Doug Evans
2014-01-25 12:29 ` Yao Qi
2014-01-26 1:48 ` Yao Qi
2014-01-26 23:01 ` Doug Evans [this message]
2014-01-29 5:45 ` Doug Evans
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='CADPb22Tho32=Pf_v4Gfqm=9Bq5Q6LiZiGM1poCyuRgGfUBuz2g@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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