rjmccall added a comment.
Wait, can you talk me through the bug here? Why is final-based
devirtualization here different from, say, user-directed devirtualization via a
qualified method name?
It sounds to me from your description that you're not sure why this is
happening. If this indeed only triggers in the presence of multiple
inheritance, it might just be the case that you're doing your object-extents
analysis starting from the wrong offset.
cfe-commits mailing list