Re: [PATCH, testsuite] Fix profile test failures

2014-02-14 Thread Steve Ellcey
On Fri, 2014-02-14 at 11:12 +, Richard Sandiford wrote: > Using target in itself should be OK. The hostname for rsh/ssh should be > [board_info $board hostname] rather than $board itself. So in this case > [board_info "multi-sim/-EL" hostname] should be multi-sim. The usual way > to set tha

Re: [PATCH, testsuite] Fix profile test failures

2014-02-14 Thread Richard Sandiford
Steve Ellcey writes: > On Thu, 2014-02-13 at 23:09 +, Joseph S. Myers wrote: >> On Thu, 13 Feb 2014, Steve Ellcey wrote: >> >> > While testing the C++ profiling tests in g++.dg/bprob and using the >> > qemu simulator we discovered that these tests were passing when we ran >> > the testsuite

Re: [PATCH, testsuite] Fix profile test failures

2014-02-13 Thread Joseph S. Myers
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

Re: [PATCH, testsuite] Fix profile test failures

2014-02-13 Thread Steve Ellcey
On Thu, 2014-02-13 at 23:09 +, Joseph S. Myers wrote: > On Thu, 13 Feb 2014, Steve Ellcey wrote: > > > While testing the C++ profiling tests in g++.dg/bprob and using the > > qemu simulator we discovered that these tests were passing when we ran > > the testsuite with no extra options but tha

Re: [PATCH, testsuite] Fix profile test failures

2014-02-13 Thread Joseph S. Myers
On Thu, 13 Feb 2014, Steve Ellcey wrote: > While testing the C++ profiling tests in g++.dg/bprob and using the > qemu simulator we discovered that these tests were passing when we ran > the testsuite with no extra options but that if we specified some options > on the testsuite run then the tests

[PATCH, testsuite] Fix profile test failures

2014-02-13 Thread Steve Ellcey
While testing the C++ profiling tests in g++.dg/bprob and using the qemu simulator we discovered that these tests were passing when we ran the testsuite with no extra options but that if we specified some options on the testsuite run then the tests would fail with this message in the c++.log file: