Will 'Guaranteed Copy Elision' (P0135, C++1z) potentially require ABI breakage?

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0135r0.html

The above proposal for 'Guaranteed Copy Elision' was voted into the C++ working paper in the June 2016 meeting in Oulu, Finland, which was then voted for publication as a committee draft. Hopefully that leads to publication as the C++17 standard next year.

The proposal clarifies various value categories involving temporary objects, to enforce the absence of copy constructor calls in certain use cases.

My question is "might this new requirement might break ABI compatibility for compilers that might previously not have done copy elision in these circumstances, or have implemented it in a way that won't be compatible with the new requirements?"

I'm thinking of things like initializations that elide copies when the creation of an object can be inlined, but not when crossing compilation unit boundaries.