From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21341 invoked by alias); 3 Jun 2019 17:03:55 -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 21332 invoked by uid 89); 3 Jun 2019 17:03:55 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-13.0 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS,USER_IN_DEF_SPF_WL autolearn=ham version=3.3.1 spammy=RUNTESTFLAGS, HX-Languages-Length:1324, runtestflags X-HELO: mail-vk1-f178.google.com Received: from mail-vk1-f178.google.com (HELO mail-vk1-f178.google.com) (209.85.221.178) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 03 Jun 2019 17:03:54 +0000 Received: by mail-vk1-f178.google.com with SMTP id s16so1610678vke.7 for ; Mon, 03 Jun 2019 10:03:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=golang-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RMmHTW1XiJi9+li21pLRex9rI0VD/3F7UxWzUrGSK5g=; b=BfCDOL8n3fR0JDs6YnIOYp00mimX7UujLO5GkS/c1JAhdUVfdtTEGeGpW8rUH+iEoW Q7yfXiNeEKPsSxWZfUHDAdB4XvLbYC1nkWAvrYRzV0RV4oi4zU5jnDlaagpwTsf8CX+L Uq2ZeY7KZiCMcACHPBQHVEg3CRjdHQqowUkQEa1Hz6niLNtORQdztMMpQUtFQ4uGJ6Rb iz4AyHujar5/vYf0XhhNDrZbdJH7kLUai6gUa1qGttp0tLz72a5VgA5H166qJhHmIe7t W4X65mfwBz3YZaNzChdqoTuv/qGZL5UvPFTjSlwR8710Q5GMBy+ZHvZ+Q9k9bWyl8vHm mvgw== MIME-Version: 1.0 References: <87a7fibpms.fsf@igel.home> <87zhn395ix.fsf@igel.home> In-Reply-To: From: Ian Lance Taylor Date: Mon, 03 Jun 2019 17:03:00 -0000 Message-ID: Subject: Re: Go patch committed: Intrinsify runtime/internal/atomic functions To: Maciej Rozycki Cc: Jim Wilson , Andreas Schwab , gcc-patches , gofrontend-dev Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-06/txt/msg00103.txt.bz2 On Mon, Jun 3, 2019 at 7:12 AM Maciej Rozycki wrote: > > On Thu, 30 May 2019, Jim Wilson wrote: > > > > Here are the test results: > > > http://gcc.gnu.org/ml/gcc-testresults/2019-05/msg02903.html > > > > 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 > mode (I have patches outstanding for configury/Makefiles to correctly > support libgo and other library testing with a build sysroot in such a > setup, pending the completion of my WDC copyright assignment paperwork > with FSF): > > FAIL: go.test/test/args.go execution, -O2 -g That is a fairly trivial test so if that one fails then something is pretty fundamentally wrong somewhere. You can run just that test by running make RUNTESTFLAGS=go-test.exp=args.go check-gcc-go If it fails you should have an executable gcc/testsuite/go/args.x. Run that executable as `args.x arg1 arg2`. Ian