search for: coarser

Hi, In following link: https://www.youtube.com/watch?reload=9&v=6X12D46sRFw They have specified that the inliner can't use DomTree/LoopInfo/MemorySSA analysis. 1. What's the reason for this? 2. Why can't we do it using getAnalysisUsage() construct? 3. Can inline use this information in the new Pass Manager? 4. What all information can we derive from DomTree to be of help to

In the old pass manager a coarser-grain pass cannot depend on a fine-grain pass (or analysis). In this case, the coarser-grain is the Inliner (CallGraphSCCPass) and the finer a FunctionPass. The reason is that the finer-grain pass has its own "pass manager", i.e. it runs all the passes and analysis (in that pass manager)...

...modulePassManager? Also, you have said that this wasn't the primary reason for the introduction of the new pass manager. But then is this one of the reasons? Regards Sushant On Tue, Nov 10, 2020 at 2:28 AM Michael Kruse <llvmdev at meinersbur.de> wrote: > In the old pass manager a coarser-grain pass cannot depend on a > fine-grain pass (or analysis). In this case, the coarser-grain is the > Inliner (CallGraphSCCPass) and the finer a FunctionPass. The reason is > that the finer-grain pass has its own "pass manager", i.e. it runs all > the passes and analysis (in...

Dear list, I'm writing a function to re-grid a data set from finer to coarser resolutions in R as follows (I use this function with sapply/apply): gridResize <- function(startVec = stop("What's your input vector"), to = stop("Missing 'to': How long do you want the fnial vector to be?")){ from <- length(startVec) shortVec<-numeric()...

...pass" doc. The > fix is to change MParSchedule to be a function pass or modulepass. Ok, after combining all your comments in this thread and reading the documentation again. I think i figured it out: Every Pass is allowed to depend on the same granularity (eg. ModulePass on ModulePass) or coarser (eg. BasicBlockPass on Functionpass but *NOT* the other way round). So my here goes my problem: Since my C-Backend modified pass is a module pass i can only depend on module passes. This stands in contrary to the proposed way to use the most apropriate (BasicBlock in my case) pass available. Sinc...

...f loads. We need a way to tell this code to not do that. The solutions I kind of see for this is: - Add some TTI hook that stops this sinking from happening for instructions that don’t support that like in this case (maybe added in canSinkInstructions()) - Add some TTI hook that is a little bit coarser that stops the optimization to run altogether. In particular this thing is creating “unstructured control-flow” in some cases and this is not always good (and actually generally bad) on GPU targets. - Put the optimization in another separate pass. It seems to be doing stuff that is a little bit mo...

...ldlike to add to my first dataframe the value of the LU variables at the coordinates of the first dataframe. Of course, the coordinates are not at the same resolution and are different, this is the problem. I wouldlike to decrease the resolution of the first one because the second dataframe have a coarser resolution and obtain something like that : X Y sp bio3 bio5 bio6 bio13 bio14 LU1 LU2 LU3 LU4 ... 1 -70.91667 -45.08333 0 47 194 -27 47 12 0 22.08 76.9 2 -86.58333 66.25000 0 16 119 -345 42 3 0 22.08 76.9 3 -62.58333 -17.91667 0 68 334 152 144 28 0 2...

I think we should try to abstract the costs of instructions of various targets instead of trying to replicate them exactly. The coarser the costing infrastructure the more robust will be the vectorization pass. Also this eliminates/reduces the need of updating the costing infrastructure as and when new h/w reduces the cost(s) of existing instructions. - Dibyendu -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mai...

...g rid of the horror that is SunSSH for some distros of Illumos (mostly SmartOS). One of the patches we're carrying around at the moment is one that simply drops fine-grained privileges in sshd, ssh-agent and sftp-server. Since the privilege dropping here is roughly equivalent to a more verbose, coarser version of a tame() call, I was wondering if there might be any interest in taking it into openssh-portable in future. Patch is attached. I've made sure all the code is behind #ifdef USE_SOLARIS_PRIVS and added some code in configure.ac to turn this macro on and off. It also has a related fix...

...- Is it worth asking LLVM to commit to a particular convention? - If not, what exactly is LLVM willing to guarantee? - Only calls to module-internal functions? - Calls to functions whose implementation is guaranteed to be compiled with this exact version of the compiler? - Some coarser degree of stability? 3. If we do publish this, what name do we use? - Does not putting LLVM in the name imply that this is some portable thing? - Should we put something like "unstable" in the name to encourage users to think twice about using this casually? 4. Is there a good r...

...c.edu Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Friday, October 5, 2012 3:59:56 AM > Subject: Re: [LLVMdev] LLVM Loop Vectorizer > > I think we should try to abstract the costs of instructions of > various targets instead of trying to replicate them exactly. The > coarser the costing infrastructure the more robust will be the > vectorization pass. Also this eliminates/reduces the need of > updating the costing infrastructure as and when new h/w reduces the > cost(s) of existing instructions. I think that one of the big questions is where this information,...

...endu > Sent: Friday, October 05, 2012 2:00 AM > To: Nadav Rotem; llvmdev at cs.uiuc.edu Mailing List > Subject: Re: [LLVMdev] LLVM Loop Vectorizer > > I think we should try to abstract the costs of instructions of various > targets instead of trying to replicate them exactly. The coarser the > costing infrastructure the more robust will be the vectorization pass. > Also this eliminates/reduces the need of updating the costing > infrastructure as and when new h/w reduces the cost(s) of existing > instructions. > - Dibyendu > > -----Original Message----- > Fr...

...g LLVM to commit to a particular convention? > - If not, what exactly is LLVM willing to guarantee? > - Only calls to module-internal functions? > - Calls to functions whose implementation is guaranteed to be compiled > with this exact version of the compiler? > - Some coarser degree of stability? > 3. If we do publish this, what name do we use? > - Does not putting LLVM in the name imply that this is some portable thing? > - Should we put something like "unstable" in the name to encourage users > to think twice about using this casually? >...

...edu Mailing > List" <llvmdev at cs.uiuc.edu> > Sent: Friday, October 5, 2012 3:59:56 AM > Subject: Re: [LLVMdev] LLVM Loop Vectorizer > > I think we should try to abstract the costs of instructions of various > targets instead of trying to replicate them exactly. The coarser the > costing infrastructure the more robust will be the vectorization pass. > Also this eliminates/reduces the need of updating the costing > infrastructure as and when new h/w reduces the > cost(s) of existing instructions. I think that one of the big questions is where this infor...

...lvmdev at cs.uiuc.edu> > > Sent: Friday, October 5, 2012 3:59:56 AM > > Subject: Re: [LLVMdev] LLVM Loop Vectorizer > > > > I think we should try to abstract the costs of instructions of > > various > > targets instead of trying to replicate them exactly. The coarser > > the > > costing infrastructure the more robust will be the vectorization > > pass. > > Also this eliminates/reduces the need of updating the costing > > infrastructure as and when new h/w reduces the > > cost(s) of existing instructions. > > I think th...

...tween llvm::GlobalObject (e.g. function or global variable) and lld:DefinedAtom." > > it seems that the primary issue on the ELF/COFF side is that currently the LLVM backends are taking a finer-grained atomicity that is present inside LLVM, and losing information by converting that to a coarser-grained atomicity that is the typical "section" in ELF/COFF. > But doesn't -ffunction-sections -fdata-sections already fix this, basically? > > On the Mach-O side, the issue seems to be that Mach-O's notion of section carries more hard-coded meaning than e.g. ELF, so at...

...mapping between llvm::GlobalObject (e.g. function or global variable) and lld:DefinedAtom." it seems that the primary issue on the ELF/COFF side is that currently the LLVM backends are taking a finer-grained atomicity that is present inside LLVM, and losing information by converting that to a coarser-grained atomicity that is the typical "section" in ELF/COFF. But doesn't -ffunction-sections -fdata-sections already fix this, basically? On the Mach-O side, the issue seems to be that Mach-O's notion of section carries more hard-coded meaning than e.g. ELF, so at the very least...

..., and I would like to get some feedback on those patches as well as my general plan. Some background: I am porting ASan to the Myriad platform. I'm looking to break up that port into components that may be useful/relevant to other platforms -- the first of those pieces is the ability to use a coarser shadow granularity. This is important for us because Myriad has a limited amount of physical memory and no virtual memory, so it is important to limit the amount of shadow memory required. My end-goal for this part is to be able to configure a build that overrides the default shadow granularity,...

Hi, I have a ts object with a frequency of 4, i.e., quarterly data, and I would like to calculate the mean for each quarter. So for example: > ts.data=ts(1:20,start=c(1984,2),frequency=4) > ts.data Qtr1 Qtr2 Qtr3 Qtr4 1984 1 2 3 1985 4 5 6 7 1986 8 9 10 11 1987 12 13 14 15 1988 16 17 18 19 1989 20 If I do this manually, the mean

..., biotechANDappliedmicrobiology=223+159, evolutionaryBIO=210+117) There's a great deal more summary information that might be extracted. What is a good way, with readily available data, to standardize the country data. Environmental Science no doubt comes up tops because it is a coarser grouping than many other areas. John Maindonald email: john.maindonald at anu.edu.au phone : +61 2 (6125)3473 fax : +61 2(6125)5549 Centre for Mathematics & Its Applications, Room 1194, John Dedman Mathematical Sciences Building (Building 27) Australian National University, Can...