adding an argument for test execution in testsuite

[Nenad Vukicevic]

It seems that I fixed my problem by defining remote_spawn
procedure (and fixing the order of loading libraries :) ) in my
own upc-dg.exp file and adding a line to it that append
additional arguments to the command line: "append commandline 
$upc_run_arguments".

global $upc_run_arguments is getting set before dg-test is being
called. I used a simple string compare to see if dynamic
threads are required. So far it works as expected.

Thank you.
Nenad

On 5/4/2011 10:18 AM, Ian Lance Taylor wrote:
> Nenad Vukicevic<nenad@intrepid.com>  writes:
>
>> Thank you for your response. I am trying to write some tests
>> for GUPC that have two modes of compilation: static and dynamic. In
>> static environment you specify number of threads you want to run in
>> compile time, while in dynamic you specify it when you run the
>> program (prog -n4 args). We have to test both modes and I was thinking
>> of checking the compile arguments and passing -n4 to _load procedure
>> for dynamic case. It could be that I can accomplish this with a new
>> target in dejagnu.
>>
>> I tried defining upc_load() procedure (the same way gnat_load() is defined)
>> and possible add all the necessary code to it, but was not successful in
>> dejagnu calling it.
> Sorry, I can't help you there.  DejaGNU is just awful.  It has only one
> thing going for it, which is that it mostly works.  In every other
> respect it is worse than having no test harness at all.  Unfortunately
> that one advantage currently outweighs the disadvantages.
>
> Ian