[llvm-bugs] [Bug 34834] New: Assertion failure with debuginfos and inlining ('Invalid result number for the given node')

[via llvm-bugs]

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

            Bug ID: 34834
           Summary: Assertion failure with debuginfos and inlining
                    ('Invalid result number for the given node')
           Product: libraries
           Version: 5.0
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: DebugInfo
          Assignee: unassignedbugs at nondot.org
          Reporter: kinke at gmx.net
                CC: llvm-bugs at lists.llvm.org

Created attachment 19233
  --> https://bugs.llvm.org/attachment.cgi?id=19233&action=edit
4 IR files (new/old, with/without inlining).

I'm hitting:

Assertion failed: (!Node || !ResNo || ResNo < Node->getNumValues()) && "Invalid
result number for the given node!", file
C:\LDC\llvm\include\llvm/CodeGen/SelectionDAGNodes.h, line 1038

when compiling a tiny D file with LDC using LLVM 5.0 (tested for Linux and
Windows-MSVC targets). It requires debuginfos output AND enabled inlining (no
other optimizations required). That code used to work; recent LDC has only
minimally changed the IR (in-place construction in one function), and that
seems to trigger it.

The tiny relevant IR diff is here:
https://github.com/ldc-developers/ldc/pull/2252#issuecomment-333412625

Also happens with LLVM 4.0.1 for Linux targets.

-- 
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/20171004/9d8f4cdd/attachment-0001.html>