search for: dlcose

...lved in adding this feature: 1. the target platform needs to have file locking support 2. there needs an efficient way to identify the profile data and associate it with the binary using binary/profdata signature; 3. Currently without merging, profile data from shared libraries (including dlopen/dlcose ones) are concatenated into the primary profile file. This can complicate matters, as the merger also needs to find the matching shared libs, and the merger also needs to avoid unnecessary data movement/copy; 4. value profile data is variable in length even for the same binary. All the above issu...

...re: > 1. the target platform needs to have file locking support > 2. there needs an efficient way to identify the profile data and > associate it with the binary using binary/profdata signature; > 3. Currently without merging, profile data from shared libraries > (including dlopen/dlcose ones) are concatenated into the primary profile > file. This can complicate matters, as the merger also needs to find the > matching shared libs, and the merger also needs to avoid unnecessary data > movement/copy; > 4. value profile data is variable in length even for the same binary....

...ature: > 1. the target platform needs to have file locking support > 2. there needs an efficient way to identify the profile data and > associate it with the binary using binary/profdata signature; > 3. Currently without merging, profile data from shared libraries > (including dlopen/dlcose ones) are concatenated into the primary > profile file. This can complicate matters, as the merger also needs > to find the matching shared libs, and the merger also needs to avoid > unnecessary data movement/copy; > 4. value profile data is variable in length even for the same binary....

...> 1. the target platform needs to have file locking support > 2. there needs an efficient way to identify the profile data and associate it > with the binary using binary/profdata signature; > 3. Currently without merging, profile data from shared libraries > (including dlopen/dlcose ones) are concatenated into the primary > profile file. This can complicate matters, as the merger also needs to > find the matching shared libs, and the merger also needs to avoid > unnecessary data movement/copy; > 4. value profile data is variable in length even for the same...

...orm needs to have file locking support > > 2. there needs an efficient way to identify the profile data and > associate it > > with the binary using binary/profdata signature; > > 3. Currently without merging, profile data from shared libraries > > (including dlopen/dlcose ones) are concatenated into the primary > > profile file. This can complicate matters, as the merger also needs to > > find the matching shared libs, and the merger also needs to avoid > > unnecessary data movement/copy; > > 4. value profile data is variable in leng...

...target platform needs to have file locking support >> 2. there needs an efficient way to identify the profile data and >> associate it with the binary using binary/profdata signature; >> 3. Currently without merging, profile data from shared libraries >> (including dlopen/dlcose ones) are concatenated into the primary profile >> file. This can complicate matters, as the merger also needs to find the >> matching shared libs, and the merger also needs to avoid unnecessary data >> movement/copy; >> 4. value profile data is variable in length even for...

...platform needs to have file locking support > > 2. there needs an efficient way to identify the profile data and associate it > > with the binary using binary/profdata signature; > > 3. Currently without merging, profile data from shared libraries > > (including dlopen/dlcose ones) are concatenated into the primary > > profile file. This can complicate matters, as the merger also needs to > > find the matching shared libs, and the merger also needs to avoid > > unnecessary data movement/copy; > > 4. value profile data is variable in leng...

...o have file locking support >> > 2. there needs an efficient way to identify the profile data and associate it >> > with the binary using binary/profdata signature; >> > 3. Currently without merging, profile data from shared libraries >> > (including dlopen/dlcose ones) are concatenated into the primary >> > profile file. This can complicate matters, as the merger also needs to >> > find the matching shared libs, and the merger also needs to avoid >> > unnecessary data movement/copy; >> > 4. value profile data is...

...ile locking support >>>> 2. there needs an efficient way to identify the profile data and >>>> associate it with the binary using binary/profdata signature; >>>> 3. Currently without merging, profile data from shared libraries >>>> (including dlopen/dlcose ones) are concatenated into the primary profile >>>> file. This can complicate matters, as the merger also needs to find the >>>> matching shared libs, and the merger also needs to avoid unnecessary data >>>> movement/copy; >>>> 4. value profile data...