search for: invar

...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","#9ACD3...

...plain what it is I am doing wrong or a workaround that I can apply. Below is the code I have so far (please feel free to criticize the code, I am new to R/programming with no background). Thanks library(shiny) ui= fluidPage( sidebarLayout( sidebarPanel( selectizeInput(inputId= "invar", label= "invar", choices= names(iris), selected= names(iris)[1], multiple=T), uiOutput("invarpdf") ), mainPanel( tableOutput("tab") ) )) server= function(input, output,ses...

...es that diff -r 3544d85cfe11 src/share/vm/opto/loopPredicate.cpp --- a/src/share/vm/opto/loopPredicate.cpp Thu Jul 19 10:00:36 2018 +0100 +++ b/src/share/vm/opto/loopPredicate.cpp Fri Jul 20 10:06:37 2018 +0800 @@ -869,7 +869,7 @@ Node* idx = cmp->in(1); assert(!invar.is_invariant(idx), "index is variant"); Node* rng = cmp->in(2); - assert(rng->Opcode() == Op_LoadRange || _igvn.type(rng)->is_int() >= 0, "must be"); + assert(rng->Opcode() == Op_LoadRange || _igvn.type(rng)->is_int()->_lo >= 0, &quot...

...>> --- a/src/share/vm/opto/loopPredicate.cpp Thu Jul 19 10:00:36 2018 >> +0100 >> +++ b/src/share/vm/opto/loopPredicate.cpp Fri Jul 20 10:06:37 2018 >> +0800 >> @@ -869,7 +869,7 @@ >> Node* idx = cmp->in(1); >> assert(!invar.is_invariant(idx), "index is variant"); >> Node* rng = cmp->in(2); >> - assert(rng->Opcode() == Op_LoadRange || _igvn.type(rng)- >>> is_int() >> >= 0, "must be"); >> + assert(rng->Opcode() == Op_LoadRange || >&...

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.

...ressions [2]. I'm not particularly happy with this syntax since it is quite verbose (but then again we don't need it that often so it doesn't really matter). It also doesn't allow saving the expression result so it needs to be repeated everywhere. I could probably use [[@EXPR:OUTVAR INVAR + 42]] but I haven't really had the need for that yet. > > We currently need the following two features: > > - Simple arithmetic with multiple operations. Example: > `cld $gp, $zero, [[@EXPR 2 * $CAP_SIZE - 8]]($c11)` > > - Conversion to hex (upper and lower case since not...

...ressions [2]. I'm not particularly happy with this syntax since it is quite verbose (but then again we don't need it that often so it doesn't really matter). It also doesn't allow saving the expression result so it needs to be repeated everywhere. I could probably use [[@EXPR:OUTVAR INVAR + 42]] but I haven't really had the need for that yet. >> > >> > We currently need the following two features: >> > >> > - Simple arithmetic with multiple operations. Example: >> > `cld $gp, $zero, [[@EXPR 2 * $CAP_SIZE - 8]]($c11)` >> > &gt...

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

...ressions [2]. I'm not particularly happy with this syntax since it is quite verbose (but then again we don't need it that often so it doesn't really matter). It also doesn't allow saving the expression result so it needs to be repeated everywhere. I could probably use [[@EXPR:OUTVAR INVAR + 42]] but I haven't really had the need for that yet. >> >> > >> >> > We currently need the following two features: >> >> > >> >> > - Simple arithmetic with multiple operations. Example: >> >> > `cld $gp, $zero, [[@EXPR...

...ressions [2]. I'm not particularly happy with this syntax since it is quite verbose (but then again we don't need it that often so it doesn't really matter). It also doesn't allow saving the expression result so it needs to be repeated everywhere. I could probably use [[@EXPR:OUTVAR INVAR + 42]] but I haven't really had the need for that yet. >> >> > >> >> > We currently need the following two features: >> >> > >> >> > - Simple arithmetic with multiple operations. Example: >> >> > `cld $gp, $zero, [[@EXPR...

...articularly happy with this syntax since it is quite verbose (but then >> again we don't need it that often so it doesn't really matter). It also >> doesn't allow saving the expression result so it needs to be repeated >> everywhere. I could probably use [[@EXPR:OUTVAR INVAR + 42]] but I haven't >> really had the need for that yet. >> >> >> > >> >> >> > We currently need the following two features: >> >> >> > >> >> >> > - Simple arithmetic with multiple operations. Example: &g...