Date: Tue, 29 Sep 2020 12:45:01 +0200 From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> To: Andriy Gapon <avg@FreeBSD.org>, Dimitry Andric <dim@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: clang build buggy code with certain CPUTYPE setting Message-ID: <b927db09-7a60-30ee-9888-7fb9588bf33d@plan-b.pwste.edu.pl> In-Reply-To: <b3c1b6e8-5d67-c20c-2086-0334f531bd64@FreeBSD.org> References: <20200926114045.GA31128@plan-b.pwste.edu.pl> <6AA016B6-EEAC-4580-B7F0-9D274ADA9E73@FreeBSD.org> <20200926195533.GA16596@plan-b.pwste.edu.pl> <b3c1b6e8-5d67-c20c-2086-0334f531bd64@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MRa5t4fDszALhyIra57qiBVeamyoFX1zt Content-Type: multipart/mixed; boundary="mPui4jCPApopk6ZdSJO9ali9rlBdviYHj"; protected-headers="v1" From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> To: Andriy Gapon <avg@FreeBSD.org>, Dimitry Andric <dim@freebsd.org> Cc: freebsd-current@freebsd.org Message-ID: <b927db09-7a60-30ee-9888-7fb9588bf33d@plan-b.pwste.edu.pl> Subject: Re: clang build buggy code with certain CPUTYPE setting References: <20200926114045.GA31128@plan-b.pwste.edu.pl> <6AA016B6-EEAC-4580-B7F0-9D274ADA9E73@FreeBSD.org> <20200926195533.GA16596@plan-b.pwste.edu.pl> <b3c1b6e8-5d67-c20c-2086-0334f531bd64@FreeBSD.org> In-Reply-To: <b3c1b6e8-5d67-c20c-2086-0334f531bd64@FreeBSD.org> --mPui4jCPApopk6ZdSJO9ali9rlBdviYHj Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US On 28.09.2020 10:59, Andriy Gapon wrote: > 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?=3Damdfam10 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? > I tried to reproduce this for debugging purposes, but I am not able to.=20 Either my builds were somehow polluted, though obj directory was cleaned = before each build, or not patched LLVM was bootstrapping itself in a=20 wrong way despite updated sources. Anyway the issue has gone and it is=20 possible to run world built with CPUTYPE?=3Damdfam10 using r366241 as=20 starting point. Thank you guys for your assistance, patience and work which gives us the = ability to use well maintained, rock-stable and modern OS. --=20 Marek Zarychta --mPui4jCPApopk6ZdSJO9ali9rlBdviYHj-- --MRa5t4fDszALhyIra57qiBVeamyoFX1zt Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEnjwyTmqn2oNX6C8qHZW8vIFppoIFAl9zEC0FAwAAAAAACgkQHZW8vIFppoIy zAf9GZxo9g62wTlfFZzsGHz9GF4a6vPPof9CEJtR8Amt6Yy+6ko+8NX4gnVlidXtruv4LT6xEQ+2 FhCTUtc6EDTbluwMW0nyLcKFJj89ecmay1B72NA5CCqHSqfe6doszfaGCo81kFdod78bhKMJ3rY5 xfEZTU1tZxdDiyzxKvx590yDIsuPgZySg7aWtO+qMVtEHw3PyiU3TcPT+gmKQ6t9aD+fudy8gEQo Zy023A3sniKeMwJLLXs/rnYYkzipVVsobN0bhESzvVYgzsDGhGpzvNfO6ecJRKYNEqY26vSq5raM Las8RnOmydY4BqFplV1pUfneZIvPtsZhK+HBWyYPLw== =Jrfa -----END PGP SIGNATURE----- --MRa5t4fDszALhyIra57qiBVeamyoFX1zt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b927db09-7a60-30ee-9888-7fb9588bf33d>