[Bug 265809] clang never finishes on one particular C++ file

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 13 Sep 2022 18:20:16 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265809

--- Comment #2 from Morgan Wesström <freebsd.bugs@pp.dyndns.biz> ---
I believe I'm hitting the same or a related problem after source upgrading from
FreeBSD-13.0-RELEASE-p5 to FreeBSD-13.1-RELEASE-p2. When recompiling all ports
afterwards it gets stuck consistently on the same file from
databases/mariadb105-server-10.5.17:

/usr/ports/databases/mariadb105-server/work/mariadb-10.5.17/storage/innobase/pars/pars0sym.cc

The compilation process gets stuck at 100% cpu but produces no output to the
object file and truss(1) shows no syscalls at this point. I let it sit for 8+
hours in this state but it never progressed so I killed the process at that
point.

I quickly installed a fresh FreeBSD-13.1-p2 in a virtual machine and verified
that the ports compilation worked there. The only thing that differs between my
 machines and a default setup are a few exclusions in /etc/src.conf and a
CPUTYPE?=bonnell directive in /etc/make.conf

I reverted those changes and recompiled my system and then the ports
compilation of mariadb105-server worked normally again. I restored the
CPUTYPE?=bonnell and recompiled the system again and once more the compilation
of mariadb gets stuck at the exact same file.

My knowledge is limited and I don't know how to track down the problem further
but the CPUTYPE directive adds a -march= to the compiler arguments just as the
original post shows. Perhaps there's a malfunction here in the clang/llvm 13
version included in FreeBSD-13.1? I had no such problems with clang/llvm 11 in
FreeBSD-13.0.

As an extra test I also tried to compile mariadb106-server and it experiences
the exact same stuck behaviour, albeit on a different file but in the same
directory. I forgot to make a note of that filename unfortunately.

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