This is trying to implement the functionality proposed in: http://lists.llvm.org/pipermail/cfe-dev/2017-April/053417.html
An exception can throw, but no cleanup is going to happen. A module compiled with exceptions on, can catch the exception throws from module compiled with -fignore-exceptions.
The use cases for enabling this option are:
- Performance analysis of EH instrumentation overhead
- The ability to QA non EH functionality when EH functionality is not available.
- User of EH enabled headers knows the calls won't throw in their program and wants the performance gain from ignoring EH construct.
The implementation tried to accomplish that by removing any landing pad code that might get generated.
construct -> constructs