Prev: errors pointing to the message map
Next: oldnames.lib in VS8
From: glchin on 17 May 2008 11:35
I wish to disable exception handling to improve application
performance. When I do this on VS2005, I get:
warning C4530: C++ exception handler used, but unwind semantics are
not enabled. Specify /EHsc

Besides removing usages of STL classes, is there anything else to
avoid?
From: Doug Harrison [MVP] on 17 May 2008 12:02
On Sat, 17 May 2008 08:35:41 -0700 (PDT), glchin(a)hotmail.com wrote:

>I wish to disable exception handling to improve application
>performance.

I doubt this will have a measurable effect, and in the unlikely event that
it does, I bet it can be mitigated merely by avoiding things that establish
exception handlers or throw exceptions in what are normally small, isolated
regions of the program that act as bottlenecks.

>When I do this on VS2005, I get:
>warning C4530: C++ exception handler used, but unwind semantics are
>not enabled. Specify /EHsc
>
>Besides removing usages of STL classes, is there anything else to
>avoid?

Everything that uses try/catch/throw, including the ordinary new operator
and dynamic_cast to reference types.

--
Doug Harrison
Visual C++ MVP
From: Anders Karlsson on 18 May 2008 10:16
On Sat, 17 May 2008 08:35:41 -0700 (PDT), glchin(a)hotmail.com wrote:

> I wish to disable exception handling to improve application
> performance. When I do this on VS2005, I get:
> warning C4530: C++ exception handler used, but unwind semantics are
> not enabled. Specify /EHsc
>
> Besides removing usages of STL classes, is there anything else to
> avoid?

I think you should instead focus work on your algorithms. Turning off
exception handling doesn't sound like a good idea.



--
Freedom is not worth having if it does not include the freedom to make mistakes.
/Mahatma Gandhi
 | 
Pages: 1
Prev: errors pointing to the message map
Next: oldnames.lib in VS8