On Thu, 13 Feb 2014, Steve Ellcey wrote: > So let me make sure I understand this: host is where you run the > testsuite from, build is where the compilation happens (probably the > same as host for most people), and target is where the test program is > executed.
Host is the system on which the compilers being tested run. Build is the system on which runtest runs and executes the .exp files. They are only different in the case of remote-host testing (using DejaGnu on GNU/Linux to test a compiler for Windows host, for example) - typically the same cases in which a Canadian cross compiler is built. > > To determine whether anything should be changed in a GCC .exp file, reason > > about which of the three systems (build, host, target) a file is on, or is > > needed on, at each point, rather than looking at what does or does not > > work with a buggy board file. > > I am not convinced that the problem is in the board file because the > only tests I see fail this way are the ones in g++.exp/bprob and that is > also the only GCC .exp file that uses remote_upload or remote_file > with 'target'. I will dig into it some more and also try it with some > different boards. Branch profiling involves the generated executables creating files with profile information when they run, so those files (on the target) need manipulating. Most testsuites do not involve testcases generating any files. But the libstdc++ testsuite uses remote_download to transfer files to the target, because various testcases need to open and read input files. -- Joseph S. Myers jos...@codesourcery.com
