From: Pedro Alves <palves@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] DEC threads: Simplify updating the thread list
Date: Fri, 03 Oct 2014 09:12:00 -0000 [thread overview]
Message-ID: <542E6864.1010102@redhat.com> (raw)
In-Reply-To: <201410021846.s92IkOVn018154@glazunov.sibelius.xs4all.nl>
On 10/02/2014 07:46 PM, Mark Kettenis wrote:
>> From: Pedro Alves <palves@redhat.com>
>> Date: Thu, 2 Oct 2014 17:21:36 +0100
>>
>> Seems to me that we can simplify DEC thread's
>> target_update_thread_list implementation, avoiding the need to build
>> the array of GDB threads.
>>
>> I have no way to test this.
>
> Given that Alpha True64 support is about to be removed, I don't think
> anyone will care.
Eh, I saw that dec-thread.o was pulled in by config/alpha/alpha-osf3.mh,
and then that is used when configuring for "alpha-osf" host, but somehow
failed to make the OSF->True64 connection. :-P
Thanks,
Pedro Alves
next prev parent reply other threads:[~2014-10-03 9:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 16:21 [PATCH 0/4] remote thread listing: get rid of unnecessary "thread alive?" traffic Pedro Alves
2014-10-02 16:21 ` [PATCH 3/4] remote: get rid of all the T packets when synching the thread list Pedro Alves
2014-10-02 16:21 ` [PATCH 1/4] Merge remote thread listing methods Pedro Alves
2014-10-17 8:57 ` Jiong Wang
2014-10-17 10:17 ` [PATCH] Fix build without libexpat (Re: [PATCH 1/4] Merge remote thread listing methods) Pedro Alves
2014-10-17 10:21 ` Jiong Wang
2014-10-02 16:21 ` [PATCH 2/4] Push pruning old threads down to the target Pedro Alves
2016-12-09 6:38 ` Thomas Schwinge
2014-10-02 16:21 ` [PATCH 4/4] DEC threads: Simplify updating the thread list Pedro Alves
2014-10-02 18:46 ` Mark Kettenis
2014-10-03 9:12 ` Pedro Alves [this message]
2014-10-15 22:01 ` [pushed] Re: [PATCH 0/4] remote thread listing: get rid of unnecessary "thread alive?" traffic Pedro Alves
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=542E6864.1010102@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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