search for: 61771

...d we use R_tryEval() at a number places to run R commands. In order to make sure that any generated warnings become visible close to the problem, we were following up (most of) these calls with Rf_PrintWarnings(). Rf_PrintWarnings() was never available in the headers (as far as I know), and in r61771 the symbol has been hidden from libR.so. So this solution is no longer available. Could you give advice on the best way to print warnings before returning to the top level? Some available options, I am aware of: 1. Call R function warnings(). However, this will always print the latest warning,...

...to robustly determine location of caller's fp. Is this incompatibility intentional/desired or we could somehow unify GCC and LLVM in this regard? (*) Links to older discussions: * http://comments.gmane.org/gmane.comp.compilers.llvm.devel/69514 * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61771 -- Best regards, Yury Gribov

Folks, It's 1st of September, and we don't have the document nor the survey ready. With the US meeting on 3-4 November, that leaves us only 2 months to do everything, and I'm not sure we'll be able to if we delay much more. Being the devil's advocate and hoping this doesn't spiral down (again), there were a few pertinent questions left unanswered from the previous

...survey (or maybe my browser). I'm seeing some stray "If responding for a" text at the top. See the PDF I've attached here. -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-10-12 at 16.16.05.png.pdf Type: application/pdf Size: 61771 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161012/56e72377/attachment-0001.pdf> -------------- next part -------------- > > We only have a month and a bit now... > > cheers, > --renato > __________________________________________...