- Nov 29, 2012
-
-
-
Jakob Stoklund Olesen authored
Use this type for arrays of physical registers. llvm-svn: 168850
-
Shuxin Yang authored
Approved by: Eli and Michael. llvm-svn: 168848
-
Richard Smith authored
performed, to determine whether that special member is deleted or constexpr. That overload resolution process can in turn trigger the instantiation of a template, which can do anything, including triggering the declaration of that very same special member function. When this happens, do not try to recursively declare the special member -- that's impossible. Instead, only try to realise the truth. There is no special member. llvm-svn: 168847
-
-
rdar://problem/12445557Greg Clayton authored
Make stack frames fix up their line table entries when the target has source remappings. Also rearranged how the m_sc.target_sp was filled in so it can be used during the StackFrame::GetSymbolContext(...) function. llvm-svn: 168845
-
Sean Callanan authored
versions of UnknownAnyTy for ObjectiveC value types. <unknown type>* makes no sense and can cause the parser to behave very oddly. <rdar://problem/12518999> llvm-svn: 168844
-
Ted Kremenek authored
Correctly handle IntegralToBool casts in C++ in the static analyzer. Fixes <rdar://problem/12759044>. llvm-svn: 168843
-
Chad Rosier authored
rdar://12771737 llvm-svn: 168841
-
Jim Ingham authored
Add an example of using the target.process.extra-startup-command to turn on debugserver logging since we always forget how to do this... llvm-svn: 168840
-
Jim Ingham authored
the frame and then getting the run lock. Which means that our frame could have gotten invalidated by stopping between the time we got the frame and assured the the target was stopped. Now we get the run lock first, and THEN resolve the underlying frame object. <rdar://problem/12621607> llvm-svn: 168838
-
Jakob Stoklund Olesen authored
This could cause miscompilations in targets where sub-register composition is not always idempotent (ARM). <rdar://problem/12758887> llvm-svn: 168837
-
Daniel Malea authored
- fixes gcc 4.6 build problems - resolves open bugzilla http://llvm.org/bugs/show_bug.cgi?id=13889 llvm-svn: 168835
-
Jason Molenda authored
<rdar://problem/12769073> llvm-svn: 168834
-
Nick Lewycky authored
Also a couple not-user-visible changes; using empty() instead of size(), and make inSection() not insert NULL Regex*'s into StringMap when doing a lookup. llvm-svn: 168833
-
Nadav Rotem authored
llvm-svn: 168832
-
Daniel Malea authored
Linux buildbot fix: detect swig tool from PATH in shell script (before searching hardcoded directories) llvm-svn: 168831
-
Bill Wendling authored
delete those as well. llvm-svn: 168829
-
Daniel Malea authored
llvm-svn: 168827
-
Michael Han authored
Implement C++11 [dcl.attr.grammar] p4: If an attribute-specifier-seq appertains to a friend declaration, that declaration shall be a definition. llvm-svn: 168826
-
Fariborz Jahanian authored
in deciding a copy/dispose field is needed in a byref structure and when generating the copy/dispose helpers. In certain cases, these fields were being added but no copy/dispose was being generated. This was uncovered in ARC, but not in MRR. // rdar://12759433 llvm-svn: 168825
-
- Nov 28, 2012
-
-
Richard Smith authored
llvm-svn: 168824
-
Richard Smith authored
decayed to a pointer type. Patch by WenHan Gu, with a little tweaking and additional testcases by me. llvm-svn: 168822
-
Manman Ren authored
rdar://12723368 llvm-svn: 168821
-
Manman Ren authored
the original parameter or return type. Since we do not accurately represent the data fields of a union, we should not directly load or store a union type. As an exmple, if we have i8,i8, i32, i32 as one field type and i32,i32 as another field type, the first field type will be chosen to represent the union. If we load with the union's type, the 3rd byte and the 4th byte will be skipped. rdar://12723368 llvm-svn: 168820
-
Richard Smith authored
determine which member function would be the callee from within the template definition, don't pass that function as a "non-member function" to CreateOverloadedBinOp. Instead, just rely on it to select the member function for itself. llvm-svn: 168818
-
Dmitri Gribenko authored
llvm-svn: 168817
-
Michael Ilseman authored
llvm-svn: 168816
-
Michael Ilseman authored
llvm-svn: 168815
-
Michael Ilseman authored
llvm-svn: 168814
-
Michael Ilseman authored
Also extended IRBuilder's documentation to mention the convenience state for DefaultFPMathTag and FastMathFlags that can be set. llvm-svn: 168812
-
Michael Ilseman authored
llvm-svn: 168811
-
Jyotsna Verma authored
llvm-svn: 168810
-
Benjamin Kramer authored
Fixes 14337. llvm-svn: 168809
-
Jim Ingham authored
llvm-svn: 168807
-
Jakob Stoklund Olesen authored
No functional change, just moved header files. Targets can inject custom passes between register allocation and rewriting. This makes it possible to tweak the register allocation before rewriting, using the full global interference checking available from LiveRegMatrix. llvm-svn: 168806
-
Jordan Rose authored
Also, minor whitespace/indentation fixes. Patch by Peeter Joot! llvm-svn: 168805
-
Jordan Rose authored
Part of PR14443. llvm-svn: 168804
-
Eli Bendersky authored
appropriate unit tests. This change in itself is not expected to affect any functionality at this point, but it will serve as a stepping stone to improve FileCheck's variable matching capabilities. Luckily, our regex implementation already supports backreferences, although a bit of hacking is required to enable it. It supports both Basic Regular Expressions (BREs) and Extended Regular Expressions (EREs), without supporting backrefs for EREs, following POSIX strictly in this respect. And EREs is what we actually use (rightly). This is contrary to many implementations (including the default on Linux) of POSIX regexes, that do allow backrefs in EREs. Adding backref support to our EREs is a very simple change in the regcomp parsing code. I fail to think of significant cases where it would clash with existing things, and can bring more versatility to the regexes we write. There's always the danger of a backref in a specially crafted regex causing exponential matching times, but since we mainly use them for testing purposes I don't think it's a big problem. [it can also be placed behind a flag specific to FileCheck, if needed]. For more details, see: * http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-November/055840.html * http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20121126/156878.html llvm-svn: 168802
-
Benjamin Kramer authored
Unbreaks the CMake shared library build. This is nasty and should be fixed eventually. llvm-svn: 168800
-