Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>,
	       Stan Shebs <stanshebs@earthlink.net>
Cc: gdb@sourceware.org
Subject: Re: FYI: GCC dropped score support
Date: Tue, 07 Oct 2014 08:35:00 -0000	[thread overview]
Message-ID: <5433A5BD.5090603@redhat.com> (raw)
In-Reply-To: <20141007001805.GX27467@adacore.com>

On 10/07/2014 01:18 AM, Joel Brobecker wrote:
>> It seems pretty dead, the company's pages are 404, and the only
>> product I can find that used it was the Mattel HyperScan, introduced in
>> 2006 and discontinued in 2008 - apparently it made PC World's "10 Worst
>> Videogames of All Time" list.

Eh.  :-)

>> Even if the code isn't being used, I think it still costs us, in the
>> sense that we have to think about whether it needs changing, it has
>> to be patchedwhen there are global changes, and so forth.  So I
>> think we should whack it soon as decently possible.  (Of course, the
>> code will actually live on forever, in old releases and repos. :-) )
> 
> Seen under this light, it does make sense!

Agreed, that's my thinking too.  For still-fresh examples, the software
single-step rework work had me stop, think and actually write patches
for IRIX (deprecated_insert_raw_breakpoint).  And then just last week
I failed to notice some code was for Tru64 and wasted time writing
this patch:
  https://sourceware.org/ml/gdb-patches/2014-10/msg00035.html

Thanks,
Pedro Alves


      reply	other threads:[~2014-10-07  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 16:21 Pedro Alves
2014-10-06 23:36 ` Joel Brobecker
2014-10-07  0:10   ` Stan Shebs
2014-10-07  0:18     ` Joel Brobecker
2014-10-07  8:35       ` Pedro Alves [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=5433A5BD.5090603@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=stanshebs@earthlink.net \
    /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