search for: minsize

Right now we have a healthy mixture of two ways to respond to -Oz and -Os in LLVM: 1) Pass this info to the PassManagerBuilder and then toggle some flag to the pass to change thresholds. 2) When running over IR, inspect it for the minsize or optsize attribute. Regardless of the particulars of what these mean and/or how they relate to -O2 vs -O3 for example, I'd really like to at least get to *one* way of doing this. The only way that is really compatible with LTO use cases is to use the function attributes, so I'd suggest...

...t >> distinguish anymore. >> > > Yes and also the issue of needing more information to make a smart > isIntDivCheap() decision. > > In visitSDIV(), checking looks like this when the denominator is a power of 2. > > if (TLI.isIntDivCheap(N->getValueType(0), MinSize)) > return SDValue(); > > // Target-specific implementation of sdiv x, pow2. > if (SDValue Res = BuildSDIVPow2(N)) > return Res; > > How about this for isIntDivCheap? > 1) pass Function* to allow the target to decide for itself which > attributes matter,...

Hi, On 08/07/2015 10:30 PM, Nick Lewycky wrote: [...] > Depends. What is the exact declaration of format_long? > > > In the input .ll file it is: > > ; Function Attrs: minsize optsize > define internal i16 @format_long(i16* %res.8.par, i16 %base.9.par, > i32 %x.10.par) #3 { > > which is later changed somewhere in opt to: > > ; Function Attrs: minsize nounwind optsize > define internal fastcc i16 @format_long(i16* %res.8.par, i16 &...

...6 10, i32 10), !dbg !22 >> which will use %_tmp30 to write in the alloca'd buffer. > >> Shoulnd't MemoryDependenceAnalysis::getDependency rather return the call? > > Depends. What is the exact declaration of format_long? In the input .ll file it is: ; Function Attrs: minsize optsize define internal i16 @format_long(i16* %res.8.par, i16 %base.9.par, i32 %x.10.par) #3 { which is later changed somewhere in opt to: ; Function Attrs: minsize nounwind optsize define internal fastcc i16 @format_long(i16* %res.8.par, i16 %base.9.par, i32 %x.10.par) #2 { Thanks, Mikael &g...

...y there. > However, I'm adding and deviating from the purely historical differences to > try and better model the latest developments in LLVM's optimizer... So here > goes: > > > > > > 1) The easiest: 'Minimize Size' or '-Oz' > > - Attribute: minsize (we already have it, nothing to do here) > > - Goal: minimize the size of the resulting binary, at (nearly) any cost. > > > > > > 2) Optimize for size or '-Os' > > - Attribute: optsize (we already have it, nothing to do here) > > - Goal: Optimize the exec...

...mmary results: ### Use a sample of 100 #### > set.seed(331) > nsize = 100 > sam <- sample(1:nrow(nhis), nsize) > > t1 <- tree( RESP ~ AGE_P + ORIGIN_I + RACRECI2 + parents + educ, + method = "class", + control = tree.control(nobs = nsize, minsize = 10), + data = nhis[sam,]) > summary(t1) Classification tree: tree(formula = RESP ~ AGE_P + ORIGIN_I + RACRECI2 + parents + educ, data = nhis[sam, ], control = tree.control(nobs = nsize, minsize = 10), method = "class") Number of terminal nodes: 13 #####...

...there. However, I'm adding and deviating from the purely historical differences to try and better model the latest developments in LLVM's optimizer... So here goes: >> > >> > >> > 1) The easiest: 'Minimize Size' or '-Oz' >> > - Attribute: minsize (we already have it, nothing to do here) >> > - Goal: minimize the size of the resulting binary, at (nearly) any cost. >> > >> > >> > 2) Optimize for size or '-Os' >> > - Attribute: optsize (we already have it, nothing to do here) >> > -...

...>>> Yes and also the issue of needing more information to make a smart >>> isIntDivCheap() decision. >>> >>> In visitSDIV(), checking looks like this when the denominator is a power of 2. >>> >>> if (TLI.isIntDivCheap(N->getValueType(0), MinSize)) >>> return SDValue(); >>> >>> // Target-specific implementation of sdiv x, pow2. >>> if (SDValue Res = BuildSDIVPow2(N)) >>> return Res; >>> >>> How about this for isIntDivCheap? >>> 1) pass Function* to allow t...

Here is something I wrote years ago. I expect you can adjust it for your needs # cat remove_blank_vmail #!/bin/bash # remove_blank_vmail takes arguments as voicemail boxes and removes messages with audio files shorter then MINSIZE (in bytes) #---------------------------------------------------------------------- # Description: # Author: John Harragin Monroe-Woodbury CSD # Created at: Thu Nov 6 12:27:35 EST 2008 # # Copyright: None. Modify and use however you like... # #-------------------------------------------------------...

...me. I can try to reduce a testcase if you need it. If you could do that, that would be great. Our testing has been primarily for -Oz and -O2, so I haven’t looked at -O3 at all. > I don't think this is really the right approach. With LTO, you can have a mix of functions, some of which are minsize, and some of which are not. Or with profile info, we might want to outline only cold code (I guess this isn't implemented yet, but potentially future work). Tying whether we run the outliner to a command-line flag restricts the possible uses; either the entire module gets outlining, or none o...

IN the /var/log/ folder there are two files WTMP and BTMP BTMP is getting huge after a year, about 800MB, WTMP is getting close to 1MB. In the /etc/logrotate.conf I see this -------------------- # no packages own wtmp -- we'll rotate them here /var/log/wtmp { monthly minsize 1M create 0664 root utmp rotate 1 } ------------------- I can see where WTMP will probably rotate at some point soon. However there is nothing for BTMP. I thought about doing the same thing for btmp however the permissions are set at 0600 currently on the file. Will logrotate be able to r...

> On Aug 19, 2015, at 3:48 PM, escha via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > >> On Aug 19, 2015, at 1:45 PM, Steve King via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> In the targets I know, shifts are >> cheaper than divides in both speed and size. > > From what I remember, udiv by

...le guided > “adaptive optimization” framework to avoid duplication: > > - A unified way of setting hot/cold cutoff percentile (e.g. through > PSI that’s already used by all PGO/FDO). > - A unified way of selecting opt strategy for cold functions: default, > none, size, minsize. > > > > Thanks, > > Wenlei > > > > *From: *llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Modi Mo > via llvm-dev <llvm-dev at lists.llvm.org> > *Reply-To: *Modi Mo <modimo at fb.com> > *Date: *Wednesday, September 9, 2020 at 5:55...

...n levels, and the relevant history there. However, I'm adding and deviating from the purely historical differences to try and better model the latest developments in LLVM's optimizer... So here goes: > > > 1) The easiest: 'Minimize Size' or '-Oz' > - Attribute: minsize (we already have it, nothing to do here) > - Goal: minimize the size of the resulting binary, at (nearly) any cost. > > > 2) Optimize for size or '-Os' > - Attribute: optsize (we already have it, nothing to do here) > - Goal: Optimize the execution of the binary without...

...functions worth outlining from. > This would incur unnecessary compile-time overhead. Thus, we decided > the best course of action is to teach the backend about size options. I don't think this is really the right approach.  With LTO, you can have a mix of functions, some of which are minsize, and some of which are not.  Or with profile info, we might want to outline only cold code (I guess this isn't implemented yet, but potentially future work).  Tying whether we run the outliner to a command-line flag restricts the possible uses; either the entire module gets outlining, or no...

...th these optimization levels, and the relevant history there. However, I'm adding and deviating from the purely historical differences to try and better model the latest developments in LLVM's optimizer... So here goes: 1) The easiest: 'Minimize Size' or '-Oz' - Attribute: minsize (we already have it, nothing to do here) - Goal: minimize the size of the resulting binary, at (nearly) any cost. 2) Optimize for size or '-Os' - Attribute: optsize (we already have it, nothing to do here) - Goal: Optimize the execution of the binary without unreasonably[1] increasing the...

...n) tree (..) Splus 6.0 Solaris 5.7 tree dataset: 100,000 records about 3 variables regression tree data read in from flat file, summary() on R and Splus showed identical distributions tree were run with all the deault setting (no mincut, minsize set etc) with added options: minsize=2, mindev=-1, get the same small tree. Did I miss anything? thanks -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "h...

...es of code test the functions. Any advice on what's going wrong would be greatly appreciated, also any tips for speeding up the code would fantastic. Many thanks Mark Dr Mark Rees Imperial College, Silwood Park, Ascot, Berks, SL5 7PY Direct line 0207 5942488 Fax 0207 594 2339 #Parameters minsize<-log(0.1); maxsize<-log(32); p.vec.names<-rep(NA,11) p.vec<-rep(0,11); p.vec[1]<- 0.36 ; p.vec.names[1]<-"1st survival param"; p.vec[2]<- 0.17 ; p.vec.names[2]<-"2nd survival param"; p.vec[3]<- -18.27; p.vec.names[3]<-"1st flow param...

...y to reduce a testcase if you need it. > If you could do that, that would be great. Our testing has been primarily for -Oz and -O2, so I haven’t looked at -O3 at all. > >> I don't think this is really the right approach. With LTO, you can have a mix of functions, some of which are minsize, and some of which are not. Or with profile info, we might want to outline only cold code (I guess this isn't implemented yet, but potentially future work). Tying whether we run the outliner to a command-line flag restricts the possible uses; either the entire module gets outlining, or none o...

...ecide divide is cheap, the DAGCombiner ignores obvious power-of-2 optimizations. In the targets I know, shifts are cheaper than divides in both speed and size. The target cannot see the value in the isIntDivCheap() call, so cannot itself check for power-of-2 cases. Second, isIntDivCheap passes a MinSize flag to the target, which is true for -Oz (MinSize function attribute). However, the MinSize flags is false for -Os (OptimizeSize function attribute). Both of these try to optimize for size and targets may like to indicate cheap division in both cases, or perhaps for other function attributes in...