Date: Sun, 05 May 2024 00:18:16 +0000 From: bugzilla-noreply@freebsd.org To: threads@FreeBSD.org Subject: [Bug 278703] Forking on 13.3 restricting to same CPU core Message-ID: <bug-278703-13406-vjrlgl5BZk@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-278703-13406@https.bugs.freebsd.org/bugzilla/> References: <bug-278703-13406@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=3D278703 --- Comment #5 from cbl@cbl.us --- More troubleshooting..=20 This issue is occurring on /usr/lib/libomp.so with llvm17, which is the def= ault with FreeBSD 13.3. I installed a few other llvm's via pkg (and even compiled llvm-devel 19.x) = to test things. When I copy over the libomp.so from llvm14 or llvm15 into /usr/lib/ the application starts using all the CPU cores as expected. So something changed in llvm16 and later that is causing our linked application (ImageMagick) to limit itself to a single cpu core. Since FreeBSD 13.2 was still using llvm14 by default, the problem was not occurring then. llvm14-14.0.6_5 - WORKS llvm15-15.0.7_10 - WORKS llvm16-16.0.6_10 - BROKE llvm17-17.0.6 (13.3 default) - BROKE llvm19-19.0.d20240426 - BROKE I'd welcome input on what to try next, or what to report to the LLVM group = to fix the issue. --=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-278703-13406-vjrlgl5BZk>