[LLVMbugs] [Bug 13654] New: [AVX] X86 DAG->DAG Instruction Selection crash

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Mon Aug 20 17:17:34 PDT 2012


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

             Bug #: 13654
           Summary: [AVX] X86 DAG->DAG Instruction Selection crash
           Product: new-bugs
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: matt at pharr.org
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified


Created attachment 9083
  --> http://llvm.org/bugs/attachment.cgi?id=9083
test case

The attached test case crashes in x86 instruction selection:

% llc -mattr=+avx /Users/mmp/ispc/src/bugpoint-reduced-simplified.ll  
...
Stack dump:
0.    Program arguments: llc -mattr=+avx
/Users/mmp/ispc/src/bugpoint-reduced-simplified.ll 
1.    Running pass 'Function Pass Manager' on module
'/Users/mmp/ispc/src/bugpoint-reduced-simplified.ll'.
2.    Running pass 'X86 DAG->DAG Instruction Selection' on function
'@f_f___un_3C_unf_3E_un_3C_unf_3E_'

Git bisect reports that this broke with the following commit:

Author: Michael Liao <michael.liao at intel.com>
Date:   Tue Aug 14 21:24:47 2012 +0000

    fix PR11334

    - FP_EXTEND only support extending from vectors with matching elements.
      This results in the scalarization of extending to v2f64 from v2f32,
      which will be legalized to v4f32 not matching with v2f64.
    - add X86-specific VFPEXT supproting extending from v4f32 to v2f64.
    - add BUILD_VECTOR lowering helper to recover back the original
      extending from v4f32 to v2f64.
    - test case is enhanced to include different vector width.



    git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@161894
91177308-0d34-0410-b5e6-96231b3b80d8

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