SuccessChanges

Summary

  1. [ScriptInterpreter] Remove ScriptInterpreterPythonImpl::Clear() (NFC) (details)
  2. [Timers] Fix printing some `-ftime-report` sections twice. Fixes (details)
  3. [ScriptInterpreter] Limit LLDB's globals to interactive mode. (details)
  4. TestFoundationDisassembly.py is not dependent on debug information. (details)
  5. Cache PYTHON_EXECUTABLE for windows (details)
  6. [Remarks] Allow the RemarkStreamer to be used directly with a stream (details)
  7. Clean up this test. (details)
  8. [X86] Prevent assertion when calling a function that returns double with (details)
Commit abb3d13778f7a93ae43f6fe906a06923e93a3350 by Jonas Devlieghere
[ScriptInterpreter] Remove ScriptInterpreterPythonImpl::Clear() (NFC)
This method is never called.
llvm-svn: 372190
The file was modifiedlldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h
The file was modifiedlldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
Commit 6e353b4df3aa452ed4741a5e5caea02b1a876d8c by vsapsai
[Timers] Fix printing some `-ftime-report` sections twice. Fixes
PR40328.
Starting from r324788 timer groups aren't cleared automatically when
printed out. As a result some timer groups were printed one more time.
For example, "Pass execution timing report" was printed again in
`ManagedStatic<PassTimingInfo>` destructor, "DWARF Emission" in
`ManagedStatic<Name2PairMap> NamedGroupedTimers` destructor.
Fix by clearing timer groups manually.
Reviewers: thegameg, george.karpenkov
Reviewed By: thegameg
Subscribers: aprantl, jkorous, dexonsmith, ributzka, aras-p, cfe-commits
Differential Revision: https://reviews.llvm.org/D67683
llvm-svn: 372191
The file was modifiedclang/tools/driver/cc1as_main.cpp
The file was modifiedclang/tools/driver/driver.cpp
The file was modifiedclang/tools/driver/cc1_main.cpp
Commit 20b52c33ba3960340ecf326314517091b8ec98f4 by Jonas Devlieghere
[ScriptInterpreter] Limit LLDB's globals to interactive mode.
Jim pointed out that the LLDB global variables should only be available
in interactive mode. When used from a command for example, their values
might be stale or not at all what the user expects. Therefore we want to
explicitly make these variables unavailable.
Differential revision: https://reviews.llvm.org/D67685
llvm-svn: 372192
The file was modifiedlldb/packages/Python/lldbsuite/test/commands/frame/recognizer/recognizer.py
The file was modifiedlldb/lit/Commands/command-script-import.test
The file was modifiedlldb/lit/Commands/Inputs/frame.py
The file was modifiedlldb/packages/Python/lldbsuite/test/python_api/sbvalue_const_addrof/main.cpp
The file was modifiedlldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
Commit f547cf12ee5764708ef70778a0acf3683e8c24f9 by jingham
TestFoundationDisassembly.py is not dependent on debug information.
This test is about disassembling symbols in a framework without debug
information. So we don't need to run it once per debug info flavor.
llvm-svn: 372193
The file was modifiedlldb/packages/Python/lldbsuite/test/lang/objc/foundation/TestFoundationDisassembly.py
Commit 5f8a3270ae74d84599dc09c581c2a417d4bbfb5e by hhb
Cache PYTHON_EXECUTABLE for windows
Summary: This way it can be overwritten when cross compiling.
Subscribers: mgorny, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D67641
llvm-svn: 372194
The file was modifiedlldb/cmake/modules/LLDBConfig.cmake
Commit ba2e752c520b4ba31c30846269f8331cc217054f by francisvm
[Remarks] Allow the RemarkStreamer to be used directly with a stream
The filename in the RemarkStreamer should be optional to allow clients
to stream remarks to memory or to existing streams.
This introduces a new overload of `setupOptimizationRemarks`, and avoids
enforcing the presence of a filename at different places.
llvm-svn: 372195
The file was modifiedllvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp
The file was modifiedllvm/include/llvm/IR/RemarkStreamer.h
The file was modifiedllvm/lib/IR/RemarkStreamer.cpp
Commit d6cad39316359a8bebac830350b1d190ce9b0cee by jingham
Clean up this test.
I don't know what the intent of parts of this test were.  We set a bunch
of breakpoints and ran from one to the other, doing "self.runCmd("thread
backtrace")" then continuing to the next one.  We didn't actually verify
the contents of the backtrace, nor that we hit the breakpoints we set in
any particular order.  The only actual test was to run sel_getName at
two of these stops.
So I reduced the test to just stopping at the places where we were
actually going to run an expression, and tested the expression.
llvm-svn: 372196
The file was modifiedlldb/packages/Python/lldbsuite/test/lang/objc/foundation/TestObjCMethods2.py
Commit 4a07336a886d6fa908ee19d72abe0ecb3732b377 by craig.topper
[X86] Prevent assertion when calling a function that returns double with
-mno-sse2 on x86-64.
As seen in the most recent updates to PR10498
llvm-svn: 372197
The file was addedclang/test/CodeGen/x86_64-mno-sse2.c
The file was modifiedllvm/lib/Target/X86/X86ISelLowering.cpp