- Feb 28, 2013
-
-
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
-
Tim Northover authored
The work done by the post-encoder (setting architecturally unused bits to 0 as required) can be done by the existing operand that covers the "#0.0". This removes at least one use of the discouraged PostEncoderMethod uses. llvm-svn: 176261
-
Daniel Jasper authored
Before: void aaaaaaaaaaaaaaaaaa() __attribute__( (aaaaaaaaaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaaaaaaaaaaa)); After: void aaaaaaaaaaaaaaaaaa() __attribute__((aaaaaaaaaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaaaaaaaaaaa)); llvm-svn: 176260
-
Tim Northover authored
If an otherwise weak var is actually defined in this unit, it can't be undefined at runtime so we can use normal global variable sequences (ADRP/ADD) to access it. llvm-svn: 176259
-
Tim Northover authored
llvm-svn: 176258
-
Bill Wendling authored
- Consistency with opt (which supports the same option with the same meaning and description). - Debugging gold plugin-based linking without optimizations getting in the way. - Debugging programs linked with the gold plugin while preserving the original debug info. - Fine-grained control over LTO passes using the gold plugin in combination with opt (or clang/dragonegg). Patch by Cristiano Giuffrida! llvm-svn: 176257
-
Alexander Potapenko authored
[ASan] Add the memcmp_strict flag (1 by default) that controls the behavior of accessibility checks in memcmp. 1: memcmp(p1, p2, n) always checks n bytes 0: memcmp checks up to n bytes depending on whether the memory contents differ. llvm-svn: 176256
-
Evgeniy Stepanov authored
llvm-svn: 176255
-
David Chisnall authored
llvm-svn: 176254
-
Tim Northover authored
llvm-svn: 176253
-
Daniel Jasper authored
Before: (a ->* f)() After: (a->*f)() llvm-svn: 176252
-
Manuel Klimek authored
This does not yet implement the LimitNode approach discussed. The impact of this is an O(n) in the number of nodes in the AST reduction of complexity for certain kinds of matchers (as otherwise the parent map gets recreated for every new MatchFinder). See FIXMEs in the comments for the direction of future work. llvm-svn: 176251
-
Kostya Serebryany authored
[asan] bump kMidMemEnd to 0x4fffffffffULL since in rare cases prelink uses addresses higher than 0x3fffffffff llvm-svn: 176250
-
Alexey Samsonov authored
[Sanitizer] Relax ThreadLister tests to allow possible pre-existing threads. Do proper mutex destruction. Patch by Sergey Matveev llvm-svn: 176249
-
Evgeniy Stepanov authored
llvm-svn: 176248
-
Evgeniy Stepanov authored
Shadow checks are disabled and memory loads always produce fully initialized values in functions that don't have a sanitize_memory attribute. Value and argument shadow is propagated as usual. This change also updates blacklist behaviour to match the above. llvm-svn: 176247
-