aboutsummaryrefslogtreecommitdiffstats
path: root/gcc-4.9/gcc/testsuite/gcc.c-torture/compile/volatile-1.c
diff options
context:
space:
mode:
Diffstat (limited to 'gcc-4.9/gcc/testsuite/gcc.c-torture/compile/volatile-1.c')
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.c-torture/compile/volatile-1.c18
1 files changed, 18 insertions, 0 deletions
diff --git a/gcc-4.9/gcc/testsuite/gcc.c-torture/compile/volatile-1.c b/gcc-4.9/gcc/testsuite/gcc.c-torture/compile/volatile-1.c
new file mode 100644
index 000000000..cb81274c0
--- /dev/null
+++ b/gcc-4.9/gcc/testsuite/gcc.c-torture/compile/volatile-1.c
@@ -0,0 +1,18 @@
+/* The problem here was that the statements that
+ loaded from exception.reason where not being
+ marked as having volatile behaviour which
+ caused load PRE on the tree level to go
+ into an infinite loop. */
+
+struct gdb_exception
+{
+ int reason;
+};
+int catch_exceptions_with_msg (int *gdberrmsg)
+{
+ volatile struct gdb_exception exception;
+ exceptions_state_mc_init (&(exception));
+ if (exception.reason != 0)
+ foo ();
+ return exception.reason;
+}