From: Richard Sandiford <richard@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Make all four mipsisa* simulators support mipsisa{32,64}{,r2}
Date: Thu, 28 Jun 2007 09:41:00 -0000 [thread overview]
Message-ID: <87tzsslibc.fsf@firetop.home> (raw)
In-Reply-To: <20070626185001.GG3700@adacore.com> (Joel Brobecker's message of "Tue, 26 Jun 2007 14:50:01 -0400")
Joel Brobecker <brobecker@adacore.com> writes:
>> Although most mipsisa* GNU tools support all four of MIPS32, MIP32r2,
>> MIPS64 and MIPS64r2, the gdb simulator doesn't. So while the gcc
>> configurations build multilibs for all four targets, it usually isn't
>> possible to test them all using one configuration's simulator.
>
> [..]
>
>> sim/mips/
>> * configure.ac (sim_mipsisa3264_configs): New variable.
>> (mipsis32*-*-, mipsisa32r2*-*-*, mips64*-*-*, mips64r2*-*-*): Make
>> every configuration support all four targets, using the triplet to
>> determine the default.
>> * configure: Regenerate.
>
> I think this deserves an entry in gdb/NEWS.
Events have proven otherwise. I can't have tested the patch as well
as I'd thought: I think the only mips32 code I tested on mipsisa64
must have been soft-float.
It turns out that mips.igen's implementation of ldc1 does not work when
WITH_TARGET_WORD_SIZE==64. The different W_T_W_S probably causes other
(perhaps more subtle) problems in the same line, so I've decided to
revert the patch. I'd still like to make the change in principle,
but it clearly needs more work, and I don't have time for that at
the moment.
Sorry for screwing this up.
Richard
prev parent reply other threads:[~2007-06-28 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 18:17 Richard Sandiford
2007-06-26 13:14 ` Thiemo Seufer
2007-06-26 19:11 ` Joel Brobecker
2007-06-28 9:41 ` Richard Sandiford [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=87tzsslibc.fsf@firetop.home \
--to=richard@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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