Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Thomas Koenig Newsgroups: comp.arch Subject: Re: Calling conventions (particularly 32-bit ARM) Date: Mon, 13 Jan 2025 21:33:32 -0000 (UTC) Organization: A noiseless patient Spider Lines: 20 Message-ID: References: <4903307dfcce354508c9fc016a4c1ea1@www.novabbs.org> Injection-Date: Mon, 13 Jan 2025 22:33:32 +0100 (CET) Injection-Info: dont-email.me; posting-host="8ae371d57a67ce9683d1f49b26012745"; logging-data="2157595"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/S0g4WwjJ9evDJyFrxBhoQR4IO+53JPGM=" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:1NwIoLKOxr+03YBP0VVmMJH12hE= Bytes: 1763 Stephen Fuld schrieb: > Has Lapack (and the other old style Fortran numeric > code that Waldek mentioned) lost its/their importance as a major user of > CPU cycles? It's less than it used to be in the days when supercomputers roamed the computer centers, but for these applications where it matters, it can be significant. > Or do these subroutines consume so many CPU cycles that the > overhead of the large number of parameters is lost in the noise? If you have many small matrices to multiply, startup overhead can be quite significant. Not on a 2000*2000 matrix, though. > Or is > there some other explanation for Mitch not considering their importance? I think eight arguments, passed by reference in registers, is not too bad.