On Thursday, 10 December 2015 at 14:38:19 UTC, Liran Zvibel wrote:
> Also, for use cases like ours, where the system runs for extended periods of time, and optimizing the init time, which may be minutes is not interesting at all, just being able to run perf while the system is doing something interesting to improve is a big plus.

As I understand, if the profiling runs long enough, the long-running statistics will dominate startup statistics?

On Wednesday, 23 December 2015 at 13:10:33 UTC, Kagamin wrote:
> On Thursday, 10 December 2015 at 14:38:19 UTC, Liran Zvibel wrote:
>> Also, for use cases like ours, where the system runs for extended periods of time, and optimizing the init time, which may be minutes is not interesting at all, just being able to run perf while the system is doing something interesting to improve is a big plus.
>
> As I understand, if the profiling runs long enough, the long-running statistics will dominate startup statistics?

The profiling is pretty simple: it is just a bunch of counters whereever the code branches. So indeed, long runs will have long-running statistics dominate startup statistics.

On Tuesday, 8 December 2015 at 19:13:41 UTC, Johan Engelen wrote:
> Hi all,
>   I have been working on getting rudimentary PGO going in LDC. It's pretty much ready!

It now works with LLVM 3.7 and LLVM 3.8 (trunk), on Mac OS X, Linux (tested on Ubuntu), and Windows! I have not tested other platforms.

Hi David,
  Could you have a look at the PR again?
I think it is almost ready for merging. (two FIXME's left that I hope to address soon)

On Sunday, 13 December 2015 at 13:21:33 UTC, David Nadlinger wrote:
> On 11 Dec 2015, at 1:38, Johan Engelen via digitalmars-d-ldc wrote:
>> What do you think about "llvm-profdata"? Should we ship that with LDC?
>
> Yes, we should probably ship it with the binary packages.

I have added llvm-profdata to the repo, and renamed the built executable to ldc-profdata (it has to be in-sync with the LLVM version that LDC was built with, and so the renaming prevents potential name clashing with a system installed profdata version).

>
> What is left to do before we can merge a first version into the main repository? A partial list:
>
>  - Deal with the remaining FIXME comments (at least open separate GitHub issues for them), as well as with commented-out fragments from the Clang implementation.

I think I will just remove all unused Clang implementation code (it is related to coverage stuff, which I think we should implement in a different branch after PGO is merged).

Thanks!
  Johan