- Mar 01, 2013
-
-
Daniel Malea authored
- if you have LLDB checked out in $llvm/tools, CMake will build it now! - LLDB is known to build on Linux with libstdc++ and GCC 4.6/4.7 or Clang 3.3 - to run lldb tests, do "make check-lldb" after a build llvm-svn: 176307
-
Daniel Malea authored
- add missing scripts (driver, tests, etc...) - enable running of tests from cmake with "make check-lldb" target - fix up problem with clang dependencies (this enables parallel builds) - implement platform-specific FIXMEs in source/CMakeLists.txt llvm-svn: 176306
-
Eli Bendersky authored
SelectionDAGIsel::LowerArguments needs a function, not a basic block. So it makes sense to pass it the function instead of extracting a basic-block from the function and then tossing it. This is also more self-documenting (functions have arguments, BBs don't). In addition, added comments to a couple of Select* methods. llvm-svn: 176305
-
- Feb 28, 2013
-
-
Bill Wendling authored
These can be easily queried by the back-end. llvm-svn: 176304
-
Fariborz Jahanian authored
use of stand-alone protocol as type and uses id<proto>. Modify warning to say what compiler is doing. // rdar//13158394 llvm-svn: 176303
-
Enrico Granata authored
llvm-svn: 176302
-
Bill Wendling authored
This was causing the folding set to fail to fold attributes, because it was being calculated in one spot without an empty values string but here with an empty values string. llvm-svn: 176301
-
Quentin Colombet authored
The instcombine recognized pattern looks like: a = b * c d = a +/- Cst or a = b * c d = Cst +/- a When creating the new operands for fadd or fsub instruction following the related fmul, the first operand was created with the second original operand (M0 was created with C1) and the second with the first (M1 with Opnd0). The fix consists in creating the new operands with the appropriate original operand, i.e., M0 with Opnd0 and M1 with C1. llvm-svn: 176300
-
Shankar Easwaran authored
llvm-svn: 176298
-
Eric Christopher authored
our bitwise compare is equal to the field we're looking for. Noticed on inspection. llvm-svn: 176296
-
Edwin Vane authored
Some buildbots use a shell that doesn't know 'exit'. So instead of using XFAIL for UseAuto/iterator.cpp (since this problem doesn't exist for cmake) leave the 'grep' command and turn off the others. llvm-svn: 176295
-
Michael J. Spencer authored
llvm-svn: 176294
-
Edwin Vane authored
The way 'make check-all' causes configuration files to be generated results in the cpp11-migrate/Makefile not being triggered to generated any files. These files are necessary for UseAuto/iterator.cpp to run. Turning off this test until the problem is fixed properly. llvm-svn: 176293
-
Benjamin Kramer authored
llvm-svn: 176292
-
Jim Ingham authored
at a time. Enforce this for now (we should relax the requirement when we have a little more time.) <rdar://problem/13314462> llvm-svn: 176291
-
Bill Wendling authored
llvm-svn: 176289
-
Chad Rosier authored
llvm-svn: 176288
-
Benjamin Kramer authored
We make the cost for calling libm functions extremely high as emitting the calls is expensive and causes spills (on x86) so performance suffers. We still vectorize important calls like ceilf and friends on SSE4.1. and fabs. Differential Revision: http://llvm-reviews.chandlerc.com/D466 llvm-svn: 176287
-
John McCall authored
calls and declarations. LLVM has a default CC determined by the target triple. This is not always the actual default CC for the ABI we've been asked to target, and so we sometimes find ourselves annotating all user functions with an explicit calling convention. Since these calling conventions usually agree for the simple set of argument types passed to most runtime functions, using the LLVM-default CC in principle has no effect. However, the LLVM optimizer goes into histrionics if it sees this kind of formal CC mismatch, since it has no concept of CC compatibility. Therefore, if this module happens to define the "runtime" function, or got LTO'ed with such a definition, we can miscompile; so it's quite important to get this right. Defining runtime functions locally is quite common in embedded applications. llvm-svn: 176286
-
Chad Rosier authored
llvm-svn: 176285
-
Greg Clayton authored
llvm-svn: 176283
-
Greg Clayton authored
Fix the getCompilerVersion() function to do the right thing with clang 5.0 which now says "LLVM version" instead of "clang version". llvm-svn: 176282
-
Greg Clayton authored
llvm-svn: 176281
-
Shankar Easwaran authored
llvm-svn: 176280
-
Shankar Easwaran authored
llvm-svn: 176279
-
Shankar Easwaran authored
llvm-svn: 176278
-
Shankar Easwaran authored
llvm-svn: 176277
-
Hans Wennborg authored
llvm-svn: 176276
-
Manuel Klimek authored
llvm-svn: 176275
-
Greg Clayton authored
Also removed the use of llvm::raw_string_ostream as it wasn't needed. Also fixed a crasher that could occur when the following line returned a C string tied to a local variable: return OS.str().c_str(); I am guessing "static std::string buf;" was supposed to get assigned to "OS.str()" and then have "buf.c_str()" returned. Modified the non-apple version code to cache its value and not recompute the version every time. llvm-svn: 176274
-
Eli Bendersky authored
other per-instruction statistics. llvm-svn: 176273
-
Fariborz Jahanian authored
llvm-svn: 176272
-
Fariborz Jahanian authored
have their own code completion comments. Use those in their properties in this case. // rdar://12791315 llvm-svn: 176271
-
Yiannis Tsiouris authored
llvm-svn: 176270
-
Daniel Malea authored
llvm-svn: 176269
-
Daniel Malea authored
- make LLDB version number match Clang (and the Debian package) - use the same revision detection magic that Clang uses to report SVN/Git revisions - update test case as per above Example output: $ lldb -v lldb version 3.3 (https://dmalea@llvm.org/svn/llvm-project/lldb/trunk revision 176211 clang revision 176208 llvm revision 176208) ss This line, and those below, will be ignored-- M source/lldb.cpp M test/help/TestHelp.py M source/Makefile llvm-svn: 176268
-
Dmitri Gribenko authored
Patch by Ariel Bernal. llvm-svn: 176267
-
Edwin Vane authored
The new Use-Auto transform replaces the type specifier for variable declarations with the special C++11 'auto' type specifier. For now, the replacement is done only for variables that are iterators of any of the std containers and only if the type used is one of those explicitly allowed by the standard (i.e. not an implementation-specific type). Reviewers: gribozavr, silvas, klimek llvm-svn: 176266
-
Evgeniy Stepanov authored
llvm-svn: 176264
-
Daniel Jasper authored
This fixes llvm.org/PR15379. Before: const uint8_t aaaaaaaaaaaaaaaaaaaaaa[0] = { 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // comment 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // comment 0x00, 0x00, 0x00, 0x00 // comment }; After: const uint8_t aaaaaaaaaaaaaaaaaaaaaa[0] = { 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // comment 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // comment 0x00, 0x00, 0x00, 0x00 // comment }; llvm-svn: 176262
-