summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Fix broken FileCheck prefixesNico Rieck2014-05-235-14/+14
| | | | llvm-svn: 209538
* Add the extracted constant offset using GEPJingyue Wu2014-05-233-39/+80
| | | | | | | | | | | | | Fixed a TODO in r207783. Add the extracted constant offset using GEP instead of ugly ptrtoint+add+inttoptr. Using GEP simplifies future optimizations and makes IR easier to understand. Updated all affected tests, and added a new test in split-gep.ll to cover a corner case where emitting uglygep is necessary. llvm-svn: 209537
* [RuntimeDyld] Remove relocation bounds check introduced in r208375 (MachO only).Lang Hames2014-05-231-4/+1
| | | | | | | | | | | | | | | | | | | We do all of our address arithmetic in 64-bit, and operations involving logically negative 32-bit offsets (actually represented as unsigned 64 bit ints) often overflow into higher bits. The overflow check could be preserved by casting to uint32 at the callsite for applyRelocationValue, but this would eliminate the value of the check. The right way to handle overflow in relocations is to make relocation processing target specific, and compute the values for RelocationEntry objects in the appropriate types (32-bit for 32-bit targets, 64-bit for 64-bit targets). This is coming as part of the cleanup I'm working on. This fixes another i386 regression test. <rdar://problem/16889891> llvm-svn: 209536
* Stopgap fix for finding module for a file mapped in the VFSBen Langmuir2014-05-2312-4/+123
| | | | | | | | | | | | | | | | If we lookup a path using its 'real' path first, we need to ensure that when we run header search we still use the VFS-mapped path or we will not be able to find the corresponding module for the header. The real problem is that we tie the name of a file to its underlying FileEntry, which is uniqued by inode, so we only ever get the first name it is looked up by. This doesn't work with modules, which rely on a specific file system structure. I'm hoping to have time to write up a proposal for fixing this more permanently soon, but as a stopgap this patch updates the name of the file's directory if it comes from a VFS mapping. llvm-svn: 209534
* Add the hasRangeInit() matcher for range-based for loop.Manuel Klimek2014-05-232-0/+17
| | | | llvm-svn: 209533
* Test case for r209489.Akira Hatanaka2014-05-231-0/+13
| | | | llvm-svn: 209532
* Make dead return statement detection more robust against changes in the CFG.Manuel Klimek2014-05-231-21/+46
| | | | | | | | | | | | This change is a precondition to the proposed change to handle temporary dtors correctly. The idea is to explicitly search for the next return that doesn't have other paths into it (that is, if the current block is dead, the block containing the return must be dead, too). Thus, introducing non-control-flow block transitions will not break the logic. llvm-svn: 209531
* Make the ParentVector default to size 2.Manuel Klimek2014-05-231-1/+1
| | | | | | | As Jordan noted, it makes more sense when we store it in the ParentMap, and doesn't really make a difference when we return it from getParents. llvm-svn: 209530
* Add FIXME comment based on code review feedback by Hal Finkel on r209338David Blaikie2014-05-231-0/+2
| | | | llvm-svn: 209529
* Convert test to use FileCheck.Rafael Espindola2014-05-231-1/+5
| | | | llvm-svn: 209528
* revert "r209526 List the function/method name in the index page of scan-build "Sylvestre Ledru2014-05-232-17/+3
| | | | | | Depends on http://reviews.llvm.org/D3762 llvm-svn: 209527
* List the function/method name in the index page of scan-build Sylvestre Ledru2014-05-232-3/+17
| | | | llvm-svn: 209526
* [MS-ABI] Silence warning from r209523Warren Hunt2014-05-231-1/+1
| | | | | | no functional change. llvm-svn: 209525
* Replace system() by native perl callsSylvestre Ledru2014-05-232-12/+14
| | | | llvm-svn: 209524
* [MS-ABI] Implements MS-compatible RTTIWarren Hunt2014-05-239-47/+656
| | | | | | | | | | | | | Enables the emission of MS-compatible RTTI data structures for use with typeid, dynamic_cast and exceptions. Does not implement dynamic_cast or exceptions. As an artiface, typeid works in some cases but proper support an testing will coming in a subsequent patch. majnemer has fuzzed the results. Test cases included. Differential Revision: http://reviews.llvm.org/D3833 llvm-svn: 209523
* [sanitizer] Make stack traces from dlclose()'d modules more meaningful.Sergey Matveev2014-05-232-0/+48
| | | | | | | Previously, they silently omitted PCs belonging to unknown modules. Now we print (<unknown module>) instead. llvm-svn: 209522
* Teach the table generated emitPseudoExpansionLowering function to not emit a ↵Aaron Ballman2014-05-231-61/+65
| | | | | | switch statement containing only a default statement (and no cases). Updated some of the code to use range-based for loops as well. No functional changes. llvm-svn: 209521
* Fix bug 19840, where some tests were not testing what we wanted. Thanks to ↵Marshall Clow2014-05-232-12/+12
| | | | | | Eric for the bug report llvm-svn: 209520
* Aliases are always definition, delete dead code.Rafael Espindola2014-05-231-8/+2
| | | | | | While at it, use a range loop. llvm-svn: 209519
* Delete dead code.Rafael Espindola2014-05-231-4/+0
| | | | | | GV is never used past this point. This was probably a copy and paste error. llvm-svn: 209518
* [ubsan] temporary disable testing with -m32 as there are bots that don't ↵Kostya Serebryany2014-05-231-11/+11
| | | | | | support it llvm-svn: 209517
* [ubsan] handle long double in 32-bit mode; part of the patch by Marek PolacekKostya Serebryany2014-05-233-0/+24
| | | | llvm-svn: 209516
* [test] Force a triple in the pragma optimize test due to expected mangled names.Dario Domizioli2014-05-231-1/+1
| | | | | | | No functional change to the compiler. This should just make the test pass on all buildbots. llvm-svn: 209515
* [mips] Work around inconsistency in llvm-mc's placement of fixup markersDaniel Sanders2014-05-235-13/+82
| | | | | | | | | | | | | | | | | | | Summary: Add a second fixup table to MipsAsmBackend::getFixupKindInfo() to correctly position llvm-mc's fixup placeholders for big-endian. See PR19836 for full details of the issue. To summarize, the fixup placeholders do not account for endianness properly and the implementations of getFixupKindInfo() for each target are measuring MCFixupKindInfo.TargetOffset from different ends of the instruction encoding to compensate. Reviewers: jkolek, zoran.jovanovic, vmedic Reviewed By: vmedic Differential Revision: http://reviews.llvm.org/D3889 llvm-svn: 209514
* [mips][mips64r6] t(eq|ge|lt|ne)i and t(ge|lt)iu are not available in ↵Daniel Sanders2014-05-235-7/+49
| | | | | | | | | | | | | | MIPS32r6/MIPS64r6 Summary: Depends on D3872 Reviewers: jkolek, zoran.jovanovic, vmedic Reviewed By: vmedic Differential Revision: http://reviews.llvm.org/D3891 llvm-svn: 209513
* [mips][mips64r6] [ls][dw][lr] are not available in MIPS32r6/MIPS64r6Daniel Sanders2014-05-2315-143/+602
| | | | | | | | | | | | | | | | | | | | | | | | | | Summary: Instead the system is required to provide some means of handling unaligned load/store without special instructions. Options include full hardware support, full trap-and-emulate, and hybrids such as hardware support within a cache line and trap-and-emulate for multi-line accesses. MipsSETargetLowering::allowsUnalignedMemoryAccesses() has been configured to assume that unaligned accesses are 'fast' on the basis that I expect few hardware implementations will opt for pure-software handling of unaligned accesses. The ones that do handle it purely in software can override this. mips64-load-store-left-right.ll has been merged into load-store-left-right.ll The stricter testing revealed a Bits!=Bytes bug in passByValArg(). This has been fixed and the variables renamed to clarify the units they hold. Reviewers: zoran.jovanovic, jkolek, vmedic Reviewed By: vmedic Differential Revision: http://reviews.llvm.org/D3872 llvm-svn: 209512
* PR19352 - getLocation() points to the wrong position for FriendDeclsNikola Smiljanic2014-05-231-1/+3
| | | | llvm-svn: 209511
* Implemented support for "pragma clang optimize on/off", based on attribute ↵Dario Domizioli2014-05-2314-1/+319
| | | | | | | | | | | | | | | | 'optnone'. This patch implements support for selectively disabling optimizations on a range of function definitions through a pragma. The implementation is that all function definitions in the range are decorated with attribute 'optnone'. #pragma clang optimize off // All function definitions in here are decorated with 'optnone'. #pragma clang optimize on // Compilation resumes as normal. llvm-svn: 209510
* [asan] fix a test following r209508Kostya Serebryany2014-05-231-1/+3
| | | | llvm-svn: 209509
* [asan] properly instrument memory accesses that have small alignment ↵Kostya Serebryany2014-05-234-18/+44
| | | | | | (smaller than min(8,size)) by making two checks instead of one. This may slowdown some cases, e.g. long long on 32-bit or wide loads produced after loop unrolling. The benefit is higher sencitivity. llvm-svn: 209508
* Updated the llvm.mem.parallel_loop_access semantics to include the possibilityPekka Jaaskelainen2014-05-231-9/+23
| | | | | | | | | to have only some of the loop's memory instructions be annotated and still _help_ the loop carried dependence analysis. This was discussed in the llvmdev ML (topic: "parallel loop metadata question"). llvm-svn: 209507
* Fixup sys::getHostCPUFeatures crypto names so it doesn't clash with kernel ↵Bradley Smith2014-05-231-9/+9
| | | | | | headers llvm-svn: 209506
* clang-tidy: Only add 'override' before inlined bodies.Daniel Jasper2014-05-232-1/+5
| | | | llvm-svn: 209505
* [YAML] Add an optional argument `EnumMask` to the `yaml::IO::bitSetCase()`.Simon Atanasyan2014-05-234-19/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some bit-set fields used in ELF file headers in fact contain two parts. The first one is a regular bit-field. The second one is an enumeraion. For example ELF header `e_flags` for MIPS target might contain the following values: Bit-set values: EF_MIPS_NOREORDER = 0x00000001 EF_MIPS_PIC = 0x00000002 EF_MIPS_CPIC = 0x00000004 EF_MIPS_ABI2 = 0x00000020 Enumeration: EF_MIPS_ARCH_32 = 0x50000000 EF_MIPS_ARCH_64 = 0x60000000 EF_MIPS_ARCH_32R2 = 0x70000000 EF_MIPS_ARCH_64R2 = 0x80000000 For printing bit-sets we use the `yaml::IO::bitSetCase()`. It does not support bit-set/enumeration combinations and prints too many flags from an enumeration part. This patch fixes this problem. New method `yaml::IO::maskedBitSetCase()` handle "enumeration" part of bitset defined by provided mask. Patch reviewed by Nick Kledzik and Sean Silva. llvm-svn: 209504
* Fix '-main-file-name <name>' so that it is used for the ModuleID.Robert Lytton2014-05-232-1/+10
| | | | | | | | | Summary: Previously, you could not specify the original file name when passing a preprocessed file into the compiler Now you can use 'clang -Xclang -main-file-name -Xclang <original file name> ...' Or 'clang -cc1 -main-file-name <original file name> ...' llvm-svn: 209503
* Typedef NumeredTypesMapTy is not used anywhere.Yaron Keren2014-05-231-4/+0
| | | | llvm-svn: 209502
* Test commit.Jingyue Wu2014-05-231-1/+1
| | | | | | The keyword "virtual" is not necessary. llvm-svn: 209501
* llvm-ar: Output the file we errored on.Filipe Cabecinhas2014-05-232-1/+6
| | | | llvm-svn: 209500
* Rename a couple of variables to be more accurate.David Blaikie2014-05-231-8/+8
| | | | | | | | It's not really a "ScopeDIE", as such - it's the abstract function definition's DIE. And we usually use "SP" for subprograms, rather than "Sub". llvm-svn: 209499
* DebugInfo: Fix cross-CU references for scopes (and variables within those ↵David Blaikie2014-05-232-3/+10
| | | | | | | | scopes) in abstract definitions of cross-CU inlined functions Found by Adrian Prantl during post-commit review of r209335. llvm-svn: 209498
* Use short identifier.Rui Ueyama2014-05-231-7/+7
| | | | llvm-svn: 209497
* MC: remove unnecessary restriction on testsSaleem Abdulrasool2014-05-237-7/+0
| | | | | | | | | | Rafael correctly pointed out that the restriction is unnecessary. Although the tests are intended to ensure that we dont abort due to an assertion, running the tests in all modes is better since it also ensures that we dont crash without assertions. Always run these tests to ensure that we can handle invalid input correctly. llvm-svn: 209496
* [ARM64] Fix a bug in shuffle vector lowering to generate corect vext ISD ↵Jiangning Liu2014-05-232-15/+186
| | | | | | with swapped input vectors. llvm-svn: 209495
* Fixed the Symbol code to resolve the callable addressSean Callanan2014-05-233-27/+63
| | | | | | | | | | of the symbol itself rather than forcing clients to do it. This simplifies the logic for the expression parser a great deal. <rdar://problem/16935324> llvm-svn: 209494
* Instead of having an UnwindTable own a single assembly profiler, Jason Molenda2014-05-234-24/+40
| | | | | | | | | | | and sharing it with all of its FuncUnwinders, have each FuncUnwinder create an AssemblyProfiler on demand as needed. I was worried that the cost of creating the llvm disassemblers would be high for this approach but it's not supposed to be an expensive operation, and it means we don't need to add locks around this section of code. <rdar://problem/16992332> llvm-svn: 209493
* Revert r209488; Greg suggests a different approach.Jason Molenda2014-05-234-28/+13
| | | | llvm-svn: 209492
* Clean DiagRanges. Fix a possible problem introduced in r209468.Alexander Kornienko2014-05-231-0/+1
| | | | llvm-svn: 209491
* Attempt to placate compilers that warn on casts between pointer-to-object andRichard Smith2014-05-231-20/+20
| | | | | | pointer-to-function types. llvm-svn: 209490
* Fix a bug in xmmintrin.h.Akira Hatanaka2014-05-231-1/+1
| | | | | | | | | | The last step of _mm_cvtps_pi16 should use _mm_packs_pi32, which is a function that reads two __m64 values and packs four 32-bit values into four 16-bit values. <rdar://problem/16873717> llvm-svn: 209489
* The UnwindTable (one per module) used to hand out shared pointersJason Molenda2014-05-234-13/+28
| | | | | | | | | | | | | | | to its unwind assembly profiler to all of the FuncUnwinders (one per symbol) under it. If lldb is running multiple targets, you could get two different FuncUnwinders in the same Module trying to use the same llvm disassembler simultaneously and that may be a re-entrancy problem. Instead, the UnwindTable has the unwind assembly profiler and when the FuncUnwinders want to use it, they get exclusive access to the assembly profiler until they're done using it. <rdar://problem/16992332> llvm-svn: 209488
OpenPOWER on IntegriCloud