just because we're being told to evaluate it twice. This sometimes happens when a variable is evaluated again during codegen.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
I keep trying to find some way to test this change... and instead, I've filed several new crashing issues in the issue tracker. The changes look correct to me despite the lack of a test, but if anyone else can dream up some way to tell a ctor is being called twice instead of once, that would be great. If not, LGTM otherwise.