search for: locb

How to I "recode" a factor into a binary data frame according to the factor levels: ### example:start set.seed(20) l <- sample(rep.int(c("locA", "locB", "locC", "locD"), 100), 10, replace=T) # [1] "locD" "locD" "locD" "locD" "locB" "locA" "locA" "locA" "locD" "locA" ### example:end What I want in the end is the followi...

...places I found by manual inspection > If I read the definition correctly, at least our Andersens' AA > implementation violates it. > see: > > AliasResult CFLAndersAAResult::alias(const MemoryLocation &LocA, > const MemoryLocation &LocB) { > if (LocA.Ptr == LocB.Ptr) > return LocA.Size == LocB.Size ? MustAlias : PartialAlias; > > > (i.e. the two objects are overlapping here *and* start at the same address). I've never noticed that part of the definition myself. I'm fairly certain that's not wha...

Hi, I going through the alias analysis documentation (http://llvm.org/docs/AliasAnalysis.html) and noticed the following in the definition of PartialAlias: " The PartialAlias response is used when the two memory objects are known to be overlapping in some way, but *do not start at the same address*. " Is it really required that the objects do no start at the same address? if

...le* %v19, i64 %v22 %getitem24 = load double* %addr23 ---- /IR ---- Right now I'm forwarding alias() calls to base class and just observing the current alias analysis result. Here's a portion of the output ---- Debug ---- LocA %gep9 = getelementptr inbounds %Slice* %a, i64 0, i32 0 LocB %gep18 = getelementptr inbounds %Slice* %b, i64 0, i32 0 Aliases? 0 LocA %addr = getelementptr double* %v10, i64 %v11 LocB %gep18 = getelementptr inbounds %Slice* %b, i64 0, i32 0 Aliases? 0 LocA %gep9 = getelementptr inbounds %Slice* %a, i64 0, i32 0 LocB %addr23 = getelementptr dou...

### example:start v <- sample(rnorm(200), 100, replace=T) k <- rep.int(c("locA", "locB", "locC", "locD"), 25) tapply(v, k, summary) ### example:end ... (hopefully) produces 4 summaries of v according to k group membership. How can I transform the output into a nice table with the croups as columns and the interesting statistics as lines? Thx, S?ren

...t think it's met in a few places I found by manual inspection If I read the definition correctly, at least our Andersens' AA implementation violates it. see: AliasResult CFLAndersAAResult::alias(const MemoryLocation &LocA, const MemoryLocation &LocB) { if (LocA.Ptr == LocB.Ptr) return LocA.Size == LocB.Size ? MustAlias : PartialAlias; (i.e. the two objects are overlapping here *and* start at the same address). I've never noticed that part of the definition myself. I'm fairly certain that's not what we actually implement...

...depends on the size > >>> check, but I don't trust my recollection in this regard. SCEV AA is > >>> known to cause miscompiles, IIRC, maybe you just found out why ;) > >> > >> It's true that the CFL AAs have this code: > >> if (LocA.Ptr == LocB.Ptr) > >> return LocA.Size == LocB.Size ? MustAlias : PartialAlias; > >> > >> > >> I grepped for clients of MustAlias: > >> ~/llvm/lib/Transforms $ grep -Rl MustAlias . > >> ./ObjCARC/ObjCARCOpts.cpp > >> ./ObjCARC/ProvenanceAnalysis.c...

...is code that depends on the size >>> check, but I don't trust my recollection in this regard. SCEV AA is known >>> to cause miscompiles, IIRC, maybe you just found out why ;) >>> >> >> It's true that the CFL AAs have this code: >> if (LocA.Ptr == LocB.Ptr) >> return LocA.Size == LocB.Size ? MustAlias : PartialAlias; >> >> >> I grepped for clients of MustAlias: >> ~/llvm/lib/Transforms $ grep -Rl MustAlias . >> ./ObjCARC/ObjCARCOpts.cpp >> ./ObjCARC/ProvenanceAnalysis.cpp >> ./Scalar/DeadStoreElimi...

...g. > > I'm under the impression that there is code that depends on the size > check, but I don't trust my recollection in this regard. SCEV AA is known > to cause miscompiles, IIRC, maybe you just found out why ;) It's true that the CFL AAs have this code: if (LocA.Ptr == LocB.Ptr) return LocA.Size == LocB.Size ? MustAlias : PartialAlias; I grepped for clients of MustAlias: ~/llvm/lib/Transforms $ grep -Rl MustAlias . ./ObjCARC/ObjCARCOpts.cpp ./ObjCARC/ProvenanceAnalysis.cpp ./Scalar/DeadStoreElimination.cpp ./Scalar/GVN.cpp ./Scalar/LICM.cpp ./Scalar/LoopVersioning...

...f.getParent()->getDataLayout()); > return false; > } > > virtual void getAnalysisUsage(AnalysisUsage &AU) const override > { > AliasAnalysis::getAnalysisUsage(AU); > } > > virtual AliasResult alias(const Location &LocA, const Location &LocB) override > { > const Value *V1 = LocA.Ptr; > const Value *V2 = LocB.Ptr; > > const PointerType *PT1 = dyn_cast<const PointerType>(V1->getType()); > const PointerType *PT2 = dyn_cast<const PointerType>(V2->getType()); > > // The log...

...ing AA. DependenceAnalysis's underlyingObjectsAlias is doing this:   // Check the original locations (minus size) for noalias, which can happen for   // tbaa, incompatible underlying object locations, etc.   MemoryLocation LocAS(LocA.Ptr, LocationSize::unknown(), LocA.AATags);   MemoryLocation LocBS(LocB.Ptr, LocationSize::unknown(), LocB.AATags);   if (AA->alias(LocAS, LocBS) == NoAlias)     return NoAlias;   // Check the underlying objects are the same   const Value *AObj = GetUnderlyingObject(LocA.Ptr, DL);   const Value *BObj = GetUnderlyingObject(LocB.Ptr, DL);   // If the underlyin...

...ti0n B - 10" on the caller ID.? I don't want to modify the caller ID for each individual extension as I want the intra-location caller IDs to show just the extension number.? (e.g. LocA/Ext. 10 calls LocA/Ext11 - LocA/Ext11's CallerID displays "10", but LocA/Ext10 calling LocB/Ext20 displays "Location A - 10" for caller ID. I have my locations set up in the pjsip_wizard.conf file like this: Location A: [Uplink_defaults](!) type = wizard transport = transport-udp endpoint/allow_subscribe = no endpoint/allow = !all,g729 aor/qualify_frequency = 30 registration...

...on't trust my recollection in this regard. SCEV AA is >>>>>> known to cause miscompiles, IIRC, maybe you just found out why ;) >>>>>> >>>>> >>>>> It's true that the CFL AAs have this code: >>>>> if (LocA.Ptr == LocB.Ptr) >>>>> return LocA.Size == LocB.Size ? MustAlias : PartialAlias; >>>>> >>>>> >>>>> I grepped for clients of MustAlias: >>>>> ~/llvm/lib/Transforms $ grep -Rl MustAlias . >>>>> ./ObjCARC/ObjCARCOpts.cpp &g...

..."Initializing everything-must-alias\n"); InitializeAliasAnalysis(this); } virtual void getAnalysisUsage(AnalysisUsage &AU) const { AliasAnalysis::getAnalysisUsage(AU); AU.setPreservesAll(); } virtual AliasResult alias(const Location &LocA, const Location &LocB) { DEBUG(dbgs() << "Everything must alias!\n"); return AliasAnalysis::MustAlias; } }; } namespace llvm { void initializeEverythingMustAliasPass(PassRegistry &Registry); } char EverythingMustAlias::ID = 0; static RegisterPass<EverythingMustAlias> A("must-aa...

Alias analysis is figuring out the relationship between two pointer expressions, at some location in the program. At a given point in the program, do two expressions always refer to the same location? At a given point in the program, do two expressions never refer to the same location? AliasAnalysis::alias() doesn't explicitly take a "point" in the program because we don't

...re are the details: > > We’re checking following two locations: > > (lldb) p ((llvm::Instruction*)(LocA.Ptr))->dump() > %arrayidx.i = getelementptr inbounds [1 x %struct.elt_list*], [1 x > %struct.elt_list*]* %te.i, i64 0, i64 %indvars.iv.i > (lldb) p ((llvm::Instruction*)(LocB.Ptr))->dump() > @reg_values = internal unnamed_addr global %struct.varray_head_tag* null, > align 8 > > and the function in question is “cselib_init”: > (lldb) p > ((llvm::Instruction*)(LocA.Ptr))->getParent()->getParent()->getName() > (llvm::StringRef) $3 = (Data =...

On Thu, Jan 15, 2015 at 1:26 PM, Nick Lewycky <nlewycky at google.com> wrote: > On 15 January 2015 at 13:10, Daniel Berlin <dberlin at dberlin.org> wrote: > >> Yes. >> I've attached an updated patch that does the following: >> >> 1. Fixes the partialalias of globals/arguments >> 2. Enables partialalias for cases where nothing has been unified to

On Fri, Jul 17, 2015 at 9:13 AM Evgeny Astigeevich < evgeny.astigeevich at arm.com> wrote: > It’s Dhrystone. > Dhrystone has historically not been a good indicator of real-world performance fluctuations, especially at this small of a shift. I'd like to see if we see any fluctuation on larger and more realistic application benchmarks. One advantage of the flag being set is that we

...ot;); > InitializeAliasAnalysis(this); > } > > virtual void getAnalysisUsage(AnalysisUsage &AU) const { > AliasAnalysis::getAnalysisUsage(AU); > AU.setPreservesAll(); > } > > virtual AliasResult alias(const Location &LocA, const Location &LocB) { > DEBUG(dbgs() << "Everything must alias!\n"); > return AliasAnalysis::MustAlias; > } > }; > } > > namespace llvm { > void initializeEverythingMustAliasPass(PassRegistry &Registry); > } > > char EverythingMustAlias::ID = 0; > st...

...e recurrences for these > >> loop expressions, has this: > >> // This is ScalarEvolutionAliasAnalysis. Get the SCEVs! > >> const SCEV *AS = SE->getSCEV(const_cast<Value *>(LocA.Ptr)); > >> const SCEV *BS = SE->getSCEV(const_cast<Value *>(LocB.Ptr)); > >> > >> // If they evaluate to the same expression, it's a MustAlias. > >> if (AS == BS) return MustAlias; > >> > >> > >> IE if the two recurrences for the pointers are equal, it's a mustalias. > >> > >>...