From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=sttm=4V=ispras.ru=amonakov@sourceware.org>
Received: from mail.ispras.ru (mail.ispras.ru [83.149.199.84])
	by sourceware.org (Postfix) with ESMTPS id A40763858D1E
	for <gcc-patches@gcc.gnu.org>; Fri, 23 Dec 2022 17:31:52 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A40763858D1E
Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=ispras.ru
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=ispras.ru
Received: from [10.10.3.121] (unknown [10.10.3.121])
	by mail.ispras.ru (Postfix) with ESMTPS id C6D4640737A7;
	Fri, 23 Dec 2022 17:31:50 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.ispras.ru C6D4640737A7
Date: Fri, 23 Dec 2022 20:31:50 +0300 (MSK)
From: Alexander Monakov <amonakov@ispras.ru>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
cc: Qing Zhao <qing.zhao@oracle.com>, 
    "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH V2] Disable sched1 in functions that call setjmp
In-Reply-To: <87h6xmyqqq.fsf@oracle.com>
Message-ID: <3183d104-b852-eb38-d5ba-9578594015bd@ispras.ru>
References: <20221222173208.13317-1-jose.marchesi@oracle.com> <53b93d7e-a157-9116-d07a-4d51cd43d205@ispras.ru> <35CA4F79-CA10-4560-8920-CDA65810E308@oracle.com> <cf62c3ec-0a9e-275e-5efa-2689ff1f00e2@ispras.ru> <D53E1E66-F51C-47BF-99B1-EA49BDB29C9E@oracle.com>
 <f41bb491-fd14-801e-ed78-797a1408dffa@ispras.ru> <87h6xmyqqq.fsf@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org
List-Id: <gcc-patches.gcc.gnu.org>


On Fri, 23 Dec 2022, Jose E. Marchesi wrote:

> > (scheduling across calls in sched2 is somewhat dubious as well, but
> > it doesn't risk register pressure issues, and on VLIW CPUs it at least
> > can result in better VLIW packing)
> 
> Does sched2 actually schedule across calls?  All the comments in the
> source code stress the fact that the second scheduler pass (after
> register allocation) works in regions that correspond to basic blocks:
> "(after reload, each region is of one block)".

A call instruction does not end a basic block.

(also, with -fsched2-use-superblocks sched2 works on regions like sched1)

Alexander