Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: comp.arch Subject: Re: OoO execution Date: Wed, 16 Jul 2025 17:45:20 -0400 Organization: A noiseless patient Spider Lines: 11 Message-ID: References: <100apst$hsll$1@dont-email.me> <100bs7t$rna2$1@dont-email.me> <20250518182303.00003542@yahoo.com> <76948d869e78f8cb511809bd159008fd@www.novabbs.com> <100e352$1d61i$3@dont-email.me> <2025May19.082242@mips.complang.tuwien.ac.at> <8cbd51d6e62b575d9c2bf6b8cfa684af@www.novabbs.com> <100g2s6$1pp8t$1@dont-email.me> <1058cru$p1jc$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Wed, 16 Jul 2025 23:45:21 +0200 (CEST) Injection-Info: dont-email.me; posting-host="1a14ecbc9b071f10f9410f940f34ee8e"; logging-data="991375"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+I8EkBiiUbLTy42DQCrXOqd5SZVup/oQU=" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:hrxunqvXfGMIVH3M44Wqnj3fYMY= sha1:pSNF+MVr7Kva6TTUsgxr2/lw3Io= > I don't know about PPro in the integer section, but it was definitely > OoO in branches, the memory section, and in the PFU. So, I don't see > why they would not have had integer OoO. For the /91 I can see some potential simplifications to keep some parts in-order, but for the PPro it seems to me that the requirements of precise-exceptions make it so having some parts OoO and some parts in-order wouldn't give much benefits (if any). Stefan