- Jul 24, 2013
-
-
Craig Topper authored
Fix aliases for shrd/shld to handle Intel syntax properly. Also suppress them from being used by the asm printer. llvm-svn: 187020
-
Akira Hatanaka authored
Similar to ARM change r182800, dynamic linker will read bits/addends from the original object rather than from the object that might have been patched previously. For the purpose of relocations for MCJIT stubs on MIPS, we internally use otherwise unused MIPS relocations. The change also enables MCJIT unit tests for MIPS (EL/BE), and the following two tests now pass: - MCJITTest.return_global and - MCJITTest.multiple_functions. These issues have been tracked as Bug 16250. Patch by Petar Jovanovic. llvm-svn: 187019
-
Eric Christopher authored
to assume we're replacing. Clarify comments. llvm-svn: 187018
-
Eric Christopher authored
llvm-svn: 187017
-
Manman Ren authored
llvm-svn: 187016
-
Eric Christopher authored
all enumerated cases. Reformat the rest of the existing constructors to match. llvm-svn: 187015
-
Eric Christopher authored
Move to a single constructor with a default argument and avoid the check and nullification. llvm-svn: 187014
-
Eric Christopher authored
llvm-svn: 187013
-
Eric Christopher authored
llvm-svn: 187012
-
Eric Christopher authored
llvm-svn: 187011
-
Eric Christopher authored
llvm-svn: 187010
-
Eric Christopher authored
llvm-svn: 187009
-
Fariborz Jahanian authored
instancetype of NSDictionary methods. llvm-svn: 187008
-
Tom Stellard authored
This commit also implements these functions for R600 and removes a test case that was relying on the buggy behavior. llvm-svn: 187007
-
Tom Stellard authored
These are really the same address space in hardware. The only difference is that CONSTANT_ADDRESS uses a special cache for faster access. When we are unable to use the constant kcache for some reason (e.g. smaller types or lack of indirect addressing) then the instruction selector must use GLOBAL_ADDRESS loads instead. llvm-svn: 187006
-
Nick Kledzik authored
llvm-svn: 187005
-
Fariborz Jahanian authored
instancetype methods. llvm-svn: 187004
-
Manman Ren authored
Improve the Finder to handle context of a DIVariable. If Scope is a DICompileUnit, add it to the list of CUs. llvm-svn: 187003
-
Manman Ren authored
llvm-svn: 187002
-
Eric Christopher authored
llvm-svn: 187001
-
Fariborz Jahanian authored
instancetype migration. llvm-svn: 187000
-
Quentin Colombet authored
When vectors are built from a single value, the ARM lowering issues a scalar_to_vector node. This node is then always morphed into a move from the general purpose unit to the vector unit. When the value comes from a load, this can be simplified into a vector load to the right lane. This patch changes the lowering of insert_vector_elt to expose a vector friendly pattern in this situation. This is a step toward fixing <rdar://problem/14170854>. llvm-svn: 186999
-
Eric Christopher authored
llvm-svn: 186998
-
Matt Arsenault authored
llvm-svn: 186997
-
Nick Kledzik authored
llvm-svn: 186996
-
Eric Christopher authored
llvm-svn: 186995
-
Eric Christopher authored
llvm-svn: 186994
-
Bill Schmidt authored
The 64-bit PowerPC ELF ABI requires a struct that contains a single vector member to be passed in a vector register as though the wrapping struct were not present. Instead we were passing this as a byval struct. The same logic was already present for floating-point arguments, so this patch just extends the logic to handle vector types. The new test case verifies that clang coerces the parameter and annotates it as inreg. Thanks, Bill llvm-svn: 186993
-
Matt Kopec authored
llvm-svn: 186992
-
Howard Hinnant authored
unordered_set, however it is not complete yet for unordered_multiset, unordered_map or unordered_multimap. There has been a lot of work done for these other three containers, however that work was done just to keep all of the tests passing. You can try this out with -D_LIBCPP_DEBUG2. You will have to link to a libc++.dylib that has been compiled with src/debug.cpp. So far, vector (but not vector<bool>), list, and unordered_set are treated. I hope to get the other three unordered containers up fairly quickly now that unordered_set is done. The flag _LIBCPP_DEBUG2 will eventually be changed to _LIBCPP_DEBUG, but not today. This is my second effort at getting debug mode going for libc++, and I'm not quite yet ready to throw all of the work under the first attempt away. The basic design is that all of the debug information is kept in a central database, instead of in the containers. This has been done as an attempt to have debug mode and non-debug mode be ABI compatible with each other. There are some circumstances where if you construct a container in an environment without debug mode and pass it into debug mode, the checking will get confused and let you know with a readable error message. Passing containers the other way: from debug mode out to a non-debugging mode container should be 100% safe (at least that is the goal). llvm-svn: 186991
-
- Jul 23, 2013
-
-
Stefanus Du Toit authored
If we are replacing a function with the nobuiltin attribute, it may be called with the builtin attribute on call sites. Remove any such attributes since it's illegal to have a builtin call to something other than a nobuiltin function. This fixes the current buildbot breakage (where LLDB crashes on "expression new foo(42)"). llvm-svn: 186990
-
Hans Wennborg authored
The help text was wrong, and we already provide help text on the option that actually changes anything, i.e. -fdiagnostics-show-note-include-stack. llvm-svn: 186989
-
Richard Trieu authored
llvm-svn: 186988
-
Eli Bendersky authored
llvm-svn: 186987
-
Eli Bendersky authored
Run in two different modes: with and without reopening the temporary file between creating it and mapping it with MemoryBuffer. llvm-svn: 186986
-
Manman Ren authored
Use getNodeField to access a field as a MDNode. No functionality change. llvm-svn: 186985
-
Rafael Espindola authored
The main observation is that we never need both the filesize and the map size. When mapping a slice of a file, it doesn't make sense to request a null terminator and that would be the only case where the filesize would be used. There are other cleanups that should be done in this area: * A client should not have to pass the size (even an explicit -1) to say if it wants a null terminator or not, so we should probably swap the argument order. * The default should be to not require a null terminator. Very few clients require this, but many end up asking for it just because it is the default. llvm-svn: 186984
-
Rafael Espindola authored
llvm-svn: 186983
-
Aaron Ballman authored
Removing a number of individual run lines and replacing them with single line test cases. This reduces the number of test runs, provides the same coverage, and allows us to test that the attribute names are included in the diagnostic. llvm-svn: 186982
-
Fariborz Jahanian authored
which are candidate for migrating to 'instancetype'. wip. llvm-svn: 186981
-