Yes, thanks for pointing the calling conventions out, I didn't really know what you were getting at.
The hardware calling convention does dictate certainly what code the compiler can put out.
If the compiler does not support NVRO and emits code that causes multiple copy/constructions it doesn't matter if the hardware supports more efficient behaviour.
I edited my earlier comment with your correction, thanks.
The hardware calling convention does dictate certainly what code the compiler can put out.
If the compiler does not support NVRO and emits code that causes multiple copy/constructions it doesn't matter if the hardware supports more efficient behaviour.
I edited my earlier comment with your correction, thanks.