Deutsch   English   Français   Italiano  
<bfdecc4197ba45eebcd15a65e1627b4d@www.novabbs.org>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: mitchalsup@aol.com (MitchAlsup1)
Newsgroups: comp.arch
Subject: Re: Efficiency of in-order vs. OoO
Date: Tue, 1 Oct 2024 18:45:11 +0000
Organization: Rocksolid Light
Message-ID: <bfdecc4197ba45eebcd15a65e1627b4d@www.novabbs.org>
References: <2024Mar25.193535@mips.complang.tuwien.ac.at> <memo.20240325202221.1408H@jgd.cix.co.uk> <PolMN.100748$_a1e.89032@fx16.iad> <2024Mar26.102754@mips.complang.tuwien.ac.at> <hMAMN.122731$SyNd.31862@fx33.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="139425"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="o5SwNDfMfYu6Mv4wwLiW6e/jbA93UAdzFodw5PEa6eU";
User-Agent: Rocksolid Light
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Site: $2y$10$CkYJ.64fD3Bex.qnnum16usNFr8BzrWfVGjOrhP2y1a69PgzOZ1LW
X-Rslight-Posting-User: cb29269328a20fe5719ed6a1c397e21f651bda71
Bytes: 2148
Lines: 25

On Tue, 26 Mar 2024 14:15:41 +0000, Scott Lurndal wrote:

> anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:
>>scott@slp53.sl.home (Scott Lurndal) writes:
>>>The biggest demand is from the OS vendors.    Hardware folks have
>>>simulation and emulators.
>>
>>You don't want to use a full-blown microarchitectural emulator for a
>>long-running program.
>
> Generally hardware folks don't run 'long-running programs' when
> analyzing performance, they use the emulator for determining latencies,
> bandwidths and efficiacy of cache coherency algorithms and
> cache prefetchers.
>
> Their target is not application analysis.

It is sequence compliance. At this point in the game all the FUs
are known to produce correct results. But we live in a world
where::
a) The test case takes the correct number of cycles
b) leaves all the right bit patterns in registers and memory
c) took at the right directions at all the branches
d) and went through an invalid sequence to get there.

HW verification is mostly about proving the sequencers are correct.