[llvm-bugs] [Bug 50782] New: fatal error: error in backend: Stack cannot be empty!

via llvm-bugs llvm-bugs at lists.llvm.org
Sun Jun 20 22:50:51 PDT 2021


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

            Bug ID: 50782
           Summary: fatal error: error in backend: Stack cannot be empty!
           Product: new-bugs
           Version: 12.0
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: llvm-bugzilla at jdrake.com
                CC: htmldeveloper at gmail.com, llvm-bugs at lists.llvm.org

Created attachment 24967
  --> https://bugs.llvm.org/attachment.cgi?id=24967&action=edit
LLVM ERROR: Cannot pop empty stack! - creduced case

I've actually run into to slightly different but similar issues on
i686-w64-windows-gnu, from
https://packages.msys2.org/package/mingw-w64-clang-i686-llvm?repo=clang32:

LLVM ERROR: Stack cannot be empty!
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace.
Stack dump:
0.      Program arguments: C:\\msys64\\clang64\\bin\\llc.exe psy-abba67.bc
1.      Running pass 'Function Pass Manager' on module 'psy-abba67.bc'.
2.      Running pass 'X86 FP Stackifier' on function '@bark_noise_hybridmp'
 #0 0x00007fff85c01d86 HandleAbort (C:\msys64\clang64\bin\libLLVM.dll+0x151d86)
 #1 0x00007fffc2211881 (C:\Windows\System32\ucrtbase.dll+0x71881)
 #2 0x00007fffc2212851 (C:\Windows\System32\ucrtbase.dll+0x72851)
 #3 0x00007fff85b43ebe llvm::report_fatal_error(llvm::Twine const&, bool)
(C:\msys64\clang64\bin\libLLVM.dll+0x93ebe)
 #4 0x00007fff85b43cf5 llvm::report_fatal_error(char const*, bool)
(C:\msys64\clang64\bin\libLLVM.dll+0x93cf5)
 #5 0x00007fff8835681c llvm::createX86FloatingPointStackifierPass()
(C:\msys64\clang64\bin\libLLVM.dll+0x28a681c)
 #6 0x00007fff8835463c llvm::createX86FloatingPointStackifierPass()
(C:\msys64\clang64\bin\libLLVM.dll+0x28a463c)
 #7 0x00007fff85f7df43
llvm::MachineFunctionPass::runOnFunction(llvm::Function&)
(C:\msys64\clang64\bin\libLLVM.dll+0x4cdf43)
 #8 0x00007fff85d547c8 llvm::FPPassManager::runOnFunction(llvm::Function&)
(C:\msys64\clang64\bin\libLLVM.dll+0x2a47c8)
 #9 0x00007fff85d5a683 llvm::FPPassManager::runOnModule(llvm::Module&)
(C:\msys64\clang64\bin\libLLVM.dll+0x2aa683)
#10 0x00007fff85d54ee3 llvm::legacy::PassManagerImpl::run(llvm::Module&)
(C:\msys64\clang64\bin\libLLVM.dll+0x2a4ee3)
#11 0x00007ff735374e43 main (C:\msys64\clang64\bin\llc.exe+0x4e43)
#12 0x00007ff7353713ea WinMainCRTStartup (C:\msys64\clang64\bin\llc.exe+0x13ea)
#13 0x00007ff735371446 mainCRTStartup (C:\msys64\clang64\bin\llc.exe+0x1446)
#14 0x00007fffc2f37034 (C:\Windows\System32\KERNEL32.DLL+0x17034)
#15 0x00007fffc4642651 (C:\Windows\SYSTEM32\ntdll.dll+0x52651)

LLVM ERROR: Cannot pop empty stack!
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace.
Stack dump:
0.      Program arguments: C:\\msys64\\clang64\\bin\\llc.exe ltp-4ac572.bc
1.      Running pass 'Function Pass Manager' on module 'ltp-4ac572.bc'.
2.      Running pass 'X86 FP Stackifier' on function '@pitch_gain_search_3tap'
 #0 0x00007fff85c01d86 HandleAbort (C:\msys64\clang64\bin\libLLVM.dll+0x151d86)
 #1 0x00007fffc2211881 (C:\Windows\System32\ucrtbase.dll+0x71881)
 #2 0x00007fffc2212851 (C:\Windows\System32\ucrtbase.dll+0x72851)
 #3 0x00007fff85b43ebe llvm::report_fatal_error(llvm::Twine const&, bool)
(C:\msys64\clang64\bin\libLLVM.dll+0x93ebe)
 #4 0x00007fff85b43cf5 llvm::report_fatal_error(char const*, bool)
(C:\msys64\clang64\bin\libLLVM.dll+0x93cf5)
 #5 0x00007fff88356d03 llvm::createX86FloatingPointStackifierPass()
(C:\msys64\clang64\bin\libLLVM.dll+0x28a6d03)
 #6 0x00007fff88355baf llvm::createX86FloatingPointStackifierPass()
(C:\msys64\clang64\bin\libLLVM.dll+0x28a5baf)
 #7 0x00007fff8835463c llvm::createX86FloatingPointStackifierPass()
(C:\msys64\clang64\bin\libLLVM.dll+0x28a463c)
 #8 0x00007fff85f7df43
llvm::MachineFunctionPass::runOnFunction(llvm::Function&)(C:\msys64\clang64\bin\libLLVM.dll+0x4cdf43)
 #9 0x00007fff85d547c8 llvm::FPPassManager::runOnFunction(llvm::Function&)
(C:\msys64\clang64\bin\libLLVM.dll+0x2a47c8)
#10 0x00007fff85d5a683 llvm::FPPassManager::runOnModule(llvm::Module&)
(C:\msys64\clang64\bin\libLLVM.dll+0x2aa683)
#11 0x00007fff85d54ee3 llvm::legacy::PassManagerImpl::run(llvm::Module&)
(C:\msys64\clang64\bin\libLLVM.dll+0x2a4ee3)
#12 0x00007ff735374e43 main (C:\msys64\clang64\bin\llc.exe+0x4e43)
#13 0x00007ff7353713ea WinMainCRTStartup (C:\msys64\clang64\bin\llc.exe+0x13ea)
#14 0x00007ff735371446 mainCRTStartup (C:\msys64\clang64\bin\llc.exe+0x1446)
#15 0x00007fffc2f37034 (C:\Windows\System32\KERNEL32.DLL+0x17034)
#16 0x00007fffc4642651 (C:\Windows\SYSTEM32\ntdll.dll+0x52651)


Unfortunately, bugpoint was not helpful, and failed with the message:
Checking for crash with changing conditionals to always jump to true:         
... <34 total>: C:/msys64/clang64/bin/opt.exe: bugpoint-input-260ba01.bc:
error: Could not open input file: Permission denied
verify failed!

But creduce was able to make a reduced (if nonsensical) case for each of them.

-- 
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/20210621/b1f72a05/attachment-0001.html>


More information about the llvm-bugs mailing list