[Scalarizer] Fix potential for stale data in Scattered across invocations
authorMatt Wala <wala@google.com>
Fri, 12 Jun 2015 22:49:11 +0000 (22:49 +0000)
committerMatt Wala <wala@google.com>
Fri, 12 Jun 2015 22:49:11 +0000 (22:49 +0000)
commit1849093f7bd8590075e3df7a1a8263e2cb500f5d
treeed66986cb83158772a4ee4d5c29240e3d20ddee0
parent956bff827ad1ff19546cedce32a842efd7f81848
[Scalarizer] Fix potential for stale data in Scattered across invocations

Summary:
Scalarizer has two data structures that hold information about changes
to the function, Gathered and Scattered. These are cleared in finish()
at the end of runOnFunction() if finish() detects any changes to the
function.

However, finish() was checking for changes by only checking if
Gathered was non-empty. The function visitStore() only modifies
Scattered without touching Gathered. As a result, Scattered could have
ended up having stale data if Scalarizer only scalarized store
instructions. Since the data in Scattered is used during the execution
of the pass, this introduced dangling pointer errors.

The fix is to check whether both Scattered and Gathered are empty
before deciding what to do in finish().

Reviewers: srhines

Reviewed By: srhines

Subscribers: llvm-commits

Differential Revision: http://reviews.llvm.org/D10422

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@239644 91177308-0d34-0410-b5e6-96231b3b80d8
lib/Transforms/Scalar/Scalarizer.cpp