emscripten-fastcomp/test/CodeGen/X86/memset.ll, branch 1.13.2LLVM with the emscripten fastcomp javascript backendhttps://git.amat.us/emscripten-fastcomp/atom/test/CodeGen/X86/memset.ll?h=1.13.22013-02-25T14:20:21ZFix the root cause of PR15348 by correctly handling alignment 0 on2013-02-25T14:20:21ZChandler Carruthchandlerc@gmail.com2013-02-25T14:20:21Zurn:sha1:af23f8e403d68e3f96eb5eb63e50e3aec4ea01c9
memory intrinsics in the SDAG builder.
When alignment is zero, the lang ref says that *no* alignment
assumptions can be made. This is the exact opposite of the internal API
contracts of the DAG where alignment 0 indicates that the alignment can
be made to be anything desired.
There is another, more explicit alignment that is better suited for the
role of "no alignment at all": an alignment of 1. Map the intrinsic
alignment to this early so that we don't end up generating aligned DAGs.
It is really terrifying that we've never seen this before, but we
suddenly started generating a large number of alignment 0 memcpys due to
the new code to do memcpy-based copying of POD class members. That patch
contains a bug that rounds bitfield alignments down when they are the
first field. This can in turn produce zero alignments.
This fixes weird crashes I've seen in library users of LLVM on 32-bit
hosts, etc.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176022 91177308-0d34-0410-b5e6-96231b3b80d8
llvm/test/CodeGen/X86/memset.ll: FileCheck-ize, and add another case on +avx.2012-11-14T21:01:40ZNAKAMURA Takumigeek4civic@gmail.com2012-11-14T21:01:40Zurn:sha1:9292136787725acbfd2c644ae8705610e45d548e
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167975 91177308-0d34-0410-b5e6-96231b3b80d8
Force CPU in test so we don't accidentally get AVX code on an AVX-capable host.2012-11-14T20:31:42ZBenjamin Kramerbenny.kra@googlemail.com2012-11-14T20:31:42Zurn:sha1:7c6e8cd7cc98b898141acb2b038b894dd11d3537
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167973 91177308-0d34-0410-b5e6-96231b3b80d8
rip out a ton of intrinsic modernization logic from AutoUpgrade.cpp, which is2011-06-18T06:05:24ZChris Lattnersabre@nondot.org2011-06-18T06:05:24Zurn:sha1:b85e4eba85a38698f3b3332f82554bf8442547e2
for pre-2.9 bitcode files. We keep x86 unaligned loads, movnt, crc32, and the
target indep prefetch change.
As usual, updating the testsuite is a PITA.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@133337 91177308-0d34-0410-b5e6-96231b3b80d8
Eliminate more uses of llvm-as and llvm-dis.2009-09-08T23:54:48ZDan Gohmangohman@apple.com2009-09-08T23:54:48Zurn:sha1:36a0947820fd4aa4b8a5fa26e3f079bdf572bc81
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@81290 91177308-0d34-0410-b5e6-96231b3b80d8
The Linux ABI emits an extra "movl %esp, %ebp" in function prologue and2008-05-26T20:18:56ZNick Lewyckynicholas@mxc.ca2008-05-26T20:18:56Zurn:sha1:3978927dfa6b88bde400e71f14154dc16bb8536b
sometimes a "mov %ebp, %esp" in the epilogue.
Force these tests that rely on counting 'mov' to use i686-apple-darwin8.8.0
where they were written.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@51568 91177308-0d34-0410-b5e6-96231b3b80d8
Add a couple of test cases.2008-05-22T21:19:19ZEvan Chengevan.cheng@apple.com2008-05-22T21:19:19Zurn:sha1:d86323efc9b107ad560cd3f7f9150f67d20b213c
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@51441 91177308-0d34-0410-b5e6-96231b3b80d8