From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Richard.Earnshaw@arm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] arm-netbsdelf cross-debugging fixes
Date: Tue, 03 Sep 2002 12:34:00 -0000 [thread overview]
Message-ID: <20020903123446.N12843@dr-evil.shagadelic.org> (raw)
In-Reply-To: <200209031923.g83JN2109855@pc960.cambridge.arm.com>; from rearnsha@cambridge.arm.com on Tue, Sep 03, 2002 at 08:23:01PM +0100
On Tue, Sep 03, 2002 at 08:23:01PM +0100, Richard Earnshaw wrote:
> Hmm, evil thought. If I said 'no' then perhaps you'd have to go
> multi-arch the solib code....
>
> No, couldn't be that mean :-)
I'm happy to try and do that at some point ... but not right now :-)
(I'd like to get this fixed up for 5.3, and won't have much time for
any major GDB projects until after the upcoming Intel Developer Forum,
at the very least...)
> > * Split a 26-bit R15 into PC and a 32-bit-format PSR.
> >
> > * Take a PC and a 32-bit-format PSR and combine them back
> > into a 26-bit R15.
>
> This is going to conflict horribly with my WIP for using cooked registers.
> Is there any chance it can be separated out, or made less invasive?
I can put it in armnbsd-tdep.c and make it static, if you want. I only
put it in the generic arm-tdep.c because it seemed like a function of
general utility.
Would that be okay?
> Yep, that would be a good move, but it would be easier to say yes if it
> were a separate patch.
Ok, I'll move the 26bit_r15 stuff into a different file, and submit this
patch again separately.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2002-09-03 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 16:58 Jason R Thorpe
2002-09-02 12:56 ` Andrew Cagney
2002-09-03 12:23 ` Richard Earnshaw
2002-09-03 12:34 ` Jason R Thorpe [this message]
2002-09-04 4:10 ` Richard Earnshaw
2002-09-03 15:40 ` Jason R Thorpe
2002-09-04 2:56 ` Richard Earnshaw
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=20020903123446.N12843@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=Richard.Earnshaw@arm.com \
--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