[LLVMbugs] [Bug 4286] New: Assertion failed: (use_empty() && " Uses remain when a value is destroyed!"), function ~Value

bugzilla-daemon at cs.uiuc.edu bugzilla-daemon at cs.uiuc.edu
Sun May 31 07:04:45 PDT 2009


http://llvm.org/bugs/show_bug.cgi?id=4286

           Summary: Assertion failed: (use_empty() && "Uses remain when a
                    value is destroyed!"), function ~Value
           Product: libraries
           Version: trunk
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Scalar Optimizations
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: ed at 80386.nl
                CC: llvmbugs at cs.uiuc.edu
            Blocks: 3696


Created an attachment (id=3044)
 --> (http://llvm.org/bugs/attachment.cgi?id=3044)
Reduced testcase

When building the attached C code with Clang, I get the following console
output:

$ cc -O2 -pipe   /home/ed/llvm-crash.c  -o llvm-crash
While deleting: i1* %storetmp.i
Use still stuck around after Def is destroyed:  store i1 true, i1* %storetmp.i

Assertion failed: (use_empty() && "Uses remain when a value is destroyed!"),
function ~Value, file .../llvm/lib/VMCore/Value.cpp, line 70.
Stack dump:
0.      Program arguments: /usr/bin/../libexec/clang-cc -triple
x86_64-undermydesk-freebsd8.0 -S -disable-free -main-file-name llvm-crash.c
--relocation-model static --disable-fp-elim --unwind-tables=1 --mcpu=x86-64
--fmath-errno=1 -O2 -fdiagnostics-show-option -o /tmp/cc-eU01Mt.s -x c
/home/ed/llvm-crash.c 
1.      <eof> parser at end of file
2.      Per-module optimization passes
3.      Running pass 'CallGraph Pass Manager' on module
'/home/ed/llvm-crash.c'.
4.      Running pass 'Scalar Replacement of Aggregates' on function
'@pnm_encode'

The testcase is based on source code from the high profile FreeBSD port
`jasper' (a JPEG decoder): http://www.ece.uvic.ca/~mdadams/jasper/


-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the llvm-bugs mailing list