[LLVMbugs] [Bug 23008] New: New error: "Use still stuck around after Def is destroyed: %.sroa.speculated"

[bugzilla-daemon at llvm.org]

https://llvm.org/bugs/show_bug.cgi?id=23008

            Bug ID: 23008
           Summary: New error: "Use still stuck around after Def is
                    destroyed:  %.sroa.speculated"
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: hans at chromium.org
                CC: james.molloy at arm.com, llvmbugs at cs.uiuc.edu,
                    nicolasweber at gmx.de
    Classification: Unclassified

This started with r233062.


$ ./skbitmap_operations-5fa857.sh 
While deleting: double %add
Use still stuck around after Def is destroyed:  %.sroa.speculated = select i1
%cmp.i137, double %add, double 2.550000e+02, !dbg !5099
clang: ../lib/IR/Value.cpp:82: virtual llvm::Value::~Value(): Assertion
`use_empty() && "Uses remain when a value is destroyed!"' failed.
#0 0x15888aa llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x15888aa)
#1 0x158a1cb SignalHandler(int)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x158a1cb)
#2 0x7f40efccc340 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x10340)
#3 0x7f40eeeedcc9 gsignal
/build/buildd/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c:56:0
#4 0x7f40eeef10d8 abort /build/buildd/eglibc-2.19/stdlib/abort.c:91:0
#5 0x7f40eeee6b86 __assert_fail_base
/build/buildd/eglibc-2.19/assert/assert.c:92:0
#6 0x7f40eeee6c32 (/lib/x86_64-linux-gnu/libc.so.6+0x2fc32)
#7 0x126ba30 llvm::ValueHandleBase::ValueIsDeleted(llvm::Value*)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x126ba30)
#8 0x1230609 llvm::BinaryOperator::~BinaryOperator()
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x1230609)
#9 0x142c33d (anonymous namespace)::Float2Int::runOnFunction(llvm::Function&)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x142c33d)
#10 0x123fdcc llvm::FPPassManager::runOnFunction(llvm::Function&)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x123fdcc)
#11 0x124000b llvm::FPPassManager::runOnModule(llvm::Module&)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x124000b)
#12 0x1240507 llvm::legacy::PassManagerImpl::run(llvm::Module&)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x1240507)
#13 0x19d4c43 clang::EmitBackendOutput(clang::DiagnosticsEngine&,
clang::CodeGenOptions const&, clang::TargetOptions const&, clang::LangOptions
const&, llvm::StringRef, llvm::Module*, clang::BackendAction,
llvm::raw_ostream*)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x19d4c43)
#14 0x19c5375 clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x19c5375)
#15 0x1f71af3 clang::ParseAST(clang::Sema&, bool, bool)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x1f71af3)
#16 0x17284fe clang::FrontendAction::Execute()
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x17284fe)
#17 0x16f7f6c clang::CompilerInstance::ExecuteAction(clang::FrontendAction&)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x16f7f6c)
#18 0x17a99ea clang::ExecuteCompilerInvocation(clang::CompilerInstance*)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x17a99ea)
#19 0x6e28e4 cc1_main(llvm::ArrayRef<char const*>, char const*, void*)
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x6e28e4)
#20 0x6e14b8 main
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x6e14b8)
#21 0x7f40eeed8ec5 __libc_start_main
/build/buildd/eglibc-2.19/csu/libc-start.c:321:0
#22 0x6de4a8 _start
(/usr/local/google/work/llvm/build.release/bin/clang-3.6+0x6de4a8)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20150324/cd376851/attachment.html>