From 1bc5aee63eb72b341f506ad058502cd0361f0d10 Mon Sep 17 00:00:00 2001 From: Ben Cheng Date: Tue, 25 Mar 2014 22:37:19 -0700 Subject: Initial checkin of GCC 4.9.0 from trunk (r208799). Change-Id: I48a3c08bb98542aa215912a75f03c0890e497dba --- .../gfortran.dg/nonreturning_statements.f90 | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 gcc-4.9/gcc/testsuite/gfortran.dg/nonreturning_statements.f90 (limited to 'gcc-4.9/gcc/testsuite/gfortran.dg/nonreturning_statements.f90') diff --git a/gcc-4.9/gcc/testsuite/gfortran.dg/nonreturning_statements.f90 b/gcc-4.9/gcc/testsuite/gfortran.dg/nonreturning_statements.f90 new file mode 100644 index 000000000..6268f7229 --- /dev/null +++ b/gcc-4.9/gcc/testsuite/gfortran.dg/nonreturning_statements.f90 @@ -0,0 +1,25 @@ +! { dg-final { scan-assembler-not "should_be_noreturn" } } +! PR 17758 +! This checks that non-returning subroutines and statements +! really don't return by calling non-existing subroutines +! afterwards. These calls are supposed to be optimized away, so +! they won't show up in the generated assembly. +program main + character(len=5) :: c + c = '12345' + read(unit=c,fmt='(A)') i + select case(i) + case(1) + call abort + call abort_should_be_noreturn + case(2) + stop 65 + call stop_numeric_should_be_noreturn + case(3) + stop "foobar" + call stop_string_should_be_noreturn + case(4) + call exit + call exit_should_be_noreturn + end select +end program main -- cgit v1.2.3