From: Andrew Cagney <cagney@gnu.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
gdb-patches@sources.redhat.com, cagney <cagney@redhat.com>
Subject: Re: [RFA] mips 32/64 register/stack fix
Date: Fri, 30 Apr 2004 00:40:00 -0000 [thread overview]
Message-ID: <4091A06A.4030803@gnu.org> (raw)
In-Reply-To: <4091754E.4010001@gnu.org>
>> Andrew Cagney wrote:
>>
>>> See daniel's follow up:
>>
>>
>>
>> OK, well, FYI, I ran the testsuite with your revised patch, and it
>> introduced a bunch of new fails in the whole callfuncs family, along
>> with some other completely unexpected places (ptype???).
>
>
> Remember, my patch was an un-tested guess. You'll want to debug it a little, but the theory is sound.
I just tried a variation of it, and it worked for me (mips-elf and
mips64-elf) so as I said the theory is sound. I'm not sure what is
happening, but it sounds like more problems at your end -- the EABI code
is seriously bitrotten :-/
Andrew
prev parent reply other threads:[~2004-04-30 0:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 18:49 Michael Snyder
2004-04-22 19:59 ` Andrew Cagney
2004-04-22 21:29 ` Daniel Jacobowitz
2004-04-22 21:43 ` Michael Snyder
2004-04-22 22:04 ` Andrew Cagney
2004-04-22 22:49 ` Michael Snyder
2004-04-28 21:45 ` Andrew Cagney
2004-04-29 3:12 ` Daniel Jacobowitz
2004-04-29 13:40 ` Andrew Cagney
2004-04-29 14:34 ` Daniel Jacobowitz
2004-04-29 18:32 ` [commit] mips_isa_regsize, mips_abi_regsize; Was: " Andrew Cagney
2004-04-29 19:45 ` [commit] compute abi regsize; Was: Andrew Cagney
2004-04-29 17:58 ` [RFA] mips 32/64 register/stack fix Michael Snyder
2004-04-29 19:49 ` Andrew Cagney
2004-04-29 21:15 ` Michael Snyder
2004-04-29 21:36 ` Andrew Cagney
2004-04-30 0:40 ` Andrew Cagney [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=4091A06A.4030803@gnu.org \
--to=cagney@gnu.org \
--cc=cagney@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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