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 C80C2383FB94; Mon, 13 Feb 2023 14:33:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C80C2383FB94
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1676298830;
	bh=R2g7XCyASAS7itW5Cwf/1l9QmMqpIrFUosvWYOF/nfA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=tuq5b/QKBZrwSQXKAFQgY3Pw6dg7NUKwHuNYQQu6aPp8sTMJcx+Lyux8G8bC4w375
	 MnJbX3ZmndNTgJOLF8qDyFQpJOeXLxRjgBrWLA0e0dmuVYetdPryf+vQUjnQDu6QF1
	 Ipkx0toWD40K8+0VgC9d0Fx6xZ9cj0gCTF92X/+0=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug middle-end/108102] rust bootstrap comparison failure on
 s390x-linux-gnu
Date: Mon, 13 Feb 2023 14:33:48 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108102-35322-v861KtZnDG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108102-35322@http.gcc.gnu.org/bugzilla/>
References: <bug-108102-35322@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
List-Id: <gcc-rust.gcc.gnu.org>

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

--- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Stefan Schulze Frielinghaus
<stefansf@gcc.gnu.org>:

https://gcc.gnu.org/g:452db716d8debb6e09b85e4a0c0e73a047ed5c1d

commit r13-5964-g452db716d8debb6e09b85e4a0c0e73a047ed5c1d
Author: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>
Date:   Mon Feb 13 15:33:38 2023 +0100

    IBM zSystems: Do not propagate scheduler state across basic blocks
[PR108102]

    So far we propagate scheduler state across basic blocks within EBBs and
    reset the state otherwise.  In certain circumstances the entry block of
    an EBB might be empty, i.e., no_real_insns_p is true.  In those cases
    scheduler state is not reset and subsequently wrong state is propagated
    to following blocks of the same EBB.

    Since the performance benefit of tracking state across basic blocks is
    questionable on modern hardware, simply reset the state for each basic
    block.

    Fix also resetting f{p,x}d_longrunning.

    gcc/ChangeLog:

            PR target/108102
            * config/s390/s390.cc (s390_bb_fallthru_entry_likely): Remove.
            (struct s390_sched_state): Initialise to zero.
            (s390_sched_variable_issue): For better debuggability also emit
            the current side.
            (s390_sched_init): Unconditionally reset scheduler state.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=