On Fri, May 29, 2015 at 11:48:34AM +0100, Alan Lawrence wrote:
Christophe Lyon wrote:
This looks OK, but why can't you also drop the other torture-related
lines as you did in your previous patch?
I mean:
load_lib c-torture.exp
load_lib torture-options.exp
etc...
We need
Christophe Lyon wrote:
This looks OK, but why can't you also drop the other torture-related
lines as you did in your previous patch?
I mean:
load_lib c-torture.exp
load_lib torture-options.exp
etc...
We need c-torture.exp in order to set-torture-options; we need to
set-torture-options to get
On 29 May 2015 at 12:48, Alan Lawrence alan.lawre...@arm.com wrote:
Christophe Lyon wrote:
This looks OK, but why can't you also drop the other torture-related
lines as you did in your previous patch?
I mean:
load_lib c-torture.exp
load_lib torture-options.exp
etc...
We need
On 28 May 2015 at 18:45, Alan Lawrence alan.lawre...@arm.com wrote:
I've tested this on aarch64, aarch64_be, and arm, and in all cases, the same
tests are executed (whether running the whole advsimd-intrinsics.exp, or
manually specifying a single file). AFAICT the loop, explicit
I've tested this on aarch64, aarch64_be, and arm, and in all cases, the same
tests are executed (whether running the whole advsimd-intrinsics.exp, or
manually specifying a single file). AFAICT the loop, explicit runtest_file_p,
and gcc_set_parallelization_enable, all stem from a point where we