[Rd] Building R from source with the PGI compiler

2017-12-21 Thread Erin Hodgess
Hello I would like to build R from source and use the PGI compiler, rather than the GCC compiler. I saw the instructions for the Intel compiler in the R Installation Manual, but I didn't see the PGI. I tried a few times without instructions, but without success. Any suggestions would be most we

Re: [Rd] Building R from source with the PGI compiler

2017-12-21 Thread Prof Brian Ripley
On 21/12/2017 01:03, Erin Hodgess wrote: Hello I would like to build R from source and use the PGI compiler, rather than the GCC compiler. On what platform? AFAIK we have only ever had reports on Linux. I saw the instructions for the Intel compiler in the R Installation Manual, but I didn't

[Rd] Wish List: base::source() + Add Execution Time Argument

2017-12-21 Thread Juan Telleria
Dear R Developers, Adding to source() base function a Timer which indicates the execution time of the source code would be a very well welcome feature, and in my opinion not difficult to implement as an additional funtion argument. The source(timing = TRUE) function shall execute internally the f

Re: [Rd] R CMD check warning about compiler warning flags

2017-12-21 Thread Duncan Murdoch
On 20/12/2017 6:52 PM, Duncan Murdoch wrote: On 20/12/2017 5:48 PM, Hadley Wickham wrote: On Wed, Dec 20, 2017 at 4:26 PM, Prof Brian Ripley wrote: On 20/12/2017 17:42, Winston Chang wrote: On recent builds of R-devel, R CMD check gives a WARNING when some compiler warning flags are detected

Re: [Rd] Wish List: base::source() + Add Execution Time Argument

2017-12-21 Thread Iñaki Úcar
2017-12-21 12:46 GMT+01:00 Juan Telleria : > Dear R Developers, > > Adding to source() base function a Timer which indicates the execution time > of the source code would be a very well welcome feature, and in my opinion > not difficult to implement as an additional funtion argument. > > The source

Re: [Rd] Wish List: base::source() + Add Execution Time Argument

2017-12-21 Thread Juan Telleria
But by statement in the source file, I mean, for knowing during the execution how much time is taking, without having to wait till the end. 2017-12-21 13:06 GMT+01:00 Iñaki Úcar : > 2017-12-21 12:46 GMT+01:00 Juan Telleria : > > Dear R Developers, > > > > Adding to source() base function a Timer

Re: [Rd] Wish List: base::source() + Add Execution Time Argument

2017-12-21 Thread Iñaki Úcar
2017-12-21 15:05 GMT+01:00 Juan Telleria : > But by statement in the source file, I mean, for knowing during the > execution how much time is taking, without having to wait till the end. What's the ultimate purpose? Are you looking for a profiler (there are some of them on CRAN) or some kind of pr

Re: [Rd] Wish List: base::source() + Add Execution Time Argument

2017-12-21 Thread Juan Telleria
I did not know "progress" package existed, thank you Iñaki. However, something like that would be nice to have by default in source(), just something to add to R's "wish list", so that everybody can benefit from it without extra-packages, as most of us I suppose we will spend all day simply doing

Re: [Rd] Wish List: base::source() + Add Execution Time Argument

2017-12-21 Thread William Dunlap via R-devel
Is source() the right place for this? It may be, but we've had customers who would like this sort of thing done for commands entered by hand. And there are those who want a description of any "non-triivial" objects created in .GlobalEnv by each expression, ... Do they need a way to wrap each expr

Re: [Rd] Wish List: base::source() + Add Execution Time Argument

2017-12-21 Thread Jim Hester
R does provide the addTaskCallback / taskCallbackManager to run a callback function after every top level command. However there is not an equivalent interface that would be run _before_ each command, which would make it possible to time of top level calls and provide other execution measurements.

Re: [Rd] R CMD check warning about compiler warning flags

2017-12-21 Thread Winston Chang
>> On recent builds of R-devel, R CMD check gives a WARNING when some >> compiler warning flags are detected, such as -Werror, because they are >> non-portable. This appears to have been added in this commit: >>https://github.com/wch/r-source/commit/2e80059 > > That is not the canonical R sourc

Re: [Rd] R CMD check warning about compiler warning flags

2017-12-21 Thread Duncan Murdoch
On 21/12/2017 1:02 PM, Winston Chang wrote: On recent builds of R-devel, R CMD check gives a WARNING when some compiler warning flags are detected, such as -Werror, because they are non-portable. This appears to have been added in this commit: https://github.com/wch/r-source/commit/2e80059

Re: [Rd] R CMD check warning about compiler warning flags

2017-12-21 Thread Martin Morgan
On 12/21/2017 01:02 PM, Winston Chang wrote: On recent builds of R-devel, R CMD check gives a WARNING when some compiler warning flags are detected, such as -Werror, because they are non-portable. This appears to have been added in this commit: https://github.com/wch/r-source/commit/2e80059

Re: [Rd] Building R from source with the PGI compiler

2017-12-21 Thread Michael Hannon
Hi, Erin. Please feel free to ignore this, but I'm curious: what is the advantage to using the PGI compiler? -- Mike On Wed, Dec 20, 2017 at 5:03 PM, Erin Hodgess wrote: > Hello > > I would like to build R from source and use the PGI compiler, rather than > the GCC compiler. > > I saw the inst

Re: [Rd] Building R from source with the PGI compiler

2017-12-21 Thread Erin Hodgess
Hello! I’m working on a supercomputer and will be tying into some FORTRAN programs. Those programs use OpenACC, which must be compiled with PGI. In case you are wondering, Why don’t I use C? I actually started with C and FORTRAN is faster. Thanks for listening, Erin On Thu, Dec 21, 2017 at 6: