Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Luis Machado <luis.machado@linaro.org>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Do we still support DICOS?
Date: Tue, 29 Sep 2020 13:16:25 +0100	[thread overview]
Message-ID: <d5616543-b3b0-a50a-1e6d-d8c39bccef0b@palves.net> (raw)
In-Reply-To: <14e31f08-fc7e-9539-09b9-b8bb8d37513b@linaro.org>

On 9/22/20 8:01 PM, Luis Machado via Gdb wrote:
> Hi,
> 
> In the middle of discussing the usefulness of tracepoints/fast tracepoints (which should be left for another thread potentially), do we still care about DICOS?

Probably not.  I never heard anything again about DICOS ever since the
original port work 12 years ago or some such.  I was under the impression
that Ericsson stopped caring about it not long after.  I'd be surprised if
the port isn't bit rotten by now.

But note that DICOS had nothing to do with tracepoints.

> 
> I see the files are still in the tree, along with sprinkled references here and there. Should we just declare that dead and have the code cleaned up?

No objections from me.

Thanks,
Pedro Alves


  reply	other threads:[~2020-09-29 12:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 19:01 Luis Machado
2020-09-29 12:16 ` Pedro Alves [this message]
2020-12-11  9:34 László Benedek via Gdb
2020-12-11 14:18 ` Simon Marchi via Gdb
2020-12-11 14:25 ` Luis Machado via Gdb
2025-05-30 21:05   ` Simon Marchi via Gdb
2025-06-02  6:47     ` László Benedek via Gdb
2025-06-02  6:57       ` Balázs Samu Fekete via Gdb
2025-06-02  7:32         ` Luis Machado via Gdb
2025-06-17  6:13           ` Balázs Samu Fekete via Gdb
2025-06-18 14:37             ` Simon Marchi via Gdb
2020-12-11 14:25 ` Luis Machado via Gdb

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=d5616543-b3b0-a50a-1e6d-d8c39bccef0b@palves.net \
    --to=pedro@palves.net \
    --cc=gdb@sourceware.org \
    --cc=luis.machado@linaro.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