- Jun 05, 2013
-
-
Arnold Schwaighofer authored
Reapply of 183258. llvm-svn: 183321
-
Pavel Labath authored
Summary: This adds two command-line parameters: -extra-arg and -extra-arg-before, which enable the user to pass additional parameters to the compiler command. Reviewers: klimek CC: cfe-commits Differential Revision: http://llvm-reviews.chandlerc.com/D919 llvm-svn: 183320
-
Arnold Schwaighofer authored
Add some generic SchedWrites and assign resources for Swift and Cortex A9. Reapply of r183257. (Removed empty InstRW for division on swift) llvm-svn: 183319
-
Reid Kleckner authored
Also addresses a review comment from John from on r180985 by removing the "== -1" check, since it's now reusing the correct code which has the comment. llvm-svn: 183318
-
Benjamin Kramer authored
llvm-svn: 183317
-
Matt Kopec authored
llvm-svn: 183316
-
Alexander Kornienko authored
llvm-svn: 183315
-
Arnold Schwaighofer authored
An instruction with less than 3 inputs is trivially a fast immediate shift. Reapply of 183256, should not have caused the tablegen segfault on linux either. llvm-svn: 183314
-
Ashok Thirumurthi authored
- Ensures that this container is populated once for the lifetime of lldb --- In particular, static methods can query this data even after the first RegisterContext has been destroyed. - Uses a singleton function to avoid global constructors. Thanks to Greg Clayton for the suggestion! llvm-svn: 183313
-
Alexander Kornienko authored
Summary: Detect if the file is valid UTF-8, and if this is the case, count code points instead of just using number of bytes in all (hopefully) places, where number of columns is needed. In particular, use the new FormatToken.CodePointCount instead of TokenLength where appropriate. Changed BreakableToken implementations to respect utf-8 character boundaries when in utf-8 mode. Reviewers: klimek, djasper Reviewed By: djasper CC: cfe-commits, rsmith, gribozavr Differential Revision: http://llvm-reviews.chandlerc.com/D918 llvm-svn: 183312
-
Arnold Schwaighofer authored
Don't output data if we are supposed to ignore the record. Reapply of 183255, I don't think this was causing the tablegen segfault on linux testers. llvm-svn: 183311
-
Timur Iskhodzhanov authored
Recommit r183298+r183300 'Get rid of VTableContext::ComputeMethodVTableIndices() and VTableContext::getNumVirtualFunctionPointers()' In r183298, I've used llvm::SmallPtrSet<..., 8> instead of llvm::SmallVector<..., 8> for NewVirtualFunctionsTy by mistake. This only manifested when a class had more than 8 virtual functions, which wasn't covered by unit-tests llvm-svn: 183310
-
Timur Iskhodzhanov authored
llvm-svn: 183309
-
Timur Iskhodzhanov authored
llvm-svn: 183308
-
Mihai Popa authored
According to the ARM reference manual, RRX(S) have defined encodings for lr, pc and sp. llvm-svn: 183307
-
Timur Iskhodzhanov authored
llvm-svn: 183306
-
Timur Iskhodzhanov authored
llvm-svn: 183305
-
Alexander Kornienko authored
Make clang tools ignore -fcolor-diagnostics and -fdiagnostics-color retrieved from the compilation database. Summary: Clang tools' diagnostic output could be force colored when a command line from the compilation database contains -fcolor-diagnostics or -fdiagnostics-color. This is not what we want e.g. for vim integration. Reviewers: klimek Reviewed By: klimek CC: cfe-commits, revane, jordan_rose Differential Revision: http://llvm-reviews.chandlerc.com/D917 llvm-svn: 183304
-
Sylvestre Ledru authored
The GNU/HURD is also using the libc. Therefor, endian.h should be included, not machine/endian.h. See full build log https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-3.3&arch=hurd-i386&ver=1%3A3.3~%2Brc3-1~exp1&stamp=1370358869 llvm-svn: 183303
-
Andrew Trick authored
This fixes some of the ridiculously complex code for optimizing the machine model tables that are shared among all processors of a given target. A9 and Swift both use the "special" feature that maps old itinerary classes to new machine model defs. They map different overlapping subsets of instructions, which wasn't handled correctly. llvm-svn: 183302
-
NAKAMURA Takumi authored
MS extensions don't prefer imaginary suffix even with -std=c++11. llvm-svn: 183301
-
David Blaikie authored
llvm-svn: 183300
-
Timur Iskhodzhanov authored
llvm-svn: 183299
-
Timur Iskhodzhanov authored
Get rid of VTableContext::ComputeMethodVTableIndices() and VTableContext::getNumVirtualFunctionPointers(); also add some tests for the VTable indices output to make sure we don't regress llvm-svn: 183298
-
David Blaikie authored
When a function is inlined we lazily construct the variables representing the function's parameters. After that, we add any remaining unused parameters. If the function doesn't use all the parameters, or uses them out of order, then the DWARF would produce them in that order, producing a parameter order that doesn't match the source. This fix causes us to always keep the arg variables at the start of the variable list & in the original order from the source. llvm-svn: 183297
-
David Blaikie authored
In an effort to make -flimit-debug-info more consistent I over-shot the mark & made types used via typedefs never produce definitions in the debug info (even if the type was used in a way that would require a definition). The fix for this is to do exactly what I was hoping to do at some point - plumb the declaration/definition choice through the various layers of "CreateType" in CGDebugInfo. In this way we can produce declarations whenever they are sufficient & definitions otherwise - including when qualifiers are used, for example (discovered in PR14467). This may not be complete (there may be other types/situations where we need to propagate the "declaration/definition" choice) but it lays the basic foundation which we can enhance in future iterations. llvm-svn: 183296
-
Rafael Espindola authored
Patch by Matthew Dempsky. llvm-svn: 183295
-
Tom Stellard authored
Reviewed-by: vljn at ovi.com llvm-svn: 183294
-
Rafael Espindola authored
llvm-svn: 183293
-
Jakob Stoklund Olesen authored
This could actually be implemented with the LLVM IR va_arg instruction, but it doesn't seem to offer any advantages over accessing the va_list pointer directly. Using the va_list pointer directly makes it possible to perform type coercion directly from the argument array, and the va_list updates are exposed to the optimizers. llvm-svn: 183292
-
Jakob Stoklund Olesen authored
Type coercion for argument passing is equivalent to storing the source type and loading the destination type from the same pointer. On big-endian targets, this means that the high bits of integers are preserved. This patch fixes the CoerceIntOrPtrToIntOrPtr() function on big-endian targets by inserting the required shift instructions to preserve the high bits instead of the low bits. This is used by SparcABIInfo when passing small structs in the high bits of registers. llvm-svn: 183291
-
Jakob Stoklund Olesen authored
The 'inreg' attribute can also be applied to function return values in LLVM IR. The SPARC v9 backend is using the flag when returning structs containing 32-bit floats. llvm-svn: 183290
-
Jason Molenda authored
Print the lldb version at the top of the output. llvm-svn: 183289
-
Rafael Espindola authored
Should fix the MCJIT tests on PPC. llvm-svn: 183288
-
Rafael Espindola authored
It will be used for ELF dumping too. llvm-svn: 183287
-
Rafael Espindola authored
This reverts commit r183279. CodeGen/R600/texture-input-merge.ll was failing. llvm-svn: 183286
-
Rafael Espindola authored
llvm-svn: 183285
-
Rafael Espindola authored
In ELF (as in MachO), not all relocations point to symbols. Represent this properly by using a symbol_iterator instead of a SymbolRef. Update llvm-readobj ELF's dumper to handle relocatios without symbols. llvm-svn: 183284
-
Richard Smith authored
handle temporaries which have been lifetime-extended to static storage duration within constant expressions. This correctly handles nested lifetime extension (through reference members of aggregates in aggregate initializers) but non-constant-expression emission hasn't yet been updated to do the same. llvm-svn: 183283
-
Jason Molenda authored
the link register save location being in the link register - in which case we should iterate down the stack, not recursively try to find the lr in the current frame over and over. <rdar://problem/13932954> llvm-svn: 183282
-