Commit b1dd7f7c by Antonio Maiorano

Workaround for ReactorUnitTests.LargeStack taking too long on LLVM

Disable the InstructionCombiningPass and O2 optimization level to make ReactorUnitTests.LargeStack take only a few seconds to run. Otherwise, it would take 6 minutes on my desktop workstation. Bug: b/174031014 Change-Id: I88fb240fe1ba6dcf822a8ff70bb595a4c3f3aa01 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/50710 Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by: 's avatarAlexis Hétu <sugoi@google.com> Tested-by: 's avatarAntonio Maiorano <amaiorano@google.com>
parent b17161ab
...@@ -1280,7 +1280,15 @@ TEST(ReactorUnitTests, LargeStack) ...@@ -1280,7 +1280,15 @@ TEST(ReactorUnitTests, LargeStack)
} }
} }
auto routine = function("one"); // LLVM takes very long to generate this routine when InstructionCombining
// and O2 optimizations are enabled. Disable for now.
// TODO(b/174031014): Remove this once we fix LLVM taking so long
auto cfg = Config::Edit{}
.remove(Optimization::Pass::InstructionCombining)
.set(Optimization::Level::None);
auto routine = function(cfg, "one");
std::array<int32_t, ArraySize> v; std::array<int32_t, ArraySize> v;
// Run this in a thread, so that we get the default reserved stack size (8K on Win64). // Run this in a thread, so that we get the default reserved stack size (8K on Win64).
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment