search for: printarg

Hi, I have a simple R script for printing arguments cat > printargs.R << EOF args = commandArgs() print(args) q() EOF To run this script, first I set PATH to ~/src/R-2.6.2 and execute > R --no-save < printargs.R I want to run this script with different R versions by defining an .Renviron file in the same directory as printargs.R...

On 2020-01-11 01:38, Darren Tucker wrote: > The command you give is always handled on the server by your shell in some > fashion. It has to be, because SSH only specifies an opaque string for the > remote command, so without doing so you would not be able to specify > arguments at all. It's not obvious why does it have to be this way. ssh sends the command as an array of

Hi , I am using LLVM for my Post Graduate course project on Optimization. I am trying to do some insrtumentation to the bytecode.I 've been going through your Instrumentation code for the past few days in /llvm/lib/Transforms/Instrumentation folder and finally found two ways of instrumentation : 1) injecting LLVM bytecode instructions 2) calling an external C function. I am trying both and

...stop.on.failure = TRUE) + { + rfoo <- eval(as.name(paste("r", stub, sep=""))) + pfoo <- eval(as.name(paste("p", stub, sep=""))) + s <- superror(rfoo, pfoo, sample.size, ...) + if (print.result || print.detail) { + printargs <- substitute(list(...)) + printargs[[1]] <- as.name(stub) + cat(deparse(printargs)) + if (print.detail) + cat("\nsupremum error = ",signif(s,2), + " with p-value=",min(1,round(pdkwbound(sample.size,s),4)),"\n"...

...ng convention is used. R.dll!6c799419() [Frames below may be incorrect and/or missing, no symbols loaded for R.dll] R.dll!6c797736() user32.dll!7633cd90() user32.dll!7636c1c2() Rgraphapp.dll!63551cba() CODE ==== // R code library(showArgs) blah = as.Date('2000-01-01') printArgs(a=1:3, b=LETTERS[1:3], blah=blah) // END R code // C/Cpp code: extern "C" { // because I compile the code 'as C++' for Visual C++, for in-code variable declaration SEXP __cdecl showArgs_ext(SEXP args); } SEXP __cdecl showArgs_ext(SEXP args) { // snip args = CDR(args); /* skip...

.../UnitTests/byval-alignment SingleSource/UnitTests/conditional-gnu-ext SingleSource/UnitTests/conditional-gnu-ext-cxx SingleSource/UnitTests/DefaultInitDynArrays SingleSource/UnitTests/FloatPrecision SingleSource/UnitTests/initp1 SingleSource/UnitTests/member-function-pointers SingleSource/UnitTests/printargs SingleSource/UnitTests/SignlessTypes/cast2 SingleSource/UnitTests/SignlessTypes/cast-bug SingleSource/UnitTests/SignlessTypes/ccc SingleSource/UnitTests/SignlessTypes/div SingleSource/UnitTests/SignlessTypes/factor SingleSource/UnitTests/SignlessTypes/Large/cast SingleSource/UnitTests/SignlessType...

...SingleSource/UnitTests/2005-05-11-Popcount-ffs-fls | * | * | SingleSource/UnitTests/2009-12-07-StructReturn | * | * | SingleSource/UnitTests/2002-12-13-MishaTest | * | * | SingleSource/UnitTests/printargs | * | * | SingleSource/UnitTests/2007-03-02-VaCopy | * | * | SingleSource/UnitTests/2003-08-11-VaListArg | * | * | SingleSource/UnitTests/2003-07-10-SignConversions...

...* * * | n/a n/a n/a n/a SingleSource/UnitTests/Vector/sumarray-dbl | 0.0057 1064 * * * | 0.00 * * * * | n/a n/a n/a n/a SingleSource/UnitTests/printargs | 0.0032 724 0.0036 * 0.0035 | 0.00 0.00 0.00 * 0.00 | - - n/a n/a

...0.00 * 0.02 | n/a - n/a n/a SingleSource/UnitTests/Vector/sumarray-dbl | 0.0040 1064 0.0080 * 0.0080 | 0.00 * 0.00 * 0.01 | n/a - n/a n/a SingleSource/UnitTests/printargs | 0.0040 680 0.0040 * 0.0000 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp...

LLVMers, The 2.2 prerelease is now available for testing: http://llvm.org/prereleases/2.2/ If anyone can help test this release, I ask that you do the following: 1) Build llvm and llvm-gcc (or use a binary). You may build release (default) or debug. You may pick llvm-gcc-4.0, llvm-gcc-4.2, or both. 2) Run 'make check'. 3) In llvm-test, run 'make TEST=nightly report'. 4) When

...0.00 * 0.02 | n/a - n/a n/a SingleSource/UnitTests/Vector/sumarray-dbl | 0.0061 1056 0.0046 * 0.0046 | 0.00 * 0.00 * 0.01 | n/a - n/a n/a SingleSource/UnitTests/printargs | 0.0038 672 0.0030 * 0.0029 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a

...0.00 * 0.00 | n/a - n/a n/a SingleSource/UnitTests/Vector/sumarray-dbl | 0.0025 1116 0.0023 * 0.0023 | 0.00 * 0.00 * 0.00 | n/a - n/a n/a SingleSource/UnitTests/printargs | 0.0013 764 0.0017 * 0.0017 | 0.00 0.00 0.00 * 0.00 | - - n/a n/a

...        0.00 | -       -       n/a          n/a > SingleSource/UnitTests/Vector/sumarray-dbl                               | > 0.0000 976      0.0100      *                0.0100      |    0.00    0.01 >  0.00 *           0.02 | -       -       n/a          n/a > SingleSource/UnitTests/printargs                                         | > 0.0000 760      0.0100      *                0.0000      |    0.00    0.00 >  0.00 *           0.01 | -       -       n/a          n/a > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.ui...

Hi Tanya, > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a > pre-compiled llvm-gcc or re-compile it yourself. I compiled llvm and llvm-gcc with separate objects directories. Platform is x86_64-linux-gnu. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to

...- n/a n/a > SingleSource/UnitTests/Vector/sumarray- > dbl | 0.0000 976 0.0100 > * 0.0100 | 0.00 0.01 0.00 * > 0.02 | - - n/a n/a > SingleSource/UnitTests/ > printargs | 0.0000 760 > 0.0100 * 0.0000 | 0.00 0.00 0.00 > * 0.01 | - - n/a n/a

LLVMers, The 2.1 pre-release (version 1) is available for testing: http://llvm.org/prereleases/2.1/version1/ I'm looking for members of the LLVM community to test the 2.1 release. There are 2 ways you can help: 1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0 binary. Run "make check" and the full llvm-test suite (make TEST=nightly report). 2) Download

LLVMers, 2.6 pre-release2 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre- compiled llvm-gcc or re-compile it yourself. 2) Run make check,

LLVMers, The 2.5 pre-release is available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run "make

Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability

...3 4997 0 0.01 4985 0 0.01 4985 PR640.ll 4 19066 0 0.01 19054 0 0.01 19054 prboard.ll 1 24762 0 0.01 24729 0 0.01 24729 prepair.ll 1 8790 0 0.01 8757 0 0.01 8757 preprocess.ll 1 12481 0 0.01 12451 0 0.01 12451 prestrict.ll 1 16735 0 0.01 16702 0 0.01 16702 primes.ll 9 14036 0 0.01 14005 0 0.01 14005 printargs.ll 1 2837 0 0.01 2828 0 0.01 2828 printgph.ll 1 12861 0 0.01 12828 0 0.01 12828 print.ll 4 23223 0 0.01 23193 0 0.01 23193 printnets.ll 1 17393 0 0.01 17360 0 0.01 17360 procesnet.ll 3 102636 0 0.02 102603 0 0.02 102603 procquery.ll 2 37292 0 0.01 37258 0 0.01 37258 ProgressMt.ll 9 27557 0 0.01 27...