search for: typicially

...39;s raw profile size is typically 80M -- if the > instrumented clang is used to build a medium to large size project > (such as clang itself), profile data can easily use up hundreds of > Gig bytes of local storage. This argument is kind of confusing. It says that one profile is typicially 80M, then claims that this uses 100s of GB of data. From these statements that only makes sense I suppose that's true if you run 1000 profiling runs without merging the data in between. Is that what you're talking about, or did I miss something? > 2) pid can also be recycled. This means...

I have purchased a simple windows program that is intended for the training of people handicapped with afasia. I need it for my wife, who suffered a stroke recently and she needs this program as part of her rehabilitation programme. We don't run windows, so I tried it using Wine. The program is written in (some) BASIC and runs on anything from Windows98 and higher. It runs nicely with Wine,

...cally 80M -- if the > > instrumented clang is used to build a medium to large size project > > (such as clang itself), profile data can easily use up hundreds of > > Gig bytes of local storage. > > This argument is kind of confusing. It says that one profile is > typicially 80M, then claims that this uses 100s of GB of data. From > these statements that only makes sense I suppose that's true if you run > 1000 profiling runs without merging the data in between. Is that what > you're talking about, or did I miss something? > Yes. For instance, firs...

...ally 80M -- if the > > instrumented clang is used to build a medium to large size project > > (such as clang itself), profile data can easily use up hundreds of > > Gig bytes of local storage. > > This argument is kind of confusing. It says that one profile is > typicially 80M, then claims that this uses 100s of GB of data. From > these statements that only makes sense I suppose that's true if you run > 1000 profiling runs without merging the data in between. Is that what > you're talking about, or did I miss something? > > Yes. For instance,...

...gt; > instrumented clang is used to build a medium to large size project >> > (such as clang itself), profile data can easily use up hundreds of >> > Gig bytes of local storage. >> >> This argument is kind of confusing. It says that one profile is >> typicially 80M, then claims that this uses 100s of GB of data. From >> these statements that only makes sense I suppose that's true if you run >> 1000 profiling runs without merging the data in between. Is that what >> you're talking about, or did I miss something? >> >>...

One of the main missing features in Clang/LLVM profile runtime is the lack of support for online/in-process profile merging support. Profile data collected for different workloads for the same executable binary need to be collected and merged later by the offline post-processing tool. This limitation makes it hard to handle cases where the instrumented binary needs to be run with large number of