From owner-freebsd-current@freebsd.org Tue Sep 29 10:45:14 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 443193FD4D9 for ; Tue, 29 Sep 2020 10:45:14 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C0wyK1vkHz4bw3; Tue, 29 Sep 2020 10:45:12 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from fomalhaut.potoki.eu ([IPv6:2001:470:71:d47:65e3:7b4a:25c7:3481]) (authenticated bits=0) by plan-b.pwste.edu.pl (8.16.1/8.16.1) with ESMTPSA id 08TAj3G6082586 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 29 Sep 2020 12:45:03 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) X-Authentication-Warning: plan-b.pwste.edu.pl: Host [IPv6:2001:470:71:d47:65e3:7b4a:25c7:3481] claimed to be fomalhaut.potoki.eu Subject: Re: clang build buggy code with certain CPUTYPE setting To: Andriy Gapon , Dimitry Andric Cc: freebsd-current@freebsd.org References: <20200926114045.GA31128@plan-b.pwste.edu.pl> <6AA016B6-EEAC-4580-B7F0-9D274ADA9E73@FreeBSD.org> <20200926195533.GA16596@plan-b.pwste.edu.pl> From: Marek Zarychta Message-ID: Date: Tue, 29 Sep 2020 12:45:01 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="MRa5t4fDszALhyIra57qiBVeamyoFX1zt" X-Rspamd-Queue-Id: 4C0wyK1vkHz4bw3 X-Spamd-Bar: ------- X-Spamd-Result: default: False [-7.38 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[plan-b.pwste.edu.pl:s=plan-b-mailer]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; HAS_ATTACHMENT(0.00)[]; HAS_XAW(0.00)[]; DWL_DNSWL_MED(-2.00)[pwste.edu.pl:dkim]; NEURAL_HAM_LONG(-1.00)[-1.001]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[plan-b.pwste.edu.pl:+]; DMARC_POLICY_ALLOW(-0.50)[plan-b.pwste.edu.pl,none]; NEURAL_HAM_SHORT(-0.49)[-0.491]; NEURAL_HAM_MEDIUM(-0.99)[-0.989]; SIGNED_PGP(-2.00)[]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; ASN(0.00)[asn:206006, ipnet:2001:678:618::/48, country:PL]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Sep 2020 10:45:14 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MRa5t4fDszALhyIra57qiBVeamyoFX1zt Content-Type: multipart/mixed; boundary="mPui4jCPApopk6ZdSJO9ali9rlBdviYHj"; protected-headers="v1" From: Marek Zarychta To: Andriy Gapon , Dimitry Andric Cc: freebsd-current@freebsd.org Message-ID: 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> In-Reply-To: --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--