Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Alan Hayward <Alan.Hayward@arm.com>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Remove MAX_REGISTER_SIZE from sol-thread.c
Date: Wed, 01 Mar 2017 17:24:00 -0000	[thread overview]
Message-ID: <20170301172400.GM7871@redhat.com> (raw)
In-Reply-To: <86d1e0rkam.fsf@gmail.com>

Hi -

> 
> > Regcache calls in sol-thread.c are bogus and do nothing.
> > The code in between will not change or update regcache.
> > Removed.
> 
> If we remove code, we need to figure out why the code was there.
> The code is about to remove was added by
> 
> commit 7cdd6cac82faad2083029b2ac014d44d869f76c0
> Author: Frank Ch. Eigler <fche@redhat.com>
> Date:   Thu Apr 2 18:54:04 1998 +0000
> 
>     * Fixes for PR 14571.
> [...]

Heh, sorry, my recollection of this after 19 years is totally blank.

Interestingly, PR14571 must refer to the pre-bugzilla bug tracker
system.  There was one on sourceware.org, but its web interface is no
longer operating, and scraps of the database files that are still
archived seem not to go up to 14571.  Likewise, no google hits.

So I'm at a loss, can't find orginal supporting data either, and
that's a bummer.

- FChE


  reply	other threads:[~2017-03-01 17:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 10:12 Alan Hayward
2017-03-01 17:14 ` Yao Qi
2017-03-01 17:24   ` Frank Ch. Eigler [this message]
2017-03-01 18:35     ` Alan Hayward
2017-03-01 21:15       ` Yao Qi
     [not found]     ` <20170301211039.aagkvmdlkqn7jf5u@localhost>
2017-03-01 21:59       ` Frank Ch. Eigler
2017-03-02  9:52         ` Yao Qi

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=20170301172400.GM7871@redhat.com \
    --to=fche@redhat.com \
    --cc=Alan.Hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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