search for: 20time

Hi, this is about kicking-off regular compile-time tracking for LLVM and CLANG on the green dragon: http://lab.llvm.org:8080/green/view/Compile%20Time/ <http://lab.llvm.org:8080/green/view/Compile%20Time/>. The goal is to stay on top of compile-time issues immediately when they occur so they can be assessed rather than creeping in unnoticed. The methodology is simple: form a CTMark suite out of 10 “long” compiling tests of the LLVM test sui...

...Hoflehner via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> >> Hi, >> >> this is about kicking-off regular compile-time tracking for LLVM and CLANG on the green dragon: http://lab.llvm.org:8080/green/view/Compile%20Time/ <http://lab.llvm.org:8080/green/view/Compile%20Time/>. The goal is to stay on top of compile-time issues immediately when they occur so they can be assessed rather than creeping in unnoticed. The methodology is simple: form a CTMark suite out of 10 “long” compiling tests of the LLVM test sui...

Hi, Does the LLVM project perform any kind of tracking for commit-by-commit compile-time changes? It looks like LNT only tracks run-time performance (and to be honest I wasn't able to make heads or tails of the results even for that -- the interface was pretty unintuitive to me.) While it is "normal" that each new LLVM release regresses compile-time by 2-3%, LLVM 10 seems to be

On Sun, Dec 18, 2016 at 11:10 AM, Philip Reames <listmail at philipreames.com> wrote: > On 12/17/2016 01:35 PM, Davide Italiano via llvm-dev wrote: >> [...] > > I'd really like to see a profile which broke down the time spent in Value > Propagation and LVI. As the person who has touched both most recently, I am > probably the responsible party. At the same time,

...ed on green dragon for O0g, Os and - forward looking - O3 LTO. This means O0g and Os is watched very closely, while O3 LTO at this stage is just "getting a look” (a double digit increase will certainly raise eyebrows though). The tracking data is at http://lab.llvm.org:8080/green/view/Compile%20Time/. > 2. Is ASM parsing treated as a bottleneck in the flow? It is not the default in the compilation flow though. > 3. Do we have a target here? how fast does LLVM want to be? Our data showed that compile-time increased steadily by double digits in the last 2 years for Os and a little less...

...: the date are not in a regular interval but like: 12-05-2009 14-05-2009 20-05-2009 and so on for each date I've many measurement that correspond to displacement registered in many points i.e. http://www.terrafirma.eu.com/Documents/Workshops/WS%206/Advanced%20interpretation%20of%20PSI%20time%20series%20for%20mapping%20and%20characterization%20of%20geological%20hazards%20Naro%20(Italy).pdf HERE So it possible to built a TS? 3) It is possible to identify and to group TS that show simlar trend? and how I can make this? For Example all TS that show seasonal trend I assign class 1,...

Here's a small R program: --------------------------------------------------------------------------- a <- rep(1,10000000) system.time(a <- a + 1) system.time(for (i in 1:10000000) {a[i] <- a[i] + 1}) --------------------------------------------------------------------------- and here's its matlab version:

Hi, Continuing recent efforts in understanding compile time slowdowns, I looked at some historical data: I picked one test and tried to pin-point commits that affected its compile-time. The data I have is not 100% accurate, but hopefully it helps to provide an overview of what's going on with compile time in LLVM and give a better understanding of what changes usually impact compile time.

Hi, It's been a while since I sent the last compile time report [1], where it was shown that LLVM was getting slower over time. But now I'm happy to bring some good news: finally, LLVM is getting faster, not slower :) *** Current status *** Many areas of LLVM have been examined and improved since then: InstCombine, SCEV, APInt implementation, and that resulted in almost 10% improvement

First of all, sorry for the long mail. Inspired by the excellent analysis Rui did for lld, I decided to do the same for llvm. I'm personally very interested in build-time for LTO configuration, with particular attention to the time spent in the optimizer. Rafael did something similar back in March, so this can be considered as an update. This tries to include a more accurate high-level