search for: globlasmodref

...both (a) and (b) seem > > like active nightmares to try to fix. I can see hacky ways to > > avoid (a) where we detect *why* GetUnderlyingObject fails, but I > > don't see how to fix both (a) and (b) (or to fix (a) well) without > > just disabling this specific aspect of GloblasModRef. > > Ok, but we need performance information to make sure this doesn’t > cause a regression in practice for LTO builds. For example, Spec 2K > and 2K6 are a reasonable place to start. > > > 1) Fix obvious issues with GloblasModRef and switch it to > > ValueHandles >...

...e that (c) doesn't happen today. But both (a) and (b) seem like active nightmares to try to fix. I can see hacky ways to avoid (a) where we detect *why* GetUnderlyingObject fails, but I don't see how to fix both (a) and (b) (or to fix (a) well) without just disabling this specific aspect of GloblasModRef. So that's what I'd like to do. It shouldn't impact the mod/ref information provided by the analysis, just the alias sets. However, even this may not be necessary. We may just not in practice see these issues, and I don't really want to perturb the LTO generated code quality for a...

...;t happen today. But both (a) and (b) seem like active > nightmares to try to fix. I can see hacky ways to avoid (a) where we detect > *why* GetUnderlyingObject fails, but I don't see how to fix both (a) and > (b) (or to fix (a) well) without just disabling this specific aspect of > GloblasModRef. > > Ok, but we need performance information to make sure this doesn’t cause a > regression in practice for LTO builds. For example, Spec 2K and 2K6 are a > reasonable place to start. > > > 1) Fix obvious issues with GloblasModRef and switch it to ValueHandles > > 2) Mai...