| Deutsch English Français Italiano |
|
<20240812181453.00004e50@yahoo.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!3.eu.feeder.erje.net!feeder.erje.net!news2.arglkargh.de!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Michael S <already5chosen@yahoo.com> Newsgroups: comp.arch Subject: Re: Instruction Tracing Date: Mon, 12 Aug 2024 18:14:53 +0300 Organization: A noiseless patient Spider Lines: 33 Message-ID: <20240812181453.00004e50@yahoo.com> References: <v970s3$flpo$1@dont-email.me> <2024Aug10.121802@mips.complang.tuwien.ac.at> <v995pm$1cni$2@gal.iecc.com> <2024Aug11.164438@mips.complang.tuwien.ac.at> <v9bg6n$2u0ud$2@dont-email.me> <2024Aug12.072929@mips.complang.tuwien.ac.at> <v9cabd$363e5$1@dont-email.me> <20240812110918.00005ea5@yahoo.com> <v9chub$37gr9$5@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Injection-Date: Mon, 12 Aug 2024 17:14:17 +0200 (CEST) Injection-Info: dont-email.me; posting-host="2556c59b1c899658c092ba80d28007fd"; logging-data="3379084"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+ohDp4IyDYsgqSaCwx3wharmqJXJinGf4=" Cancel-Lock: sha1:nYb19txHUCyBCqgc7sRa6A6oA+A= X-Newsreader: Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-w64-mingw32) Bytes: 2626 On Mon, 12 Aug 2024 08:42:51 -0000 (UTC) Lawrence D'Oliveiro <ldo@nz.invalid> wrote: > On Mon, 12 Aug 2024 11:09:18 +0300, Michael S wrote: >=20 > > On Mon, 12 Aug 2024 06:33:17 -0000 (UTC) > > Lawrence D'Oliveiro <ldo@nz.invalid> wrote: > > =20 > >> But in spite of having, say, 2=C2=BD times the clock speed of POWER, > >> Alpha was not 2=C2=BD times faster, was it? =20 > >=20 > > Of course not. =20 >=20 > That=E2=80=99s what I mean: it took several clock cycles per instruction, > contrary to just about every other RISC architecture. On EV4 simple ALU instructions took 1 cycle , both for throughput and for latency.=20 Shifts and conditional moves had latency of 2, throughput of 1.=20 Integer multiplier was not pipelined, but few RISC also had it none-pipelined. Latency of integer multiplier was 19-21 cycles. On FP side both FADD and FMUL were fully pipelined (T=3D1) and had latency of 6 cycles. L1D cache hits were fully pipelined (T=3D1) and had latency of 3 cycles. So, as long as code/data was fitting in L1 cache, EV4 IPC was not far behind competition. Relatively to MIPS R4K, may be, even ahead. Of course, cache misses were relatively more expensive than for much lower clocked competitors. DEC's solution to that was wide and fast system bus.