search for: invars

...esvar - name of the variable that contains dates # inars - names of the variables to be graphed # myfunction - function to be used (mean or sum) # my metric - string for the metric # mytitle - title of the graph # fixedy - if 1, range on y axis starts with zero # indata=en;datesvar="Week";invars=seas[5];myfunction=mean # mymetric="TEST";fixedy=0;title="BLA" mylines = function(indata,datesvar,invars,myfunction,mymetric,mytitle,fixedy=0) { all.colors<-c("#E0EEEE","#0000CD","#D4D4D4","#FFC1C1","#FFDEAD","#9ACD32...

Hi All, I am not sure if this is a relevant platform to ask but I have tried other more related platforms and haven't had any luck so i thought i would try my luck here. Basically I want to generate a selectInput widget with a conditional under renderUI in Shiny. The number of widgets generated will depend on the number of variables a user selects. Try as I may I have not been able to get

Hi Thomas, Thanks for your kind response! Please review my backport for hs25, thanks a lot! diff -r 3544d85cfe11 src/share/vm/opto/lcm.cpp --- a/src/share/vm/opto/lcm.cpp Thu Jul 19 10:00:36 2018 +0100 +++ b/src/share/vm/opto/lcm.cpp Fri Jul 20 10:06:37 2018 +0800 @@ -49,7 +49,7 @@ // Check whether val is not-null-decoded compressed oop, // i.e. will grab into the base of the heap

Hi Thomas, Looks good. Your changes in loopPredicate.cpp does not match original changes - they miss iff->is_RangeCheck() check [1]. But in JDK8 we did not have specialized RangeCheckNode class in C2. Suggested fix should be fine fro jdk 8u. Reviewed. Please, when sending RFA ( approval request) use original 8174050 bug id. Thanks, Vladimir [1]

Hi HotSpot and LLVM developers, I am building OpenJDK8[1] with LLVM toolchain[2] for mips64el, it failed to build: /home/loongson/jdk8-mips/hotspot/src/share/vm/opto/lcm.cpp:52:35: error: ordered comparison between pointer and zero ('address' (aka 'unsigned char *') and 'int') if (Universe::narrow_oop_base() > 0) { // Implies UseCompressedOops.

Hi Alex, Thanks for the feedback. My first thought was that introducing the new pseudo var @EXPR is a nice way to generalize that syntax beyond @LINE since it would also evaluate to an arithmetic value. On the other hand there is a small inconsistency because @LINE evaluates to a value which can be part of an expression while @EXPR is an expression, and so the @ syntax as a whole becomes defined

Hi Alexander, Please forgive me if I'm missing the obvious but I do not see how the order helps allowing a comma in the expression. It seems to me that what would allow it is to make FMTSPEC mandatory or at least the comma to separate it (ie. [[#,EXPR]] for the default format specifier). In any case comma in a function-call like expression can be distinguished from comma for the format

To be clear, I do not intend to add support for hex specifier in the current patch, I just want to make sure the syntax we choose is going to allow it later. My immediate use case is decimal integer and I intend to write the code so that it's easy to extend to more type of numeric variables and expressions later. This way we'll only add specifier that are actually required by actual

Hi Alex, On Fri, 27 Jul 2018 at 11:53, Alexander Richardson <arichardson.kde at gmail.com> wrote: > > On Thu, 26 Jul 2018 at 10:28 Thomas Preudhomme <thomas.preudhomme at linaro.org> wrote: >> >> Hi Alexander, >> >> Please forgive me if I'm missing the obvious but I do not see how the >> order helps allowing a comma in the expression. It seems

I can certainly envision a use case for a [BASE + LENGTH + 4] computation to verify the address of a next-thingy. Comes up in DWARF dumps all the time. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of James Henderson via llvm-dev Sent: Tuesday, July 31, 2018 11:53 AM To: Thomas Preudhomme Cc: llvm-dev Subject: Re: [llvm-dev] Syntax for FileCheck numeric variables

Hi James, Yes I think you summary proposal is a good one though I disagree with the colon being optional because there is ambiguity with looking for the value of VAR5 in the %x format. If anything, [[# %x, VAR5]] is equivalent to [[#:%x, VAR5]] or ([[#:%x = VAR5]] with your proposal. My other suggestion would be to use == rather than = since = could be confused with assignment. Note that