Fix incorrect behavior of __has_unique_object_representations when using the no_unique_address attribute.
Based on the bug report: https://bugs.llvm.org/show_bug.cgi?id=47722
Differential D89649
Fix __has_unique_object_representations with no_unique_address gbencze on Oct 18 2020, 10:18 AM. Authored by
Details Fix incorrect behavior of __has_unique_object_representations when using the no_unique_address attribute. Based on the bug report: https://bugs.llvm.org/show_bug.cgi?id=47722
Diff Detail Event TimelineComment Actions This looks fine as far as it goes, but it doesn't fix all cases of incorrect behavior of __has_unique_object_representations due to [[no_unique_address]]. Feel free to either to land this as-is and leave the other case to a separate patch, or fix it as a revision of this same change. I would expect we'll want to unify the code paths for base classes and non-static data members, which might be better done all at once.
Comment Actions Sorry for the slow update on this.
Comment Actions It looks great.
Comment Actions Adding a few subscribers I could find from the original bugzilla entry, + perhaps a few reviewers to help us. Comment Actions Gentle boop. Bugzilla is offline for me right now (and rumour has it that it will be completely shut down in the near future), so it would be good to know what is the status of this patch and how it related to the mentioned (and right now unavailable) bug report, as it is also blocking a Clang-Tidy check. |