Displaying 2 results from an estimated 2 matches for "profile_weight".
2016 Jan 15
3
[PGO] Thoughts on adding a key-value store to profile data formats
...erged it might be simplest to keep all input metadata
(machine-readable things such as feature bits might need to be handled
differently):
$ llvm-profdata merge -weighted-input=3,foo.profdata bar.profdata -o
foobar.profdata
$ llvm-profdata show -metadata foobar.profdata
foo.profdata
llvm.profile_weight: 3
llvm.profile_start_time: "2016-01-08T23:41:56.755Z"
llvm.profile_duration: 5.102s
llvm.exe_time: "2016-01-08T23:35:56.745Z"
customkey: "value1"
bar.profdata
llvm.profile_weight: 1
llvm.profile_start_time: "2016-01-15T00:08:41.168Z"...
2016 Jan 15
2
[PGO] Thoughts on adding a key-value store to profile data formats
...d
> > differently):
>
> Feature bits should not be part of it.
>
> >
> > $ llvm-profdata merge -weighted-input=3,foo.profdata bar.profdata -o
> > foobar.profdata
> > $ llvm-profdata show -metadata foobar.profdata
> > foo.profdata
> > llvm.profile_weight: 3
> > llvm.profile_start_time: "2016-01-08T23:41:56.755Z"
> > llvm.profile_duration: 5.102s
> > llvm.exe_time: "2016-01-08T23:35:56.745Z"
> > customkey: "value1"
> > bar.profdata
> > llvm.profile_weight: 1
>...