How to turn off exceptions in Microsoft compiler(cl)?
What compiler flags do I use to completely get rid of the exception handling? I don't use them at all but the compiler still generates .pdata and .xdata sections which there for exception handling only.
Solution
In your project properties set the Enable C++ Exceptions to No:
and enable the unwind semantics by specifying the /EHsc flag:
To set this option on command line you would leave out the /EHa, /EHsc and /EHs flags from the [option] section as described in the Compiler Command-Line Syntax manual.
Further relevant MSDN reading:
- Call function in pre-compile time
- Why is there a large performance difference between C and Fortran for matrix multiplication?
- Why doesn't the child window pop up on top of the parent window?
- Free space bitmap C implementation
- Does devm_drm_dev_alloc() treat the drm_device as a managed resource of the parent device?
- Count bits 1 on an integer as fast as GCC __builtin__popcount(int)
- Stabilizing the standard library qsort?
- C- Readline() undefined reference
- Does the the 2+2W litmus test code in the 'Repairing Sequential Consistency' paper have a problem?
- How to render text in SDL2?
- How to write same client text when using different implementation?
- Backspace can't be detected in Linux terminal , K&R 1.10 exercise
- Check scanf formatting without conversions
- Accessing structure member that is identical to macro name
- how to create a new type with custom bytes in C?
- How to avoid integer promotion in C?
- How do I generate gzip files with the optional CRC16 field?
- How to write Linux Security Module to deny delete (unlink) For kernel 6.x?
- integer, printf: is there a way to write an integer as a wide char to console without locale.h?
- Can a C program detect if its own source code has been modified?
- #define macro for debug printing in C?
- Convert current time from Windows to Unix timestamp?
- Determine size of dynamically allocated memory in C
- Why is it allowed for a const pointer to be passed as non-const argument of a function and get modified?
- Function that implements Taylor Series in C return the value of the argument
- Why does this C code print different values for the same pointer when cast to different types?
- Can a C compiler legally reject a program if its call stack depth exceeds a fixed limit at compile time?
- Why does this function not modify the original array when passed as a parameter?
- What does the ??!??! operator do in C?
- Why does this function pointer typedef behave differently when used with const?