[PATCH] D27163: Introduce -f[no-]strict-return flag that controls code generation for C++'s undefined behaviour return optimisation

[David Majnemer via Phabricator via cfe-commits]

majnemer added a comment.

My 2 cents: If making this a target-specific default is not OK, why not turn on -fno-strict-return if -fapple-kext is specified? I believe that would cover the critical use case in question.


Repository:
  rL LLVM

https://reviews.llvm.org/D27163