[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Optimising Elisp code [again]
From: |
Barry Margolin |
Subject: |
Re: Optimising Elisp code [again] |
Date: |
Mon, 08 Oct 2018 20:38:45 -0400 |
User-agent: |
MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) |
In article <mailman.1852.1539009893.1284.help-gnu-emacs@gnu.org>,
<tomas@tuxteam.de> wrote:
> 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...
Since we're talking about a byte-code interpreter, not machine code, the
pipeline is probably not relevant.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], (continued)
- 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, 2018/10/08
- Message not available
- Re: Optimising Elisp code [again],
Barry Margolin <=
- 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
- Message not available
- Re: Optimising Elisp code [again], Emanuel Berg, 2018/10/11