[llvm-bugs] [Bug 25461] New: MachineVerifier complains about Windows EH constructs

via llvm-bugs llvm-bugs at lists.llvm.org
Mon Nov 9 11:06:26 PST 2015


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

            Bug ID: 25461
           Summary: MachineVerifier complains about Windows EH constructs
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P
         Component: Common Code Generator Code
          Assignee: unassignedbugs at nondot.org
          Reporter: rnk at google.com
                CC: andrew.kaylor at intel.com, david.majnemer at gmail.com,
                    JCTremoulet at gmail.com, llvm-bugs at lists.llvm.org
    Classification: Unclassified

Apparently we've never run the MachineVerifier with WinEH, and I'm getting
errors like this now:

*** Bad machine code: MBB has more than one landing pad successor ***
*** Bad machine code: Using an undefined physical register ***
*** Bad machine code: Using an undefined physical register ***
*** Bad machine code: Using an undefined physical register ***
*** Bad machine code: Using an undefined physical register ***
*** Bad machine code: Using an undefined physical register ***
*** Bad machine code: MBB exits via conditional branch/fall-through but the CFG
successors don't match the actual successors! ***
*** Bad machine code: Using an undefined physical register ***
*** Bad machine code: Using an undefined physical register ***
*** Bad machine code: Using an undefined physical register ***
*** Bad machine code: Using an undefined physical register ***

We should relax the first verifier invariant, since in WinEH there can be
multiple EH pad successors for an invoke.

The undefined physreg stuff is probably our bad and we should sort that out.

The condbr/fallthrough stuff might be our bad, I'm not sure.

-- 
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/20151109/d3521c35/attachment.html>


More information about the llvm-bugs mailing list