Deutsch English Français Italiano |
<memo.20240830090549.19028u@jgd.cix.co.uk> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: jgd@cix.co.uk (John Dallman) Newsgroups: comp.arch Subject: Re: Computer architects leaving Intel... Date: Fri, 30 Aug 2024 09:05 +0100 (BST) Organization: A noiseless patient Spider Lines: 42 Message-ID: <memo.20240830090549.19028u@jgd.cix.co.uk> References: <vaqgtl$3526$1@dont-email.me> Reply-To: jgd@cix.co.uk Injection-Date: Fri, 30 Aug 2024 10:05:50 +0200 (CEST) Injection-Info: dont-email.me; posting-host="38033b2def40f84b61277130ee7f3660"; logging-data="451262"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/Sbm+wa7i6sfrPFrQLJIim2TORkvXxn1Q=" Cancel-Lock: sha1:FxMHEsY8e6JdFOmQHFE0Aj9mX0I= X-Clacks-Overhead-header: GNU Terry Pratchett Bytes: 2553 In article <vaqgtl$3526$1@dont-email.me>, cr88192@gmail.com (BGB) wrote: > On 8/29/2024 11:23 AM, MitchAlsup1 wrote: > > With differing instructions, how does a software vendor write > > software such that it can run near optimally on any implementation? > > They presumably target whatever is common, or the least common > denominator (such as RV64G or RV64GC), and settle with "probably > good enough"... ISVs can be proactive or passive about adopting a new ISA. Anyone promoting a new ISA wants to motivate them to be proactive, but faces problems with prerequisites: * Who can work with simulators, and who needs hardware? * Different kinds of software need more or less powerful hardware. * Application people need an OS and development tools at minimum. * Quite often they need other software: math libraries, databases, etc. > But, probably not too much different from other ISAs, just with a > lot more parties involved. Variant ISAs create fear, uncertainty and doubt, and that means delay. ISA promotors fear delay, because their investors will run out of patience. > The alternative is that one expects that all the software be > rebuilt for the specific configuration being used, ISVs /really/ don't like that. It multiplies their testing and QA and those are expensive. It rarely shows up problems, but convincing themselves to do without it is hard for them. > or recompiled from source or some other distribution format on > the local machine which it is to be run (with binaries distributed > as some form of "portable IR"). ISVs get sceptical about that, because it's generating code they have not tested. John