Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Stefan Monnier <monnier@iro.umontreal.ca>
Newsgroups: comp.arch
Subject: Re: Stealing a Great Idea from the 6600
Date: Thu, 13 Jun 2024 12:52:07 -0400
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <jwvzfrobxll.fsf-monnier+comp.arch@gnu.org>
References: <lge02j554ucc6h81n5q2ej0ue2icnnp7i5@4ax.com>
	<v02eij$6d5b$1@dont-email.me>
	<152f8504112a37d8434c663e99cb36c5@www.novabbs.org>
	<v04tpb$pqus$1@dont-email.me> <v4f5de$2bfca$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Thu, 13 Jun 2024 18:52:07 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="a7718b9e88ab33048a514445d1aeb032";
	logging-data="2487632"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18tUsOYq4/dZTwVT6XEFRn5uUOyWPTWe/Y="
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:9SQ+9xhwx4Aa/klRKb4as7pWcPs=
	sha1:pMwSlAL6jjVR0zUF8fdYwZHHups=
Bytes: 1569

> This is a late reply, but optimal static ordering for N-wide may be
> very non-optimal for N-1 (or N-2, etc.).  As an example, assume a perfectly

AFAICT Terje was talking about scheduling for OoO CPUs, and wasn't
talking about the possible worst case situations, but about how things
usually turn out in practice.

For statically-scheduled or in-order CPUs, it can be indeed more
difficult to generate code that will run (almost) optimally on a variety
of CPUs.


        Stefan