From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 45143 invoked by alias); 4 Jan 2017 15:01:07 -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 45105 invoked by uid 89); 4 Jan 2017 15:01:05 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=sk:people, sk:people., Hx-languages-length:1275, january X-HELO: mail-qt0-f170.google.com Received: from mail-qt0-f170.google.com (HELO mail-qt0-f170.google.com) (209.85.216.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 04 Jan 2017 15:00:55 +0000 Received: by mail-qt0-f170.google.com with SMTP id c47so492600726qtc.2 for ; Wed, 04 Jan 2017 07:00:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zPE7miZLCxO52Yuyq1UFnqvzkI2nR5edcZzjUjXrkaY=; b=hqZbgt/avWTnWHmFbQHQPAwj5KAGd8oNcXXJpgfIqIUYj6z3n53LctegIvAttEHvsR wFiUJ2vVNdJL+DLH+p0yluJg4afvtqpYcCkbJKU93tu0kOsVWdEqBIX533s2xWSYH40x LA0Q5VL2eGXUl9CFDbLew83iR6x5P3sWhsHPM6dR8qOOVNi8ga0U7U3M64Pv2bZgFvW2 zbRk5KzNaaNmrMWYw9QBg2w2HVKItjQJLVraXY6RbznCFIfWjRXe8Z/xD9RfcQFy5ZfC w9NThJUb4I6m4J3HGAVVlWjlQ6MeHX6k/0qrUqFlOgebXB96Nfq4thtod5beJJmqM6dY 5fCg== X-Gm-Message-State: AIkVDXIeyhzL8OnckDdc1ubDidf9T8GQAEVxcSN2zAUKDRRtTldronXteOKDhZX0Xqge4muO0ct6Nxa4AhG6+teh X-Received: by 10.200.50.209 with SMTP id a17mr61379404qtb.41.1483542053983; Wed, 04 Jan 2017 07:00:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.101.144 with HTTP; Wed, 4 Jan 2017 07:00:52 -0800 (PST) In-Reply-To: <20170104110232.GG895@redhat.com> References: <20161109212623.2488-1-suokkos@gmail.com> <20161216175257.GG895@redhat.com> <20161219175227.GP895@redhat.com> <20170103153224.GF895@redhat.com> <20170104110232.GG895@redhat.com> From: Christophe Lyon Date: Wed, 04 Jan 2017 15:01:00 -0000 Message-ID: Subject: Re: [PATCH] libstdc++: Allow using without lock free atomic int To: Jonathan Wakely Cc: Pauli , "libstdc++@gcc.gnu.org" , "gcc-patches@gcc.gnu.org" Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2017-01/txt/msg00218.txt.bz2 Hi Jonathan, On 4 January 2017 at 12:02, Jonathan Wakely wrote: > On 03/01/17 15:32 +0000, Jonathan Wakely wrote: >> >> Here's what I plan to commit to trunk tomorrow. > > > Committed to trunk. > > After this commit (r244051), I do see improvements, but also a few new failures. The big picture is at http://people.linaro.org/~christophe.lyon/cross-validation/gcc/trunk/244051/report-build-info.html Where the expected improvements for arm-none-eabi, with default cpu&fpu are: http://people.linaro.org/~christophe.lyon/cross-validation/gcc/trunk/244051/arm-none-eabi/diff-libstdc++-rh60-arm-none-eabi-default-default-default.txt New failures appear when forcing -march=armv5t in runtestflags (the 3 red items in the 1st report): - FAIL appears [ => FAIL]: 18_support/exception_ptr/60612-terminate.cc execution test 18_support/exception_ptr/60612-unexpected.cc execution test 30_threads/packaged_task/members/at_thread_exit.cc execution test 30_threads/promise/members/at_thread_exit.cc execution test Note that in these cases we are compiling the test cases with -march=armv5t, but link with libraries built --with-cpu=cortex-a9, so there might be a mismatch? Christophe