MC: remove unnecessary restriction on tests

Rafael correctly pointed out that the restriction is unnecessary.  Although the
tests are intended to ensure that we dont abort due to an assertion, running the
tests in all modes is better since it also ensures that we dont crash without
assertions.  Always run these tests to ensure that we can handle invalid input
correctly.

llvm-svn: 209496

llvm/test/MC/AsmParser/invalid-input-assertion.s

@@ -1,5 +1,4 @@
 // RUN: not llvm-mc -triple i686-linux -o /dev/null %s
-// REQUIRES: asserts
 
 	.macro macro parameter=0
 		.if \parameter

llvm/test/MC/COFF/invalid-def.s

@@ -1,5 +1,4 @@
 # RUN: not llvm-mc -triple i686-windows -filetype obj -o /dev/null %s
-# REQUIRES: asserts
 
 	.def first
 	.def second

llvm/test/MC/COFF/invalid-endef.s

@@ -1,5 +1,4 @@
 # RUN: not llvm-mc -triple i686-windows -filetype obj -o /dev/null %s
-# REQUIRES: asserts
 
 	.endef
 

llvm/test/MC/COFF/invalid-scl-range.s

@@ -1,5 +1,4 @@
 # RUN: not llvm-mc -triple i686-windows -filetype obj -o /dev/null %s
-# REQUIRES: asserts
 
 	.def storage_class_range
 		.scl 1337

llvm/test/MC/COFF/invalid-scl.s

@@ -1,5 +1,4 @@
 # RUN: not llvm-mc -triple i686-windows -filetype obj -o /dev/null %s
-# REQUIRES: asserts
 
 	.scl 1337
 

llvm/test/MC/COFF/invalid-type-range.s

@@ -1,5 +1,4 @@
 # RUN: not llvm-mc -triple i686-windows -filetype obj -o /dev/null %s
-# REQUIRES: asserts
 
 	.def invalid_type_range
 		.type 65536

llvm/test/MC/COFF/invalid-type.s

@@ -1,5 +1,4 @@
 # RUN: not llvm-mc -triple i686-windows -filetype obj -o /dev/null %s
-# REQUIRES: asserts
 
 	.type 65536