[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Optimising Elisp code [again]
From: |
tomas |
Subject: |
Re: Optimising Elisp code [again] |
Date: |
Mon, 8 Oct 2018 16:43:22 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Mon, Oct 08, 2018 at 04:11:14PM +0200, Emanuel Berg wrote:
> Garreau, Alexandre wrote:
>
> > I kind of forgot why jumps are slow
>
> Isn't it as simple as all the overhead of
> placing the new function on the stack with
> return pointers and stuff?
And cold caches, and pipeline stalls and...
Modern processors are quite complex beasts, and much of it has to
do with the sad fact that RAM is much, much, MUCH slower than the
CPU, and they try to lie to you about it...
Cheers
-- tomás
signature.asc
Description: Digital signature
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], (continued)
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], tomas, 2018/10/06
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Garreau, Alexandre, 2018/10/06
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], tomas, 2018/10/07
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Garreau, Alexandre, 2018/10/07
- Message not available
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/07
- Message not available
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/07
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Stefan Monnier, 2018/10/07
- Message not available
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/07
- Re: Optimising Elisp code [again], Garreau, Alexandre, 2018/10/07
- Message not available
- Re: Optimising Elisp code [again], Emanuel Berg, 2018/10/08
- Re: Optimising Elisp code [again],
tomas <=
- Message not available
- Re: Optimising Elisp code [again], Barry Margolin, 2018/10/08
- Re: Optimising Elisp code [again], Emanuel Berg, 2018/10/09
- Re: Optimising Elisp code [again], Garreau, Alexandre, 2018/10/09
- Message not available
- Re: Optimising Elisp code [again], Emanuel Berg, 2018/10/09
- Re: Optimising Elisp code [again], Garreau, Alexandre, 2018/10/09
- Message not available
- Re: Optimising Elisp code [again], Emanuel Berg, 2018/10/09
- Re: Optimising Elisp code [again], Garreau, Alexandre, 2018/10/09
- Re: Optimising Elisp code [again], Barry Margolin, 2018/10/10
- Re: Optimising Elisp code [again], Óscar Fuentes, 2018/10/10
- Re: Optimising Elisp code [again], Garreau, Alexandre, 2018/10/10