search for: inference

Dear R Admins, I received an unsolicited e-mail from BlueInference as an R user. Does it mean that R that our e-mails (and names) is sharing it's user database with third parties without our consent? Or perhaps the BlueInference guys are using an e-mail address miner to get our contact details? [SNIP] Dear Gorden Jemwa, As a fellow R user, I am sure...

While looking at optimizations where Souper exploits known bits, I realized that it would be easy to teach Souper to compute known bits. Comparing its results against computeKnownBits() from r246393, it looks like there are some easy (and some not-easy) opportunities for improvement, please see a few examples below. The expressions come from compiling LLVM itself. Happily, this exercise

...making everything be redundantly specified with "let" clauses and in the patterns. I agree that it is a problem that we're not inferring from Pat<> patterns, and that not all instructions are expressible with patterns, but I'd rather we solve *those* problems than throw out inference. After discussing this, we have reached a workable compromise. Here's what we'll do: The inferred instruction properties will become tristate and default to Unset: bit hasSideEffects = ?; bit mayLoad = ?; bit mayStore = ?; TableGen will attempt to infer these properties from any i...

The bio.infer package contains a data frame /usr/lib/R/library/bio.infer/data/itis.ttable.rda that needs to be modified. After loading the bio.infer package and attaching the data frame with the data() function, I wrote the data frame to a text file. After adding another row to the data frame I applied read.table() to create a data frame, but it's in my pwd, not the R library data

...Besides my current experiments with wide register classes, Blackfin's general purpose registers can hold both i32 and v2i16 types. Does that mean Blackfin instructions can't use GPR implicit defs as SDNode results? I would like to fix this, but I am not sure how. I could: - Disable type inference for individual registers entirely, or - Add a ValueType field to the Register tablegen class, so types are not inferred by enumerating register classes. Any suggestions? /jakob

Hello, I looked for R packages which focused on order-restricted statistical inference, but I could find only the isoreg() function. I would need to test whether the means in my (repeated measures) data follow a given order, e.g. A<B=C<D. I took a look at the monograph by Barlow et al. (1972) on this topic and found that for my case the null hypothesis is always A=B=C=D. Th...

...it is assumed to have side effects. > > Hi Jakob, > > I don't understand what you're saying. Are you proposing that all properties (may load, store, side effects) be explicitly added to all instructions, and the pattern only be used to produce warnings? Yes. The side effect inference is worse than the load/store inference, but features like this work best when they work all the time. If all instructions had patterns, and we could accurately infer properties, it wouldn't be a problem. > Won't this hugely bloat the .td files? Not really, TableGen has a fairly conveni...

...esen <stoklund at 2pi.dk> wrote: >> I don't understand what you're saying. Are you proposing that all properties (may load, store, side effects) be explicitly added to all instructions, and the pattern only be used to produce warnings? > > Yes. > > The side effect inference is worse than the load/store inference, but features like this work best when they work all the time. If all instructions had patterns, and we could accurately infer properties, it wouldn't be a problem. Ok, I agree with that. I think it's crazy that we still can't write a pattern for...

...ed GR32 registers to no >> longer have a unique type, breaking the world. > > I can't remeber the specific situation, but I remember running into > this kind of problem before. > >> This seems too fragile to me. > > Yes, it is. :( > >> - Disable type inference for individual registers entirely, or >> >> - Add a ValueType field to the Register tablegen class, so types are >> not inferred by enumerating register classes. > > I tend to think the second would be preferable, but how would we handle > registers than can hold diffe...

In porting some Common LISP code to R, I am trying to found out whether special care must be taken for the let* function. In Common LISP, "the let* block is like let except it is guaranteed to evaluate the initialization of its local variables in sequentially nested scopes, i.e. it provides an order to the binding and visibility of preceding variables.". I have included the recursive

All, TableGen likes to infer the MCID::UnmodeledSideEffects flag from an instruction's pattern. When an instruction doesn't have a pattern, it is assumed to have side effects. It's possible to override this behavior by setting neverHasSideEffects = 1. It was originally the intention that most instructions have patterns, but that's not the way it worked out. It is often more

...> with a unique type. My WIDE32 class caused GR32 registers to no > longer have a unique type, breaking the world. I can't remeber the specific situation, but I remember running into this kind of problem before. > This seems too fragile to me. Yes, it is. :( > - Disable type inference for individual registers entirely, or > > - Add a ValueType field to the Register tablegen class, so types are > not inferred by enumerating register classes. I tend to think the second would be preferable, but how would we handle registers than can hold different types of values?...

...listed explicitly in the td files. >>>> >>>> Having recently audited these flags in the PowerPC backend, I highly recommend looking at these from the *GenInstrInfo.inc file directly. I find this much easier. In theory, we'd like to move away from the pattern-based flag inference. Once a target is free of dependence on the inference rules, it can set bit guessInstructionProperties = 0; to turn them off completely (see class InstrInfo in Target.td). >>> >>> In MHO, we should try to avoid redundancy as much as possible. The only reason to have these flags...

In the following snippet, can''t the includes being inferred from the where clause? Order.includes(:items).where(:items => { :category => [1,2,3] }) Can''t the includes be inferred from the where clause? Order.where(:items => { :category => [1,2,3] }) Would this conflict with any existing usages of the where clause and hashes? -- You received this

Jakob Stoklund Olesen <stoklund at 2pi.dk> writes: >>> - Disable type inference for individual registers entirely, or >>> >>> - Add a ValueType field to the Register tablegen class, so types are >>> not inferred by enumerating register classes. >> >> I tend to think the second would be preferable, but how would we handle >> regis...

...-non technical topic ( but hey it is Friday) Following last week's interview with REvolution Computing which makes enterprise versions of R, here is another interview with the rapidly growing company Blue Reference CEOPaul van Eikeren at <http://www.decisionstats.com/2009/06/04/interview-inference-for-r/> http://www.decisionstats.com/2009/06/04/interview-inference-for-r/ Paul talks on his product, Inference for R- a add on plugin which makes a R GUI within Office Excel available for 199$ a year ( and *separate academic*program as well) for enhanced analytics as well as graphical capabili...

Good afternoon! My question is more of a "is there a package for doing........?" an inference regarding the mean, median, regression estimates, etc. by using the information from dual frame surveys? (this methodology is based on the work of BANKIER 1986, SKINNER 1991, LOHR and RAO 2000...) If one has 2 independent studies which both independently measure a trait of a population, but b...

...17/2018 03:52 PM, Nuno Lopes wrote: > I can step in, if that's ok with you. > Nuno > > -----Original Message----- From: Philip Reames > Sent: Saturday, February 17, 2018 1:04 AM > To: Davide Italiano ; Nuno Lopes > Cc: llvm-dev > Subject: Re: [llvm-dev] Missing attribute inference cases > > Sure, but is anyone willing to mentor?  I don't have time.  I can > advise, but only infrequently. > > Philip > > > On 02/16/2018 03:47 PM, Davide Italiano wrote: >> Yes, I agree with you this sounds like a great GSoC. >> >> On Fri, Feb 16, 20...

Dear R mailing list, I have a dataset with genotypes from trios and I would like to infer haplotypes for each mother, father and child. The package that I could find that can do this is tdthap. But when the mother is homozygous (e.g., 2/2) the haplotype is called as not possible to infer (0); I would prefer for it to call the genotype (2). From what I understand it is doing what I would like

Hi Devs, I am a PhD student at Indiana University. I am interested in working on the project on function attribute inference. My current research direction involves runtime binary optimization using JIT compilation from a lifted LLVM IR. I am hoping various runtime information coupled with static analysis on the IR can provide better avenues for runtime code JITTIng (akin to PGO). Anyway I think the project on function...