[Bug 276170] LLVM bug prevents from enabling PGO optimization for Python 3.11+

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276170

--- Comment #10 from Dimitry Andric <dim@FreeBSD.org> ---
I can't reproduce any crashes here, at least on my 15-CURRENT machine. Since
15-CURRENT uses a newer version of clang, I have used an older binary which
identifies itself as "FreeBSD clang version 16.0.6
(https://github.com/llvm/llvm-project.git llvmorg-16.0.6-0-g7cbf1a259152)",
corresponding to your version.

With the unpacked contents of your zipfile, I can run all .sh files (I only
replaced the clang command in there to point at clang 16.0.6) successfully, and
they all produce .bc files as intended:

$ ls -l *.bc
-rw-r--r--  1 dim dim 258948 2024-01-07 15:17:06 pegen-d7bb62.bc
-rw-r--r--  1 dim dim  52752 2024-01-07 15:17:07 pegen_errors-c153bb.bc
-rw-r--r--  1 dim dim   4244 2024-01-07 15:17:07 python-50eaf7.bc
-rw-r--r--  1 dim dim  14520 2024-01-07 15:17:07 token-7986e1.bc
-rw-r--r--  1 dim dim  14428 2024-01-07 15:17:07 token-9bf20d.bc

However, as indicated, this is on an amd64 host with 15-CURRENT and ample RAM.

I am suspecting that something else may be going on on your system? Do you see
any out of memory errors or other indications like segfaults in dmesg or system
logs?

Can you also share the full error message shown when an instance of clang
crashes? There should be some more information about what is exactly causing
the 134 exit code, which usually indicates an assertion failure.

-- 
You are receiving this mail because:
You are the assignee for the bug.