From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 77783 invoked by alias); 3 Jun 2019 14:12:32 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 77775 invoked by uid 89); 3 Jun 2019 14:12:32 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_20,KAM_SHORT autolearn=ham version=3.3.1 spammy=jpeg, gcctestresults, gcc-testresults, makefiles X-HELO: esa5.hgst.iphmx.com Received: from esa5.hgst.iphmx.com (HELO esa5.hgst.iphmx.com) (216.71.153.144) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 03 Jun 2019 14:12:26 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=wdc.com; i=@wdc.com; q=dns/txt; s=dkim.wdc.com; t=1559571147; x=1591107147; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=AY2jGA0xggTq/2VXFZheU2OZVpqcpGXRbX74NkrRWtU=; b=fJVH4HkuE+9VFC94NugAQHl9dT1+/gAOyxmrH/vnCILzz2xh58WhQZDC goNy6cZbtcuPwOApzYh/HEADZeQRTL2Dnytx17oqz4sIU9lFxti6dKKqn EcpaYqdyFyojloeht+XIVzkFWnQGxqMURiFNVn0Jy3u1JfMIqRngp4Aj8 JN24A0sdBhQ8SbFY1y/I8dA+uRTvhZng88eqYdxTOAlxo68/+Xu8On/3x 9RE/XHH01scXzLrjtS7UA0bAtT6IhOAtCU/gMrrv9XsndthglNeDEDW/L +0BljLhVEmm1TDJRiS8HdHMfn09D2P7th6u53LHbvHRlwPZm5+/Ly4JDk w==; Received: from mail-co1nam03lp2057.outbound.protection.outlook.com (HELO NAM03-CO1-obe.outbound.protection.outlook.com) ([104.47.40.57]) by ob1.hgst.iphmx.com with ESMTP; 03 Jun 2019 22:12:23 +0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sharedspace.onmicrosoft.com; s=selector2-sharedspace-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PqnP+prJ2dwdK7bd83qWAoZVbE6aB8hQRPNuin4rnGI=; b=Vo1nrJ2SurAuBOBTFBE7EahlPZgR+1/R9QA65JGjl+sQso8wChUAxQsM9NeVYoDIrA7v0an3wNdzkUZbCpYhAhbBVWVmMBEAuENVWSONWuqJcr15/aVAPPULsURRgUhdlnFByhMYIIxlVFMdRToBvbJ+SQ+B3NNR3+E5bSR6J3Q= Received: from BYAPR04MB4502.namprd04.prod.outlook.com (52.135.238.11) by BYAPR04MB4456.namprd04.prod.outlook.com (52.135.237.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.22; Mon, 3 Jun 2019 14:12:20 +0000 Received: from BYAPR04MB4502.namprd04.prod.outlook.com ([fe80::e15b:4e75:ab6c:8e1a]) by BYAPR04MB4502.namprd04.prod.outlook.com ([fe80::e15b:4e75:ab6c:8e1a%6]) with mapi id 15.20.1943.018; Mon, 3 Jun 2019 14:12:20 +0000 From: Maciej Rozycki To: Jim Wilson CC: Andreas Schwab , Ian Lance Taylor , gcc-patches , gofrontend-dev Subject: Re: Go patch committed: Intrinsify runtime/internal/atomic functions Date: Mon, 03 Jun 2019 14:12:00 -0000 Message-ID: References: <87a7fibpms.fsf@igel.home> <87zhn395ix.fsf@igel.home> In-Reply-To: authentication-results: spf=none (sender IP is ) smtp.mailfrom=macro@wdc.com; x-ms-exchange-purlcount: 1 wdcipoutbound: EOP-TRUE x-ms-oob-tlc-oobclassifiers: OLM:10000; x-ms-exchange-senderadcheck: 1 Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: macro@wdc.com X-SW-Source: 2019-06/txt/msg00086.txt.bz2 On Thu, 30 May 2019, Jim Wilson wrote: > > Here are the test results: > > http://gcc.gnu.org/ml/gcc-testresults/2019-05/msg02903.html >=20 > I tried running RISC-V go checks on my system. I see 7 unexpected > failures for gcc check-go, 6 unexpected failures for check-gotools, > and 1 unexpected failure for check-target-libgo. I haven't tried > building and testing the go support before so I don't have any old > results to compare against. It seems reasonable for a first attempt > though. I have results as at r270765, taken with QEMU run in the user emulation=20 mode (I have patches outstanding for configury/Makefiles to correctly=20 support libgo and other library testing with a build sysroot in such a=20 setup, pending the completion of my WDC copyright assignment paperwork=20 with FSF): FAIL: go.test/test/args.go execution, -O2 -g FAIL: go.test/test/fixedbugs/bug347.go execution, -O0 -g FAIL: go.test/test/fixedbugs/bug348.go execution, -O0 -g FAIL: go.test/test/fixedbugs/issue4562.go execution, -O2 -g FAIL: go.test/test/fixedbugs/issue6055.go execution, -O2 -g FAIL: go.test/test/method5.go execution, -O2 -g FAIL: go.test/test/nil.go execution, -O2 -g FAIL: go.test/test/recover3.go execution, -O2 -g =3D=3D=3D go Summary =3D=3D=3D # of expected passes 3188 # of unexpected failures 8 # of expected failures 1 # of untested testcases 32 # of unsupported tests 3 I don't know why the number of passes (effectively # of tests run) is=20 reduced by more than a half with otherwise similar figures; it could be=20 due to the use of a simulator vs native test setup. For some reason I haven't looked into libgo tests are deliberatly run=20 individually and results, concatenated into libgo-all.sum, have to be=20 processed manually to get a summary. Here's one I have come up with: WARNING: program timed out. FAIL: archive/zip FAIL: cmd/go/internal/lockedfile/internal/filelock FAIL: compress/flate FAIL: compress/lzw FAIL: compress/zlib WARNING: program timed out. FAIL: crypto/dsa FAIL: crypto/tls FAIL: database/sql FAIL: html/template FAIL: image/draw FAIL: image/jpeg FAIL: internal/cpu FAIL: internal/x/crypto/cryptobyte FAIL: internal/x/net/http/httpproxy FAIL: log/syslog FAIL: net FAIL: net/http FAIL: net/http/cgi FAIL: net/http/internal FAIL: net/http/pprof FAIL: os FAIL: os/exec FAIL: os/signal FAIL: reflect WARNING: program timed out. FAIL: regexp WARNING: program timed out. FAIL: runtime FAIL: runtime/pprof FAIL: sync FAIL: sync/atomic FAIL: syscall FAIL: text/template FAIL: time =3D=3D=3D libgo Summary =3D=3D=3D # of expected passes 136 # of unexpected failures 32 These are significantly worse, but I suspect the use of the user emulation= =20 mode of QEMU may have contributed here. No gotools tests run in my setup for some reason: make[2]: Entering directory '.../gcc/gotools' make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '.../gcc/gotools' -- maybe this is not supported with a cross-toolchain. I have current test results (also for the other frontends/libraries, e.g.= =20 GNAT) with the same setup as well in case someone is interested. There=20 are minor differences. Maciej