Currently regression checks are run with 'make xcheck' and this makes up the command:
${RUN} -i -o -l 2> .err > .out
In some builds we may want extra arguments e.g. -geom 1 1 1 1
or for QDP-JIT one may want a -ptxdb or similar argument
or for QPhIX builds one may want a list of -by -bz etc options.
These would need to go after the eecutable (so they cannot be part of the the RUN)
which would place them either before the executable or after the redirects.
The issue can be solved if the RUN script is made a bit more sophisticated e.g. it doesn't just
do $* but splits it into a head and a and the extra args can be sandwiched between the head and the tail.
Alternatively the orchestrator in chroma/scripts/run_chroma_xmldiff.pl could be changed.
Currently regression checks are run with 'make xcheck' and this makes up the command:
${RUN} -i -o -l 2> .err > .out
In some builds we may want extra arguments e.g. -geom 1 1 1 1 or for QDP-JIT one may want a -ptxdb or similar argument or for QPhIX builds one may want a list of -by -bz etc options.
These would need to go after the eecutable (so they cannot be part of the the RUN) which would place them either before the executable or after the redirects.
The issue can be solved if the RUN script is made a bit more sophisticated e.g. it doesn't just do $* but splits it into a head and a and the extra args can be sandwiched between the head and the tail.
Alternatively the orchestrator in chroma/scripts/run_chroma_xmldiff.pl could be changed.