Wait a second, won't UBSan handle this automatically if memcpy/memmove are declared with __attribute__((nonnull)) in the header? Otherwise, is there a change to the standard that imposes these additional constraints on memcpy/memmove?
Not really. memcpy/memmove calls are handled by CGBultin and not CGCall. It's a different code path. Nuno
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
