This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'
- From: Mike Stump <mikestump at comcast dot net>
- To: Michael Eager <eager at eagerm dot com>
- Cc: Chen Gang <gang dot chen dot 5i5j at gmail dot com>, Jeff Law <law at redhat dot com>, davem at redhat dot com, gcc-patches List <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 24 Sep 2014 08:37:01 -0700
- Subject: Re: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'
- Authentication-results: sourceware.org; auth=none
- References: <53B9246A dot 5090408 at gmail dot com> <53EB7FE3 dot 40406 at eagerm dot com> <53EC1264 dot 2080205 at gmail dot com> <540C7703 dot 7090303 at gmail dot com> <540D1363 dot 10909 at gmail dot com> <540DCB1B dot 40901 at gmail dot com> <54154907 dot 2000007 at gmail dot com> <541656FE dot 8020008 at eagerm dot com> <541668CF dot 5080206 at gmail dot com> <54170603 dot 8090607 at eagerm dot com> <54176DCF dot 403 at gmail dot com> <54182E13 dot 1090006 at eagerm dot com> <541DA2A0 dot 5040200 at gmail dot com> <541DABEC dot 7090705 at eagerm dot com> <541DAE2B dot 8050104 at gmail dot com> <541E6F2F dot 7080101 at gmail dot com> <541E8A04 dot 7060208 at gmail dot com> <541EAC71 dot 2090403 at gmail dot com> <541F1459 dot 8090003 at eagerm dot com> <541FA13E dot 2040003 at gmail dot com> <542035EC dot 6000106 at eagerm dot com> <5420469C dot 2030600 at gmail dot com> <54205777 dot 8030506 at eagerm dot com> <5420D55E dot 90605 at gmail dot com> <54219F49 dot 3090508 at gmail dot com> <54221C79 dot 5090206 at gmail dot com> <5422D5D0 dot 4070604 at gmail dot com> <5422E30C dot 2040508 at eagerm dot com>
On Sep 24, 2014, at 8:28 AM, Michael Eager <eager@eagerm.com> wrote:
>> After check the current result log, I find many remote target test
>> related sentences, do we have to process it?
>>
>> e.g. "Download to microblaze-xilinx-gdb failed, couldn't execute "rcp": no such file or directory."
>
> The test suite uses rcp to transfer files to or from the target,
> either to provide input to a test case or to check the output.
> Most Linux systems do not install rcp, since it is a security risk.
To clarify:
if {[board_info $desthost exists rcp_prog]} {
set RCP [board_info $desthost rcp_prog]
} else {
set RCP rcp
}
So, if you set rcp_prog to something else, you should be able to avoid rsh if you want. Most people use ssh now-a-days. You will want it set up to not require a password for testing.