- Nov 19, 2013
-
-
Arnold Schwaighofer authored
llvm-svn: 195161
-
Aaron Ballman authored
llvm-svn: 195160
-
Rui Ueyama authored
This should improve code readability as the class definitions are now more readable than before. llvm-svn: 195159
-
Warren Hunt authored
Microsoft adds an extra byte of padding before laying out zero sized non-virtual bases if the non-virtual base before it contains a vbptr. This patch adds the same behavior to clang. Differential Revision: http://llvm-reviews.chandlerc.com/D2106 llvm-svn: 195158
-
Petar Jovanovic authored
Instead of processing relocation for branch to stubs right away, emit a modified relocation and add it to queue to be resolved later when final load address is known. This resolves seven MIPS MCJIT issues that were caused by missing relocation fixups at the end. llvm-svn: 195157
-
Juergen Ributzka authored
Reviewed by Tom llvm-svn: 195156
-
Rafael Espindola authored
The object files we support use null terminated strings, so there is no way to support these. This patch adds an assert to catch bad API use and an error check in the .ll parser. llvm-svn: 195155
-
Rafael Espindola authored
The previous patches tried to deduce the correct function type. I now realize this is not possible in general. Consider class foo { template <typename T> static void bar(T v); }; extern template void foo::bar(const void *); We will only know that bar is static after a lookup, so we have to handle this in the template instantiation code. This patch reverts my previous two changes (but not the tests) and instead handles the issue in DeduceTemplateArguments. llvm-svn: 195154
-
Yuchen Wu authored
llvm-svn: 195153
-
Jack Carter authored
llvm-svn: 195152
-
Yuchen Wu authored
Added constness to methods that shouldn't modify objects. Replaced operator[] lookup in maps with find() instead. llvm-svn: 195151
-
Benjamin Kramer authored
llvm-svn: 195150
-
Jim Grosbach authored
Make sure armv7 doesn't get the iOS deployment version definitions when it's being used for non-iOS. rdar://15497681 llvm-svn: 195149
-
Rafael Espindola authored
This is the first step to fix pr17918. It extends the .section directive a bit, inspired by what the ELF one looks like. The problem with using linkonce is that given .section foo .linkonce.... .section foo .linkonce we would already have switched sections when getting to .linkonce. The cleanest solution seems to be to add the comdat information in the .section itself. llvm-svn: 195148
-
Dmitri Gribenko authored
llvm-svn: 195147
-
Fariborz Jahanian authored
property is redeclared as 'weak' in class extension. // rdar://15465916 llvm-svn: 195146
-
Dmitri Gribenko authored
llvm-svn: 195145
-
Marshall Clow authored
llvm-svn: 195144
-
Marshall Clow authored
llvm-svn: 195143
-
Andrew Trick authored
Caught by Aaron Ballman. llvm-svn: 195138
-
Fariborz Jahanian authored
'Deprecated' name suffix. llvm-svn: 195137
-
Marshall Clow authored
Patch by Bruce Mitchener. Change all references to EMSCRIPTEN to __EMSCRIPTEN__. If you're not using the PP symbol EMSCRIPTEN, then you should see no functionality change. llvm-svn: 195136
-
Fariborz Jahanian authored
'objc_bridge' attribute. // rdar://15454846. llvm-svn: 195135
-
John Thompson authored
YAML I/O - Added default trait support for std:string. Making another attempt at this, this time doing a clean build on Linux, and running the LLVM, clang, and extra tests, to try to make sure there's no problems. llvm-svn: 195134
-
Dmitry Vyukov authored
actually use the passed size llvm-svn: 195133
-
Alexander Potapenko authored
(-Wl,-syslibroot was accidentally overridden by -isysroot from Clang on OSX 10.9) -isysroot is a Clang/LLVM-GCC-specific option, but hosting libsanitizer for LLVM with GCC on Darwin shouldn't work anyway, because of the missing blocks support. llvm-svn: 195132
-
Kostya Serebryany authored
llvm-svn: 195131
-
Evgeniy Stepanov authored
llvm-svn: 195130
-
Cameron McInally authored
llvm-svn: 195129
-
Alexander Kornienko authored
Summary: Pure refactoring, no semantic changes intended. Reviewers: klimek Reviewed By: klimek CC: cfe-commits, klimek Differential Revision: http://llvm-reviews.chandlerc.com/D2220 llvm-svn: 195128
-
Samuel Benzaquen authored
Summary: Change VariadicOperatorMatcherInterface<> to take an ArrayRef<DynTypedMatcher>. This simplifies its implementation and use. Also reduces the number of symbols in Registry.cpp.o, which we are always in need. Reviewers: klimek CC: cfe-commits, revane, klimek Differential Revision: http://llvm-reviews.chandlerc.com/D2216 llvm-svn: 195127
-
Joerg Sonnenberger authored
llvm-svn: 195126
-
Alexander Potapenko authored
if the iOS Simulator SDK is missing on the machine. llvm-svn: 195125
-
Simon Atanasyan authored
should be isolated in the backend (r195123). From the frontend point of view in case of "-mhard-float -mips16" combination of flags the float ABI mode should remain unchanged. The patch reviewed by Reed Kotler. llvm-svn: 195124
-
Simon Atanasyan authored
Hard float for mips16 means essentially to compile as soft float but to use a runtime library for soft float that is written with native mips32 floating point instructions (those runtime routines run in mips32 hard float mode). The patch reviewed by Reed Kotler. llvm-svn: 195123
-
Eric Christopher authored
llvm-svn: 195122
-
Eric Christopher authored
llvm-svn: 195121
-
Eric Christopher authored
we can emit various sections in any order. No functional change. llvm-svn: 195120
-
Eric Christopher authored
llvm-svn: 195119
-
Chandler Carruth authored
order of slices of the alloca which have exactly the same size and other properties. This was found by a perniciously unstable sort implementation used to flush out buggy uses of the algorithm. The fundamental idea is that findCommonType should return the best common type it can find across all of the slices in the range. There were two bugs here previously: 1) We would accept an integer type smaller than a byte-width multiple, and if there were different bit-width integer types, we would accept the first one. This caused an actual failure in the testcase updated here when the sort order changed. 2) If we found a bad combination of types or a non-load, non-store use before an integer typed load or store we would bail, but if we found the integere typed load or store, we would use it. The correct behavior is to always use an integer typed operation which covers the partition if one exists. While a clever debugging sort algorithm found problem #1 in our existing test cases, I have no useful test case ideas for #2. I spotted in by inspection when looking at this code. llvm-svn: 195118
-