[llvm-bugs] [Bug 49003] New: Compiler produces a partial stack trace and hangs

[via llvm-bugs]

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

            Bug ID: 49003
           Summary: Compiler produces a partial stack trace and hangs
           Product: clang
           Version: 11.0
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: release blocker
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: rennieallen at gmail.com
                CC: htmldeveloper at gmail.com, llvm-bugs at lists.llvm.org,
                    neeilans at live.com, richard-llvm at metafoo.co.uk

I suspect the issue is associated with the following error:

fatal error: bracket nesting level exceeded maximum of 256

which happens with default bracket depth. If I set -fbracket-depth=512 then the
compiler produces a partial stack trace, and then hangs forever (or at least
for a very long time)

This the "stack trace" produced (sensitive information redacted)

0.      Program arguments: D:\Program Files\LLVM\bin\clang++.exe -cc1 -triple
x86_64-pc-windows-msvc19.23.28106 -emit-obj -mincremental-linker-compatible
-disable-free -disable-llvm-verifier -discard-value-names -main-file-name
ForeignCodeProcessScanner.cpp -mrelocation-model pic -pic-level 2
-mframe-pointer=none -fmath-errno -fno-rounding-math -mconstructor-aliases
-munwind-tables -target-cpu x86-64 -resource-dir D:\Program
Files\LLVM\lib\clang\11.0.0 -MP -I ../ -I {redacted} -I {redacted} -I
{redacted} -D _CRT_SECURE_NO_WARNINGS -D _HAS_EXCEPTIONS=0 -D _SECURE_SCL=0 -D
_WIN32_IE=0x0601 -D _WIN32_WINNT=0x0601 -D {redacted} -D {redacted} -D
{redacted} -D {redacted} -D {redacted} -D {redacted} -D NDEBUG -D WIN32 -D
WINVER=0x0601 -D _WINDLL -D _MBCS -Fp -internal-isystem D:\Program
Files\LLVM\lib\clang\11.0.0\include -internal-isystem C:\Program Files
(x86)\Microsoft Visual
Studio\2019\Professional\VC\Tools\MSVC\14.23.28105\include -internal-isystem
C:\Program Files (x86)\Microsoft Visual
Studio\2019\Professional\VC\Tools\MSVC\14.23.28105\atlmfc\include
-internal-isystem C:\Program Files (x86)\Windows
Kits\10\Include\10.0.19041.0\ucrt -internal-isystem C:\Program Files
(x86)\Windows Kits\10\include\10.0.19041.0\shared -internal-isystem C:\Program
Files (x86)\Windows Kits\10\include\10.0.19041.0\um -internal-isystem
C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt -Os
-fdeprecated-macro -fdebug-compilation-dir {redacted} -fbracket-depth 512
-ferror-limit 19 -fmessage-length=273 -fno-use-cxa-atexit -fms-extensions
-fms-compatibility -fms-compatibility-version=19.23.28106 -std=c++14
-fdelayed-template-parsing -fcxx-exceptions -fexceptions -fcolor-diagnostics
-vectorize-loops -vectorize-slp -faddrsig -o {redacted} -627d91.o -x c++
.\{redacted}.cpp
1.

The isolated "1." is what is displayed and at this point the compiler just
spins forever.

Unfortunately this is a security related product, so I cannot publicly post the
preprocessed file, but I figured this hanging behavior is pretty significant
and should be reported, if for nothing else it might provide an indication of
prevalence.

As can be surmised from the command line, this is from attempting to compile
code which compiles fine with MSVC 14.23.

-- 
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/20210202/771d063e/attachment-0001.html>