[UBSan] Disable one run line of this test to allow the test as a whole
to pass in an opt build. The test case in question does show UBSan catching the error, but it doesn't then successfully set the exit code of the program. I'll let the UBSan folks sort out why. It should reproduce trivially with an optimized build. llvm-svn: 219563
This commit is contained in:
		
							parent
							
								
									bff0ae772c
								
							
						
					
					
						commit
						30bdfa7f99
					
				| 
						 | 
					@ -9,7 +9,7 @@
 | 
				
			||||||
// RUN: %run %t 5 2>&1 | FileCheck %s --check-prefix=CHECK-5
 | 
					// RUN: %run %t 5 2>&1 | FileCheck %s --check-prefix=CHECK-5
 | 
				
			||||||
// RUN: %run %t 6 2>&1 | FileCheck %s --check-prefix=CHECK-6
 | 
					// RUN: %run %t 6 2>&1 | FileCheck %s --check-prefix=CHECK-6
 | 
				
			||||||
// FIXME: %run %t 7 2>&1 | FileCheck %s --check-prefix=CHECK-7
 | 
					// FIXME: %run %t 7 2>&1 | FileCheck %s --check-prefix=CHECK-7
 | 
				
			||||||
// RUN: not %run %t 8 2>&1 | FileCheck %s --check-prefix=CHECK-8
 | 
					// FIXME: not %run %t 8 2>&1 | FileCheck %s --check-prefix=CHECK-8
 | 
				
			||||||
// RUN: not %run %t 9 2>&1 | FileCheck %s --check-prefix=CHECK-9
 | 
					// RUN: not %run %t 9 2>&1 | FileCheck %s --check-prefix=CHECK-9
 | 
				
			||||||
 | 
					
 | 
				
			||||||
// This test assumes float and double are IEEE-754 single- and double-precision.
 | 
					// This test assumes float and double are IEEE-754 single- and double-precision.
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in New Issue