From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 54445 invoked by alias); 28 Jun 2018 17:10:33 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 54429 invoked by uid 89); 28 Jun 2018 17:10:32 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=HX-Received:sk:x22-v6m X-HELO: mail-ua0-f169.google.com Received: from mail-ua0-f169.google.com (HELO mail-ua0-f169.google.com) (209.85.217.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 28 Jun 2018 17:10:31 +0000 Received: by mail-ua0-f169.google.com with SMTP id v15-v6so4028674ual.11 for ; Thu, 28 Jun 2018 10:10:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=i7SXlU9YwCqyg8Nn9mPDm+0YQGaNT9UFJiK81VNtMTM=; b=PD+RT5duAqX7DUrCoCLpEj8DQmJWAtEYp9W4VCdgDkk6poOCe2efHsmz1/93DFRNdK 2szX7t/B+LVFxPDgLuRryRRdetApM0s8GJN4uEMBwP/Pumv2yTGyOabNI9exlOZXAyxx /5lkl4i+jBOC9oVWyTcwz4dayDWyTCLjSB800= MIME-Version: 1.0 References: <201806281523.w5SFNQjY030212@sellcey-dt.caveonetworks.com> In-Reply-To: <201806281523.w5SFNQjY030212@sellcey-dt.caveonetworks.com> From: Christophe Lyon Date: Thu, 28 Jun 2018 22:40:00 -0000 Message-ID: Subject: Re: GCC regression question (pr77445-2.c & ssa-dom-thread-7.c) To: Steve Ellcey Cc: gcc@gcc.gnu.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-06/txt/msg00290.txt.bz2 On Thu, 28 Jun 2018 at 17:23, Steve Ellcey wrote: > > Does anyone know anything about these failures that I see on my aarch64 > build & test? > > FAIL: gcc.dg/tree-ssa/pr77445-2.c scan-tree-dump-not thread3 "not considered" > FAIL: gcc.dg/tree-ssa/ssa-dom-thread-7.c scan-tree-dump-not vrp2 "Jumps threaded" > > The both seem to have started showing up on May 20th and I don't see any > bugzilla report on them. Before I try and track down what checkin caused > them and whether or not they were caused by the same checkin I thought I > would see if anyone had already done that. > Yes it's sometimes tricky to find out if a regression has been reported or not. Martin is aware of these two: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg01479.html Christophe > Steve Ellcey > sellcey@cavium.com