> have an option for true AAPCS compliance, which will > be allowed to break the C++11 memory model and
> And an option that addresses your requirements, > which will _not_ break the C++11 memory model So the problem isn't that what *I* need conflicts with C++11, it's that what AAPCS needs conflicts?
