search for: inferring

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 you agree with me that R is a

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

On Aug 21, 2012, at 4:41 PM, Chris Lattner <clattner at apple.com> wrote: > Personally, I don't like the direction of 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 becom...

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

...s<"X86", [i32, f32], 32, (add GR32, FR32)>; I thought this would be a harmless thing to do since the new register class is not being referenced anywhere. I was wrong, it caused all kinds of assertion failures from tablegen's isel pattern generator. It appears that tablegen is inferring the 'type' of an individual register by enumerating all the register classes it appears in. Some things, like using implicit defs in SDNodes, only works for registers with a unique type. My WIDE32 class caused GR32 registers to no longer have a unique type, breaking the world. This seems...

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. This might be

On Aug 21, 2012, at 3:02 PM, Chris Lattner <clattner at apple.com> wrote: > > On Aug 21, 2012, at 2:02 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: > >> 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. >

...iants. I don't think it would detract to add "let mayLoad = 1 in {…}" around the *rm groups etc. Personally, I don't like the direction of 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. -Chris

On Sep 23, 2011, at 1:38 PM, David A. Greene wrote: > Jakob Stoklund Olesen <stoklund at 2pi.dk> writes: > >> It appears that tablegen is inferring the 'type' of an individual >> register by enumerating all the register classes it appears in. Some >> things, like using implicit defs in SDNodes, only works for registers >> with a unique type. My WIDE32 class caused GR32 registers to no >> longer have a unique t...

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

...n, and we often forget to set neverHasSideEffects = 1. $ grep -c UnmodeledSideEffects lib/Target/*/*GenInstrInfo.inc lib/Target/ARM/ARMGenInstrInfo.inc:727 lib/Target/X86/X86GenInstrInfo.inc:920 I don't think more than half of those UnmodeledSideEffects flags should be there. I want to stop inferring instruction properties from patterns in TableGen. It has become very hard to read instruction definitions when some properties are inferred, but only half the time. We can still use any patterns to emit TableGen warnings. If an instruction has a sideeffecting pattern, but hasSideEffects isn't...

Jakob Stoklund Olesen <stoklund at 2pi.dk> writes: > It appears that tablegen is inferring the 'type' of an individual > register by enumerating all the register classes it appears in. Some > things, like using implicit defs in SDNodes, only works for registers > with a unique type. My WIDE32 class caused GR32 registers to no > longer have a unique type, breaking th...

On Jan 7, 2014, at 10:47 AM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: > > On Jan 7, 2014, at 10:40 AM, Evan Cheng <evan.cheng at apple.com> wrote: > >> >> On Dec 30, 2013, at 8:40 PM, Chris Lattner <clattner at apple.com> wrote: >> >>> >>> On Dec 30, 2013, at 4:17 PM, Hal Finkel <hfinkel at anl.gov> wrote:

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 >> registers

Dear All, Slightly off -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/>

...over all the universities offering graduate degrees in statistics" Lohr and Rao 2000. Now suppose someone wants to study a characteristic of this population but does so by taking 2 separate samples, each from its corresponding frame. What package lets me combine the info from the 2 samples for inferring something to the whole population? Thank you and have a great day!! __________________________________________________ [[alternative HTML version deleted]]

SGTM On 02/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

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