Mark asm tests as requiring LLVM 10.0.1

[Amanieu]

No description provided.

[rust-highfive]

r? @Mark-Simulacrum

(rust-highfive has picked a reviewer for you, use r? to override)

[Amanieu]

Inline asm requires LLVM 10.0.1 but the Ubuntu package is only 10.0.0. Unfortunate.

[Amanieu]

I've added proper LLVM version annotations to the tests so they should be enabled automatically when we do the next LLVM version bump.

[joshtriplett]

@bors r+

[bors]

📌 Commit 62e7331 has been approved by joshtriplett

[infinity0]

Should codegen/alloc-optimisation.rs really have been shifted away from no-system-llvm? If I understand correctly it depends on rust-specific changes to LLVM regarding knowledge about how malloc works. The test fails on all Debian architectures like this:

------------------------------------------
stderr:
------------------------------------------
/<<PKGBUILDDIR>>/src/test/codegen/alloc-optimisation.rs:10:17: error: CHECK-NEXT: is not on the line after the previous match
 // CHECK-NEXT: ret void
                ^
/<<PKGBUILDDIR>>/build/x86_64-unknown-linux-gnu/test/codegen/alloc-optimisation/alloc-optimisation.ll:25:2: note: 'next' match was here
 ret void
 ^
/<<PKGBUILDDIR>>/build/x86_64-unknown-linux-gnu/test/codegen/alloc-optimisation/alloc-optimisation.ll:11:7: note: previous match ended here
start:
      ^
/<<PKGBUILDDIR>>/build/x86_64-unknown-linux-gnu/test/codegen/alloc-optimisation/alloc-optimisation.ll:12:1: note: non-matching line after previous match is here
 %0 = tail call i8* @__rust_alloc(i64 4, i64 4) #2
^

Input file: /<<PKGBUILDDIR>>/build/x86_64-unknown-linux-gnu/test/codegen/alloc-optimisation/alloc-optimisation.ll
Check file: /<<PKGBUILDDIR>>/src/test/codegen/alloc-optimisation.rs

-dump-input=help explains the following input dump.

Input was:
<<<<<<
         .
         .
         .
        20: 
        21: "_ZN5alloc5boxed12Box$LT$T$GT$3new17haf7fc1520aeaf056E.exit": ; preds = %start
        22:  %2 = bitcast i8* %0 to i32*
        23:  store i32 %data, i32* %2, align 4
        24:  tail call void @__rust_dealloc(i8* nonnull %0, i64 4, i64 4) #2
        25:  ret void
next:10      !~~~~~~~ error: match on wrong line
        26: }
        27: 
        28: ; Function Attrs: nounwind nonlazybind uwtable
        29: declare i32 @rust_eh_personality(i32, i32, i64, %"unwind::libunwind::_Unwind_Exception"*, %"unwind::libunwind::_Unwind_Context"*) unnamed_addr #0
        30: 
         .
         .
         .
>>>>>>

------------------------------------------

[Amanieu]

Oh yea that's definitely a mistake. Rust's LLVM has a custom patch to recognize __rust_alloc as an allocation function like malloc, but this patch isn't in upstream LLVM.