Date: Mon, 15 Aug 2022 18:57:59 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 265809] clang never finishes on one particular C++ file Message-ID: <bug-265809-29464-KiQ0jPI8Fl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-265809-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-265809-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265809 John F. Carr <jfc@mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfc@mit.edu --- Comment #1 from John F. Carr <jfc@mit.edu> --- The hang (or exponential runtime) appears to be in LLVM's DAGCombiner::Run working on the function deriv2eri3_aB_P__0__F__1___TwoPRep_unit__0__P__1___Ab__up_0. To narrow it = down I ran clang++ -emit-llvm to get an IR file. That ran quickly. Then I ran = llc from an LLVM 14 build (it's not installed by default) on that IR file and t= hat part hung. The C++ file does not compile with LLVM 15 clang due to changes= in intrinsics. The LLVM 15 llc program hangs on the output from LLVM 14 clang. Is anybody in particular responsible for reporting LLVM bugs upstream? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265809-29464-KiQ0jPI8Fl>