- Mar 19, 2013
-
-
Evgeniy Stepanov authored
llvm-svn: 177400
-
Rafael Espindola authored
If this should not happen, we should have an assert. If it should happen, we should have a test and remove the comment. In no case should we have this self inconsistent code. llvm-svn: 177399
-
Rafael Espindola authored
-no-integrated-as. It is the only assembler we have there. llvm-svn: 177398
-
Evgeniy Stepanov authored
llvm-svn: 177397
-
Alexey Samsonov authored
llvm-svn: 177396
-
Dmitry Vyukov authored
llvm-svn: 177395
-
Dmitry Vyukov authored
tsan: flush dead thread info earlier (when another thread is finished rather than new thread is created) llvm-svn: 177394
-
Dmitry Vyukov authored
llvm-svn: 177393
-
Alexey Samsonov authored
llvm-svn: 177392
-
Alexey Samsonov authored
llvm-svn: 177391
-
Dmitry Vyukov authored
llvm-svn: 177390
-
Dmitry Vyukov authored
llvm-svn: 177389
-
Dmitry Vyukov authored
llvm-svn: 177388
-
Dmitry Vyukov authored
llvm-svn: 177387
-
David Tweed authored
The testing to ensure a vector of zeros of type floating point isn't misclassified as negative zero can be simplified, as pointed out by Duncan Sands. llvm-svn: 177386
-
Alexey Samsonov authored
llvm-svn: 177385
-
Evgeniy Stepanov authored
llvm-svn: 177384
-
Evgeniy Stepanov authored
Moved this code to sanitizer_common. llvm-svn: 177383
-
Alexey Samsonov authored
llvm-svn: 177382
-
Dmitry Vyukov authored
helps to reduce memory consumption if an atomic is used only with relaxed ops (stats) llvm-svn: 177381
-
Renato Golin authored
The ARM backend currently has poor codegen for long sext/zext operations, such as v8i8 -> v8i32. This patch addresses this by performing a custom expansion in ARMISelLowering. It also adds/changes the cost of such lowering in ARMTTI. This partially addresses PR14867. Patch by Pete Couperus llvm-svn: 177380
-
Hal Finkel authored
llvm-svn: 177379
-
John McCall authored
we expect a related result type. rdar://12493140 llvm-svn: 177378
-
Andrew Trick authored
This reverts commit 82cd8f7382322bee7a71cdc31f7a923c44d37d32. Just add a comment instead! llvm-svn: 177377
-
Greg Clayton authored
- TestCase.m_thread is now filled in with the first thread that has a valid stop reason. This eliminates the need for the SelectMyThread() functions. - The first thread that stops for a reason is also set as the selected thread in the process in case any command line commands are run. - Changed launch over to take a SBLaunchInfo parameter so that the launch function doesn't keep getting new arguments as they are needed. - TestCase::Setup() and TestCase::Launch(SBLaunchInfo) now return bool to indicate success of setup and launch. - ActionWanted::Next(SBThread) was renamed to ActionWanted::StepOver(SBThread) - ActionWanted::Finish(SBThread) was renamed to ActionWanted::StepOut(SBThread) llvm-svn: 177376
-
Andrew Trick authored
Make the code more obvious to scan-build and humans. llvm-svn: 177375
-
Andrew Trick authored
No test case, but should fix a scan_build warning. llvm-svn: 177374
-
Sean Callanan authored
interpreter. They now have correct values, even when the process is not running. llvm-svn: 177372
-
Nick Lewycky authored
that we'll prefer to emit the mangled C++ name (pending a clang change). llvm-svn: 177371
-
Douglas Gregor authored
llvm-svn: 177370
-
Douglas Gregor authored
Minor optimization to r177367 to treat a module with missing dependencies as out-of-date rather than missing. llvm-svn: 177369
-
Rafael Espindola authored
The general pattern now is that Foobar::constructTool only creates tools defined in the tools::foobar namespace and then delegates to the parent. The remaining duplicated code is now in the tools themselves. llvm-svn: 177368
-
rdar://problem/13363214Douglas Gregor authored
<rdar://problem/13363214> Eliminate race condition between module rebuild and the global module index. The global module index was querying the file manager for each of the module files it knows about at load time, to prune out any out-of-date information. The file manager would then cache the results of the stat() falls used to find that module file. Later, the same translation unit could end up trying to import one of the module files that had previously been ignored by the module cache, but after some other Clang instance rebuilt the module file to bring it up-to-date. The stale stat() results in the file manager would trigger a second rebuild of the already-up-to-date module, causing failures down the line. The global module index now lazily resolves its module file references to actual AST reader module files only after the module file has been loaded, eliminating the stat-caching race. Moreover, the AST reader can communicate to its caller that a module file is missing (rather than simply being out-of-date), allowing us to simplify the module-loading logic and allowing the compiler to recover if a dependent module file ends up getting deleted. llvm-svn: 177367
-
Enrico Granata authored
This checkin removes the last Cocoa formatters that were implemented in Python and reimplements them in C++. The Python Cocoa formatters are not shipped as part of LLDB anymore, but still exist in the source repository for user reference. Python formatters still exist for STL classes and users can still define their own Python formatters llvm-svn: 177366
-
rdar://problem/13443931Greg Clayton authored
Fixed a crasher in the SourceManager where it wasn't checking the m_target member variable for NULL. In doing this fix, I hardened this class to have weak pointers to the debugger and target in case they do go away. I also changed SBSourceManager to hold onto weak pointers to the debugger and target so they don't keep objects alive by holding a strong reference to them. llvm-svn: 177365
-
Sean Callanan authored
and the JITted code are managed by a standalone class that handles memory management itself. I have removed RecordingMemoryManager and ProcessDataAllocator, which filled similar roles and had confusing ownership, with a common class called IRExecutionUnit. The IRExecutionUnit manages all allocations ever made for an expression and frees them when it goes away. It also contains the code generator and can vend the Module for an expression to other clases. The end goal here is to make the output of the expression parser re-usable; that is, to avoid re-parsing when re-parsing isn't necessary. I've also cleaned up some code and used weak pointers in more places. Please let me know if you see any leaks; I checked myself as well but I might have missed a case. llvm-svn: 177364
-
Richard Smith authored
llvm-svn: 177363
-
Richard Smith authored
it wasn't taking into account that the float should be truncated *before* the range check happens. Thus (unsigned)-0.99 and (unsigned char)255.9 have defined behavior and should not be trapped. llvm-svn: 177362
-
Hal Finkel authored
Don't sign extend the immediate value from the OR instruction in an LIS/OR pair. llvm-svn: 177361
-
Rafael Espindola authored
llvm-svn: 177360
-