[PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'

Michael Eager eager@eagerm.com
Wed Sep 24 16:55:00 GMT 2014

On 09/24/14 09:23, Chen Gang wrote:
> On 09/24/2014 11:37 PM, Mike Stump wrote:
>> 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.
> OK, thank you for your information.
> For one simple solving way under fedora: "yum install rsh", and I will
> get another issue:
>    "Download to microblaze-xilinx-gdb failed, microblaze-xilinx-gdb: Unknown host"
> So I guess the root cause is: I only use cross-compiling environments
> under fedora x86_64, no any real or virtual target for test.

You can see the command which is getting the error by looking at gcc.log.
If the command is not displayed, add another "-v" (or two) to RUNTESTFLAGS.

If I recall correctly, DejaGNU is executing a command like "rcp file microblaze-xilinx-gdb".
This means that you need to have the name microblaze-xilinx-gdb resolved into an IP address.
This can be done by adding it to /etc/hosts.  Or you can specify the target IP address
in the DejaGNU options.  I don't recall which one off the top of my head.

Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077

More information about the Gcc-patches mailing list