From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] mips32_next_pc overdue cleanup
Date: Thu, 05 Jul 2001 13:51:00 -0000 [thread overview]
Message-ID: <3B44D365.4090403@cygnus.com> (raw)
In-Reply-To: <20010705133346.A15705@nevyn.them.org>
> Thanks. I'm curious.
>
> Is there a CVS repository backed up somewhere which predates 1999, when
> it seems the sourceware copy was created? Makes it a little more
> challenging to do the archaelogy.
There is the archive of some of the old releases that Jason Molenda put
together:
${sources-shadow}/pub/gdb/old-releases/
and Red Hat employees do occasionally act as a remote archive search
engine (back to ~1991). However, prior to that there is little.
>> One thing, it is very easy for a software single step function to be
>> implemented yet never tested - everything supports h/w singlestep
>> now-a-days.
>
>
> Everything except my target :)
>
> The thing is, the (trivial) software single step function wasn't even
> in mips-tdep.c. Only all the complicated support routines for it were.
> The lossage isn't all that surprising, given that these functions had
> no callers.
Perhaphs -Wunused-function should be the next -Werror :-)
Andrew
next prev parent reply other threads:[~2001-07-05 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 11:41 Daniel Jacobowitz
2001-07-04 23:45 ` Eli Zaretskii
2001-07-05 0:00 ` Daniel Jacobowitz
2001-07-05 13:29 ` Andrew Cagney
2001-07-05 13:34 ` Daniel Jacobowitz
2001-07-05 13:51 ` Andrew Cagney [this message]
2001-07-05 14:05 ` Stan Shebs
[not found] ` <3B454B1B.7040506@cygnus.com>
2001-07-05 22:37 ` Daniel Jacobowitz
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=3B44D365.4090403@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dmj+@andrew.cmu.edu \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.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