From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 1CEF3388E82F; Thu, 16 Jul 2020 23:53:32 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1CEF3388E82F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1594943612;
 bh=FNQqnH2YkO8W8xIpE9t/affMv6tVvlnaLoggWY4hPNc=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=LoXUjSfP8qEuKyoBK7Alj1Vj2ld7kQtRuou8gzOh4tLuZorzH0DMupVGKwSwXuo6N
 U88SeSmxKVdkvzW23KhvVgs8NTvTUMqMSQkVZROgeJYqJCe+wDJo+wS+PqycWRaTEJ
 w5vh47VVivTWr9ffOUqh/wePW0QQgYg4L/lEZSMs=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93372] cris performance regressions due to de-cc0 work
Date: Thu, 16 Jul 2020 23:53:31 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hp at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-93372-4-GU3hQ9R9Qb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93372-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93372-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2020 23:53:32 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D93372

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Segher Boessenkool <segher@gcc.gnu.or=
g>:

https://gcc.gnu.org/g:84c5396d4bdbf9f1d628c77db4421808f9a9dcb6

commit r11-2185-g84c5396d4bdbf9f1d628c77db4421808f9a9dcb6
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date:   Thu Jul 16 23:42:46 2020 +0000

    combine: Use single_set for is_just_move

    Since we now only call is_just_move on the original instructions, we
    always have an rtx_insn* (not just a pattern), so we can use single_set
    on it.  This makes no detectable difference at all on all thirty Linux
    targets I test, but it does help cris, and it is simpler, cleaner code
    anyway.

    2020-07-16  Hans-Peter Nilsson  <hp@axis.com>
                Segher Boessenkool  <segher@kernel.crashing.org>

            PR target/93372
            * combine.c (is_just_move): Take an rtx_insn* as argument.  Use
            single_set on it.=