David Blaikie 615f63e149 Revert "[FastISel] Flush local value map on ever instruction" and dependent patches
This reverts commit cf1c774d6ace59c5adc9ab71b31e762c1be695b1.

This change caused several regressions in the gdb test suite - at least
a sample of which was due to line zero instructions making breakpoints
un-lined. I think they're worth investigating/understanding more (&
possibly addressing) before moving forward with this change.

Revert "[FastISel] NFC: Clean up unnecessary bookkeeping"
This reverts commit 3fd39d3694d32efa44242c099e923a7f4d982095.

Revert "[FastISel] NFC: Remove obsolete -fast-isel-sink-local-values option"
This reverts commit a474657e30edccd9e175d92bddeefcfa544751b2.

Revert "Remove static function unused after cf1c774."
This reverts commit dc35368ccf17a7dca0874ace7490cc3836fb063f.

Revert "[lldb] Fix TestThreadStepOut.py after "Flush local value map on every instruction""
This reverts commit 53a14a47ee89dadb8798ca8ed19848f33f4551d5.
2020-12-01 14:26:23 -08:00

43 lines
920 B
C++

// This test is intended to create a situation in which two threads are stopped
// at a breakpoint and the debugger issues a step-out command.
#include "pseudo_barrier.h"
#include <thread>
pseudo_barrier_t g_barrier;
volatile int g_test = 0;
void step_out_of_here() {
g_test += 5; // Set breakpoint here
}
void *
thread_func ()
{
// Wait until both threads are running
pseudo_barrier_wait(g_barrier);
// Do something
step_out_of_here(); // Expect to stop here after step-out (clang)
// Return
return NULL; // Expect to stop here after step-out (icc and gcc)
}
int main ()
{
// Don't let either thread do anything until they're both ready.
pseudo_barrier_init(g_barrier, 2);
// Create two threads
std::thread thread_1(thread_func);
std::thread thread_2(thread_func);
// Wait for the threads to finish
thread_1.join();
thread_2.join();
return 0;
}