Displaying 3 results from an estimated 3 matches for "example_prog".
Did you mean:
example_plot
2009 Feb 17
3
R scripts and parameters
...iced this function returns the pathname of the R executable which is not what I need.
I meant to ask if it is possible to open an R session and launch a script passing parameters that the script can retrieve and use itself.
Just like in C I can run a program and call it with some arguments
> Example_Prog A B C
The program "Example_Prog" can acess its own arguments through the data structures "argc" an "argv".
How can I launch an R script simulating the above mechanism ?
Shall I use source ("script-name") ?
Where are the arguments to be passed, as part of...
2017 Sep 27
2
OrcJIT + CUDA Prototype for Cling
...places the 4th and 5th step. It interprets the host
code with pre-compiled device code as fatbinary. The fatbinary (Step 1
to 3) will be generated with the clang compiler and the nvidia tools
ptxas and fatbinary.
=== Test Cases and Issues
You find the test sources on GitHub in the directory "example_prog".
Run the tests with cuda-interpeter and the two arguments as above:
[1] path to the source code in "example_prog"
- note: even for host-only code, use the file-ending .cu
[2] path to the runtime .fatbin
- note: needs the file ending .fatbin
- a fatbin file is...
2017 Nov 14
1
OrcJIT + CUDA Prototype for Cling
...host code with pre-compiled device code as fatbinary. The
> fatbinary (Step 1 to 3) will be generated with the clang compiler
> and the nvidia tools ptxas and fatbinary.
>
> === Test Cases and Issues
>
> You find the test sources on GitHub in the directory "example_prog".
>
> Run the tests with cuda-interpeter and the two arguments as above:
>
> [1] path to the source code in "example_prog"
> - note: even for host-only code, use the file-ending .cu
>
> [2] path to the runtime .fatbin
> ...