- Sep 05, 2013
-
-
Eric Christopher authored
we're proposing it for DWARF5. No functional change intended. llvm-svn: 190074
-
James Dennett authored
Summary: Closure classes for C++ lambdas are always compiler-generated. This one-line change calls setImplicit(true) on them at creation time, such that a default RecursiveASTVisitor (or any for which shouldVisitImplicitCode returns false) will skip them. Reviewers: rsmith, dblaikie Reviewed By: dblaikie CC: klimek, revane, cfe-commits, jordan_rose Differential Revision: http://llvm-reviews.chandlerc.com/D1593 llvm-svn: 190073
-
Fariborz Jahanian authored
code to work for bit 32bit and 64bit APIs. // rdar://14913632 llvm-svn: 190072
-
Hans Wennborg authored
We already use .obj as extension when the user provides a stem file name (via /Fo), but were failing in the most basic case when the file name is based on the input file. llvm-svn: 190071
-
Ed Maste authored
llvm-svn: 190070
-
Virgile Bello authored
OptionValueProperties::DeepCopy (): return empty value to avoid compilation error on MSVC (even if assert). llvm-svn: 190069
-
Virgile Bello authored
llvm-svn: 190068
-
Eric Christopher authored
llvm-svn: 190067
-
Virgile Bello authored
llvm-svn: 190066
-
Virgile Bello authored
llvm-svn: 190065
-
Eric Christopher authored
llvm-svn: 190064
-
Virgile Bello authored
llvm-svn: 190063
-
Virgile Bello authored
llvm-svn: 190062
-
Daniel Jasper authored
builds. llvm-svn: 190061
-
Joey Gouly authored
llvm-svn: 190060
-
Aaron Watry authored
Reviewed-By:
Aaron Watry <awatry@gmail.com> llvm-svn: 190059
-
Aaron Watry authored
Reviewed-by:
Aaron Watry <awatry@gmail.com> llvm-svn: 190058
-
Sylvestre Ledru authored
llvm-svn: 190057
-
Sylvestre Ledru authored
llvm-svn: 190056
-
Joey Gouly authored
This removes the custom ISD Node: MEMBARRIER and replaces it with an intrinsic. llvm-svn: 190055
-
Manuel Klimek authored
Before: enum X : int { A, B, C }; After: enum X : int { A, B, C }; llvm-svn: 190054
-
Richard Barton authored
These were pretty straightforward instructions, with some assembly support required for HLT. The ARM assembler is keen to split the instruction mnemonic into a (non-existent) 'H' instruction with the LT condition code. An exception for HLT is needed. HLT follows the same rules as BKPT when in IT blocks, so the special BKPT hadling code has been adapted to handle HLT also. Regression tests added including diagnostic tests for out of range immediates and illegal condition codes, as well as negative tests for pre-ARMv8. llvm-svn: 190053
-
Alexander Kornienko authored
Summary: Count column width instead of the number of code points. This also includes correct handling of tabs inside string literals and comments (with an exception of multiline string literals/comments, where tabs are present before the first escaped newline). Reviewers: djasper, klimek Reviewed By: klimek CC: cfe-commits, klimek Differential Revision: http://llvm-reviews.chandlerc.com/D1601 llvm-svn: 190052
-
Sylvestre Ledru authored
llvm-svn: 190051
-
Manuel Klimek authored
If transformations lead to changes that do not need reformatting, the current strategy will not write those files. With this patch, we just update the overall state with the changes due to reformatting, and then write out everything. llvm-svn: 190050
-
Alexander Kornienko authored
llvm-svn: 190049
-
Sylvestre Ledru authored
As a result, Clang doesn't define the pre-processor macros that are expected on this platform. Thanks to Robert Millan for the patch llvm-svn: 190048
-
Tilmann Scheller authored
Solution is not sufficient to prevent 'mov pc, lr' being emitted for jump table code. Test case doesn't trigger the added functionality. llvm-svn: 190047
-
Daniel Jasper authored
Before: constexpr char hello [] { "hello" }; After: constexpr char hello[]{ "hello" }; llvm-svn: 190046
-
Kostya Serebryany authored
llvm-svn: 190045
-
Stepan Dyatkovskiy authored
getRealTypeByWidth and getIntTypeByWidth for ASTContext names are almost same(invokes new methods from TargetInfo): getIntTypeForBitwidth and getRealTypeForBitwidth. As first commit for PR16752 fix: 'mode' attribute for unusual targets doesn't work properly Description: Troubles could be happened due to some assumptions in handleModeAttr function (see SemaDeclAttr.cpp). For example, it assumes that 32 bit integer is 'int', while it could be 16 bit only. Instead of asking target: 'which type do you want to use for int32_t ?' it just hardcodes general opinion. That doesn't looks pretty correct. Please consider the next solution: 1. In Basic/TargetInfo add getIntTypeByWidth and getRealTypeByWidth virtual methods. By default current behaviour could be implemented here. 2. Fix handleModeAttr according to new methods in TargetInfo. This approach is implemented in the patch attached to this post. Fixes: 1st Commit (Current): Add new methods for TargetInfo: getRealTypeByWidth and getIntTypeByWidth for ASTContext names are almost same(invokes new methods from TargetInfo): getIntTypeForBitwidth and getRealTypeForBitwidth 2nd Commit (Next): Fix SemaDeclAttr, handleModeAttr function. llvm-svn: 190044
-
Tilmann Scheller authored
This improves code generation for jump tables by avoiding the emission of "mov pc, lr" which could fool the processor into believing this is a return from a function causing mispredicts. The code generation logic for jump tables uses ADR to materialize the address of the jump target. Patch by Daniel Stewart! llvm-svn: 190043
-
Daniel Jasper authored
Mostly additional comments :-). llvm-svn: 190042
-
Richard Sandiford authored
For now these are just used to handle scalar ANDs, ORs and XORs in which all operands are memory. llvm-svn: 190041
-
Chandler Carruth authored
it works in the CL flavor driver. llvm-svn: 190040
-
Daniel Jasper authored
Before: void f() { other(x.begin(), x.end(), // [&](int, int) { return 1; }); } After: void f() { other(x.begin(), x.end(), // [&](int, int) { return 1; }); } llvm-svn: 190039
-
Daniel Jasper authored
Among other things, this enables (better) formatting lambdas and constructs like: MACRO({ long_statement(); long_statement_2(); }, { long_statement(); long_statement_2(); }, { short_statement(); }, ""); This fixes llvm.org/PR15381. llvm-svn: 190038
-
Pavel Labath authored
Summary: I've had a test failure here while experimenting and I've found that it's impossible to find what is wrong with the previous structure of the file. So I have grouped the expected output with the function that produces it, to make searching for discrepancies more obvious. Reviewers: jordan_rose CC: cfe-commits Differential Revision: http://llvm-reviews.chandlerc.com/D1595 llvm-svn: 190037
-
Manuel Klimek authored
as this is going to be a common mistake (installing LLVM defaults to not putting the tools onto the PATH). llvm-svn: 190036
-
Nick Lewycky authored
llvm-svn: 190035
-