Previously this flag was just ignored. If set, set the IMAGE_DLL_CHARACTERISTICS_NO_SEH bit, regardless of the normal safeSEH machinery.
In mingw configurations, the safeSEH bit might not be set in e.g. object files built from handwritten assembly, making it impossible to use the normal safeseh flag. As mingw setups don't generally use SEH on 32 bit x86 at all, it should be fine to set that flag bit though - hook up the existing GNU ld flag for controlling that.
@hans - This isn't a regression fix, but a fairly safe new option, that might be important for VLC (it might fix https://code.videolan.org/videolan/vlc-winrt/-/issues/303, issues in certifying VLC built with llvm-mingw, due to this flag missing).
Should setNoSEHCharacteristic and config->noSEH always agree? What happens when they don't?
setNoSEHCharacteristic is set in Writer::createSEHTable when there are no SEH handlers. Should this logical-OR happen there?
What happens if the user chooses --noSEH but there are SEH handlers?