search for: cxx_devirtu

...produce IR that gets linked together (e.g. clang vs. swift). > > How about this approach: > - Instead of taking a meaningless !{} argument, invariant.group takes a string argument which identifies a metadata-dependent optimization. In your case, it would be something like !"clang.cxx_devirtualization". > - Functions have a "supported optimizations" list which declares all the metadata-reliant optimizations they promise to have correct metadata for. So e.g. clang++ would list "clang.cxx_devirtualization" on every single function it compiled, regardless of...

...together (e.g. clang vs. swift). >> >> How about this approach: >> - Instead of taking a meaningless !{} argument, invariant.group takes a >> string argument which identifies a metadata-dependent optimization. In >> your case, it would be something like !"clang.cxx_devirtualization". >> - Functions have a "supported optimizations" list which declares all >> the metadata-reliant optimizations they promise to have correct metadata >> for. So e.g. clang++ would list "clang.cxx_devirtualization" on every >> single funct...

...IR that gets linked together (e.g. clang vs. swift). > > How about this approach: > - Instead of taking a meaningless !{} argument, invariant.group takes a > string argument which identifies a metadata-dependent optimization. In > your case, it would be something like !"clang.cxx_devirtualization". > - Functions have a "supported optimizations" list which declares all the > metadata-reliant optimizations they promise to have correct metadata for. > So e.g. clang++ would list "clang.cxx_devirtualization" on every single > function it compiled,...

...frontends that produce IR that gets linked together (e.g. clang vs. swift). How about this approach: - Instead of taking a meaningless !{} argument, invariant.group takes a string argument which identifies a metadata-dependent optimization. In your case, it would be something like !"clang.cxx_devirtualization". - Functions have a "supported optimizations" list which declares all the metadata-reliant optimizations they promise to have correct metadata for. So e.g. clang++ would list "clang.cxx_devirtualization" on every single function it compiled, regardless of wheth...

...that gets linked together (e.g. clang vs. swift). >> >> How about this approach: >> - Instead of taking a meaningless !{} argument, invariant.group takes a string argument which identifies a metadata-dependent optimization. In your case, it would be something like !"clang.cxx_devirtualization". >> - Functions have a "supported optimizations" list which declares all the metadata-reliant optimizations they promise to have correct metadata for. So e.g. clang++ would list "clang.cxx_devirtualization" on every single function it compiled, regardless...

Hi folks, here is a link to the proposal that we've been working on lately: https://docs.google.com/document/d/16GVtCpzK8sIHNc2qZz6RN8amICNBt vjWUod2SujZVEo/edit?usp=sharing But for the record, I also paste it here. Feedback will be really appreciated!