Well, the Elisp and Scheme integration is pretty great. Maybe you know all of the following, but for those who didn't: - There's no data type conversion because the same object in memory is the right
It looks like I had some cruft in my emacs directory from when I experimented with the native compilation branch that make clean couldn't clean up. A git clean -dfx got me going again. That said, 4ac
[...] ATM if using --with-nativecomp libgccjit is not present (or non functional) we stop at configure time with an error. I guess that's one of the hairs we'll have to split then :) Andrea
I think there are two hairs here. Having an emacs compiled with nativecomp behave cleanly if libgccjit is not available at runtime. And having a runtime mechanism for switching nativecomp of totally
Right, at this stage this should be easy to implement (on Windows). We should define "switching nativecomp of" and the triggering mechanism, this might be already implmentented. Andrea
Well, I view the bytecode compiler as a crutch to get to LIMPLE for native compilation ;-) I'm all for a revolution, but it might be a bit early to chop off this particular king's head... Except for
I'll get there. Until we have good debugging support for byte-compiled code, the interpreter isn't going anywhere, indeed. But error reporting from the interpreter is very secondary because in my vi
Yes, but there's a good chance we would have had that anyway, since it's "only" a factor of two, at most. I see similarities to how we decide how many processes to use for native compilation. The cur
Greetings, all! My name is Andy, and together with Ludovic Courtès I co-maintain Guile. I meant to put off writing this note until some months in the future, but as people seem to be interested in t
I find this very interesting. Do you have some form of plan how to integrate this form of Guile and Emacs? Can it be done incrementally, that is, can the current elisp system and the guile system coe
Parallel builds are supported by the native Windows build of GNU Make since v3.81. So if you have mingw32-make v3.81 or 3.82, you should be all set for parallelism. Like I said: you need to say "min
Hi Alex, I believe so far what we have is this: https://elpa.gnu.org/packages/elisp-benchmarks.html Note that you have to native compile by hand the tests because this package doesn't know about nati
I think this is looking in the wrong direction: DESTDIR is almost _never_ defined. It exists for a corner use case, so much so that I even don't think it will help to describe that use cased here. M
I'd seen &aux before but didn't look up what it does until now, and I must say I share Stefan's sentiment :). Let's just say I would sooner see native arglists gain support for keyword arguments ;).
I did C-h f elisp-benchmark-run and navigated to the file and executed (native-compile (buffer-file-name)) and waited for it to dump the .eln filename. The results don't seem that impressive so I don
Sorry, I suspect I misunderstood. What's a native arglist? Doesn't defmacro already have native support for &optional and &rest keywords? I guess I'm confused, again. The arity of macro being defined
Uh, no? In Lisp, functions are bound to the function cell of a symbol which is different from the value cell of a symbol. In GUILE, nothing is bound to a symbol at all. Modules establish a mapping be
Yes I guess we should do something like that. Either add a table or support the native compilation when available and the entry function is called with the compile parameter set to t. Andrea -- addre
I added elisp-benchmarks.git to my .emacs.d and included in the load-path but it fell over: (require 'elisp-benchmark) (elb-run) But Messages show: Compiling nbody.el Wrote /home/alex/.emacs.d/elisp-