llvm-project/llvm/test/CodeGen/X86/mul-remat.ll

; RUN: llc < %s -mtriple=i686-- | grep mov | count 1
; PR1874
	
define i32 @test(i32 %a, i32 %b) {
entry:
	%tmp3 = mul i32 %b, %a
	ret i32 %tmp3
}
X86: Do not use llc -march in tests. `llc -march` is problematic because it only switches the target architecture, but leaves the operating system unchanged. This occasionally leads to indeterministic tests because the OS from LLVM_DEFAULT_TARGET_TRIPLE is used. However we can simply always use `llc -mtriple` instead. This changes all the tests to do this to avoid people using -march when they copy and paste parts of tests. See also the discussion in https://reviews.llvm.org/D35287 llvm-svn: 309774 2017-08-02 08:28:10 +08:00			`; RUN: llc < %s -mtriple=i686-- \| grep mov \| count 1`
Don't mark scalar integer multiplication as Expand on x86, since x86 has plain one-result scalar integer multiplication instructions. This avoids expanding such instructions into MUL_LOHI sequences that must be special-cased at isel time, and avoids the problem with that code that provented memory operands from being folded. This fixes PR1874, addressesing the most common case. The uncommon cases of optimizing multiply-high operations will require work in DAGCombiner. llvm-svn: 47277 2008-02-19 01:55:26 +08:00			`; PR1874`

			`define i32 @test(i32 %a, i32 %b) {`
			`entry:`
			`%tmp3 = mul i32 %b, %a`
			`ret i32 %tmp3`
			`}`