Thanks for tackling this.
Atsushi Nemoto <[EMAIL PROTECTED]> writes:
> On 22 Jul 2006 20:58:16 -0700, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
>> OK, patch is approved, with a ChangeLog entry, and assuming it passes
>> the testsuite.
>
> Thanks, here is a patch with a ChangeLog entry.
>
> I can cross-build gcc and glibc successfully, but unfortunately I can
> not build and run the testsuite natively (in reasonable time) due to
> limited CPU/memory resources on my target platform. Is there good way
> to run testsuite on cross environment?
You can set up DejaGNU's unix.exp to use rsh and rcp. It's usually
a case of creating a board file "foo.exp" like this:
load_generic_config "unix"
process_multilib_options ""
set_board_info hostname "...."
You can use ssh and scp instead by adding:
set_board_info rsh_prog ssh
set_board_info rcp_prog rcp
and then running with "make -k check RUNTESTFLAGS='--target_board foo'".
FWIW, I can run a gcc test run for you on mips64-linux-gnu (and perhaps
glibc too, depending on the time). I should have the results by the weekend.
> +; Since rdhwr always generate a trap for now, it should not be be put
> +; on delay slot. It it was on delay slot, the emulation will be
> +; slower.
Andreas has already commented on this, but the tense sounds wrong too.
Maybe it would be better to have something like:
; Putting rdhwr in a delay slot would make the kernel's emulation
; of it much slower.
right above the "can_delay" line. Whatever you feel is best though.
Richard
