Intravision/reactos
1
0
Fork 0
mirror of https://github.com/reactos/reactos.git synced 2025-05-15 07:17:23 +00:00
Code Issues Projects Releases Packages Wiki Activity

[PSEH_TEST]

Browse source 
#if out a test for C++. This test only shows the limitations of PSEH and does not provide a satisfying result anyway.

svn path=/trunk/; revision=62629
This commit is contained in:
Timo Kreuzer 2014-04-05 16:49:17 +00:00
parent e76390da3e
commit 73512e7ad4
1 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
rostests/tests/pseh2/psehtest.c
View file

@ -2447,6 +2447,15 @@ DEFINE_TEST(test_unvolatile_2)
return (val == 3) || (val == 4) || (val == 5);
}
/* This test is mainly for documentation purpose. As can be seen it doesn't
provide a satisfying result. In fact the compiler could do even more
crazy things like reusing val1 between the assignment to 0 and the last
assignment to 3. This DOES happen with C++ and it's NOT a PSEH bug, but
rather an unavoidable consequence of how the compiler works.
The conclusion: Do not use assignments to a variable inside a __try block
that is being used later inside the __except block, unless it is declared
volatile! */
#ifndef __cplusplus
DEFINE_TEST(test_unvolatile_3)
{
int register val1 = 0, val2 = 0;
@ -2494,6 +2503,7 @@ DEFINE_TEST(test_unvolatile_3)
return FALSE;
}
#endif // __cplusplus
DEFINE_TEST(test_unvolatile_4)
{
@ -2840,7 +2850,9 @@ void testsuite_syntax(void)
USE_TEST(test_unvolatile),
USE_TEST(test_unvolatile_2),
#ifndef __cplusplus
USE_TEST(test_unvolatile_3),
#endif
USE_TEST(test_unvolatile_4),
USE_TEST(test_finally_goto),
USE_TEST(test_nested_exception),