On Fri, Oct 3, 2014 at 12:45 PM, Jason Merrill <ja...@redhat.com> wrote: > On 10/03/2014 02:41 PM, Cary Coutant wrote: >>> >>> O. Then I was indeed wrong and defaulted does not impact ABI at all. >>> At least that is one worry less for the abi checkers :) >> >> >> As Siva mentioned, it does in fact impact the ABI. A class with a >> non-trivial destructor is not a POD, and affects the calling >> convention, so the debugger needs to know the difference. > > > Yes, but defaulted does not imply trivial (though the converse is true), so > knowing whether a declaration is defaulted is neither necessary nor > sufficient to determine the parameter passing ABI.
I understand that knowing whether a copy-ctor or a d-tor has been explicitly defaulted is not sufficient to determine the parameter passing ABI. However, why is it not necessary? I could be wrong, but doesn't the example I have given show that it is necessary? Thanks, Siva Chandra
