[LLVMbugs] [Bug 7712] New: psuedo instructions should be removed before code emission

[bugzilla-daemon at llvm.org]

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

           Summary: psuedo instructions should be removed before code
                    emission
           Product: tools
           Version: trunk
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: lli
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: grosser at fim.uni-passau.de
                CC: llvmbugs at cs.uiuc.edu


Created an attachment (id=5265)
 --> (http://llvm.org/bugs/attachment.cgi?id=5265)
Failing test case

#> bin/lli /tmp/out.ll 
psuedo instructions should be removed before code emission
UNREACHABLE executed at
/home/grosser/Projekte/llvm/git_trunk/lib/Target/X86/X86CodeEmitter.cpp:609!
Stack dump:
0.    Program arguments: bin/lli /tmp/out.ll 
1.    Running pass 'X86 Machine Code Emitter' on function
'@loop_with_condition'
zsh: abort      bin/lli /tmp/out.ll

I get this bug on a test case since this commit:
-------------------------------------------------------------------------------
Author: Eric Christopher <echristo at apple.com>
Date:   Thu Jul 22 02:48:34 2010 +0000

    Custom lower the memory barrier instructions and add support
    for lowering without sse2.  Add a couple of new testcases.

    Fixes a few libgomp tests and latent bugs.  Remove a few todos.


    svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@109078 
-------------------------------------------------------------------------------

The code is executed on this processor:
-------------------------------------------------------------------------------
processor    : 3
vendor_id    : GenuineIntel
cpu family    : 6
model        : 37
model name    : Intel(R) Core(TM) i5 CPU       M 520  @ 2.40GHz
stepping    : 2
cpu MHz        : 2400.000
cache size    : 3072 KB
physical id    : 0
siblings    : 4
core id        : 2
cpu cores    : 2
apicid        : 5
initial apicid    : 5
fpu        : yes
fpu_exception    : yes
cpuid level    : 11
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf
pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1
sse4_2 popcnt aes lahf_lm ida arat tpr_shadow vnmi flexpriority ept vpid
bogomips    : 4787.92
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:
-------------------------------------------------------------------------------

running a recent 64bit debian system.

I tried to reduce the bug with bugpoint, but did not understand how to use
bugpoint to debug lli test cases. Is this possible?

-- 
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.