- Mar 08, 2016
-
-
Hans Wennborg authored
Apparently this makes my email address easier to find. llvm-svn: 262951
-
Saleem Abdulrasool authored
Add a missing include. This is important in the case HandleLLVMOptions is included prior to the missing CheckCXXSourceCompiles or CheckCXXCompilerFlag which includes CheckCXXSourceCompiles. llvm-svn: 262949
-
Chris Bieneman authored
This adds llvm_add_implicit_projects which takes a project name and is wrapped by add_llvm_implicit_projects. llvm-svn: 262948
-
Chad Rosier authored
llvm-svn: 262944
-
Quentin Colombet authored
The fix consisting in using the library call for atomic compare and swap when the instruction is not safe to use may be incorrect. Indeed the library call may not exist on all platform. In other words, we need a better fix! llvm-svn: 262943
-
Chad Rosier authored
Test to be committed in follow up commit, per discussion in D17097. http://reviews.llvm.org/D17097 llvm-svn: 262942
-
Sanjay Patel authored
llvm-svn: 262940
-
Krzysztof Parzyszek authored
This was inadvertently omitted from r262774, which added the mutation interface. llvm-svn: 262939
-
Sanjay Patel authored
llvm-svn: 262937
-
Artyom Skrobov authored
Reviewers: t.p.northover, grosbach, resistor Subscribers: aemerson, rengolin, llvm-commits Differential Revision: http://reviews.llvm.org/D17636 llvm-svn: 262936
-
Hans Wennborg authored
This caused PR26870. llvm-svn: 262935
-
Manuel Klimek authored
llvm-svn: 262934
-
Krzysztof Parzyszek authored
llvm-svn: 262930
-
Igor Breger authored
Differential Revision: http://reviews.llvm.org/D17953 llvm-svn: 262929
-
Benjamin Kramer authored
llvm-svn: 262926
-
Filipe Cabecinhas authored
Summary: I left --build-system for backwards compat, in case there are scripts using it. Feel free to ask for its removal too. Reviewers: chapuni, tstellarAMD Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D17886 llvm-svn: 262924
-
Simon Pilgrim authored
llvm-svn: 262919
-
Junmo Park authored
This commit removes pr25342 for reverting r262670 clearly. llvm-svn: 262918
-
Junmo Park authored
This reverts commit r262670 due to compile failure. llvm-svn: 262916
-
Justin Bogner authored
Should fix the breakage in r262902. llvm-svn: 262908
-
Peter Collingbourne authored
llvm-svn: 262907
-
Kit Barton authored
We follow the comments mentioned in http://reviews.llvm.org/D16842#344378 to implement this new patch. This patch implements the following vsx instructions: Vector load/store: lxv lxvx lxvb16x lxvl lxvll lxvh8x lxvwsx stxv stxvb16x stxvh8x stxvl stxvll stxvx Scalar load/store: lxsd lxssp lxsibzx lxsihzx stxsd stxssp stxsibx stxsihx 21 instructions Phabricator: http://reviews.llvm.org/D16919 llvm-svn: 262906
-
Dan Gohman authored
Also note that the operand order changed; the default label is now listed after the regular labels. llvm-svn: 262903
-
Justin Bogner authored
This re-applies r262886 with a fix for 32 bit platforms that have 8 byte pointer alignment, effectively reverting r262892. Original Message: Currently some SDNode operands are malloc'd, some are stored inline in subclasses of SDNode, and some are thrown into a BumpPtrAllocator. This scheme is complex, inconsistent, and makes refactoring SDNodes fairly difficult. Instead, we can allocate all of the operands using an ArrayRecycler that wraps a BumpPtrAllocator. This keeps the cache locality when iterating operands, improves locality when iterating SDNodes without looking at operands, and vastly simplifies the ownership semantics. It also means we stop overallocating SDNodes by 2-3x and will make it simpler to fix the rampant undefined behaviour we have in how we mutate SDNodes from one kind to another (See llvm.org/pr26808). This is NFC other than the changes in memory behaviour, and I ran some LNT tests to make sure this didn't hurt compile time. Not many tests changed: there were a couple of 1-2% regressions reported, but there were more improvements (of up to 4%) than regressions. llvm-svn: 262902
-
Quentin Colombet authored
Thanks to Ahmed Bougacha for noticing! llvm-svn: 262899
-
Quentin Colombet authored
llvm-svn: 262898
-
Quentin Colombet authored
llvm-svn: 262897
-
Quentin Colombet authored
llvm-svn: 262896
-
Quentin Colombet authored
llvm-svn: 262893
-
Justin Bogner authored
Looks like the largest SDNode is different between 32 and 64 bit now, so this is breaking 32 bit bots. Reverting while I figure out a fix. This reverts r262886. llvm-svn: 262892
-
Richard Smith authored
llvm-svn: 262891
-
Quentin Colombet authored
By complex types, I mean aggregate or vector types. llvm-svn: 262890
-
Justin Bogner authored
Currently some SDNode operands are malloc'd, some are stored inline in subclasses of SDNode, and some are thrown into a BumpPtrAllocator. This scheme is complex, inconsistent, and makes refactoring SDNodes fairly difficult. Instead, we can allocate all of the operands using an ArrayRecycler that wraps a BumpPtrAllocator. This keeps the cache locality when iterating operands, improves locality when iterating SDNodes without looking at operands, and vastly simplifies the ownership semantics. It also means we stop overallocating SDNodes by 2-3x and will make it simpler to fix the rampant undefined behaviour we have in how we mutate SDNodes from one kind to another (See llvm.org/pr26808). This is NFC other than the changes in memory behaviour, and I ran some LNT tests to make sure this didn't hurt compile time. Not many tests changed: there were a couple of 1-2% regressions reported, but there were more improvements (of up to 4%) than regressions. llvm-svn: 262886
-
Quentin Colombet authored
Before this change, we would get the type definition in the middle of the instruction. E.g., %0(48) = G_ADD %struct_alias = type { i32, i16 } %edi, %edi Now, we have just the expected type name: %0(48) = G_ADD %struct_alias %edi, %edi llvm-svn: 262885
-
Quentin Colombet authored
Without actually parsing a type it is difficult to perdict where the type definition ends. In other words, instead of expecting the user of the parser API to hand over only the relevant bits of the string being parsed, take the whole string, parse the type, and get back the number of characters that have been read. This will be used by the MIR testing infrastructure. llvm-svn: 262884
-
Easwaran Raman authored
llvm-svn: 262883
-
Quentin Colombet authored
llvm-svn: 262880
-
Quentin Colombet authored
llvm-svn: 262879
-
Quentin Colombet authored
llvm-svn: 262878
-
Quentin Colombet authored
llvm-config can know tell whether or not a build has been configured to support global-isel. Use '--has-global-isel' for that. llvm-svn: 262877
-