It is unfortunate that UPC program cannot use dg-additional-sources
as we would need to change our run-time to support this option. By the
time we reach "main" run-time is already initialized to support specified
number of threads. One of the options might be to define a default number
of threads
On 05/04/2011 11:21 AM, Nenad Vukicevic wrote:
> 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
> $
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 getti
Nenad Vukicevic 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
> pro
On 5/3/2011 3:47 PM, Ian Lance Taylor wrote:
There is no support for passing options to a test in the dg framework.
You would have to write your own Tcl code to do that.
Note that such tests are somewhat discouraged because not all remote
execution environments support passing command line argum
Nenad Vukicevic writes:
> Is it possible to add an argument to the test in the
> execution phase of the testsuite? I am looking into
> some test cases where number of threads to run must
> be provided on the invocation line of the test if not
> specified during the test compilation. Something tha
Is it possible to add an argument to the test in the
execution phase of the testsuite? I am looking into
some test cases where number of threads to run must
be provided on the invocation line of the test if not
specified during the test compilation. Something that
is similar to "dg-skip-if" syntax
