Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Sep 2020 11:59:51 +0300
From:      Andriy Gapon <avg@FreeBSD.org>
To:        Marek Zarychta <zarychtam@plan-b.pwste.edu.pl>, Dimitry Andric <dim@freebsd.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: clang build buggy code with certain CPUTYPE setting
Message-ID:  <b3c1b6e8-5d67-c20c-2086-0334f531bd64@FreeBSD.org>
In-Reply-To: <20200926195533.GA16596@plan-b.pwste.edu.pl>
References:  <20200926114045.GA31128@plan-b.pwste.edu.pl> <6AA016B6-EEAC-4580-B7F0-9D274ADA9E73@FreeBSD.org> <20200926195533.GA16596@plan-b.pwste.edu.pl>

next in thread | previous in thread | raw e-mail | index | archive | help
On 26/09/2020 22:55, Marek Zarychta wrote:
> Thank you for the information and for the fix. Sadly I must admit it
> doesn't work for me. I have tried two builds with fresh sources today to
> be certain and it looks like the bug is still present on FreeBSD
> 13-CURRENT r366186. Either the upstream fixed it only partially or it is
> another bug. As a workaround, I will build worlds without
> CPUTYPE?=amdfam10 for a while. I hope the problem will be resolved
> before clang 11 is MFCed to 12-STABLE.

Can you disassemble the faulting instruction in the core dump?
Can you provide full CPU ID / features information from dmesg?

-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b3c1b6e8-5d67-c20c-2086-0334f531bd64>