From 507fc64df3ed10e985a24af92e59628ff03f1b85 Mon Sep 17 00:00:00 2001 From: Sacha Chua Date: Wed, 8 Dec 2021 01:07:18 -0500 Subject: Add chapters for native --- 2021/info/native-schedule.md | 34 +++++++++++++++++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-) (limited to '2021/info') diff --git a/2021/info/native-schedule.md b/2021/info/native-schedule.md index 5b813005..d1e0478b 100644 --- a/2021/info/native-schedule.md +++ b/2021/info/native-schedule.md @@ -13,7 +13,39 @@ If you have questions and the speaker has not indicated public contact informati # Q&A -
+
    +
  1. 00:00 Thanks
    2. +
  2. 01:16 Why is Elisp not a general-purpose programming language, at least not completely?
    3. +
  3. 02:05 Is this activity related to the garbage collector?
    4. +
  4. 02:37 Is the idea to eventually develop Emacs itself in Elisp?
    5. +
  5. 03:42 How did you work on this?
    6. +
  6. 04:27 Does this compilation pipeline introduce vulnerabilities?
    7. +
  7. 05:39 What code, if any, will still benefit significantly from being written in C?
    8. +
  8. 07:28 What's the risk of (setq native-comp-speed 3)?
    9. +
  9. 08:49 Are there any limits introduced by native comp with respect to runtime introspectability, changeability/redefinability, etc?
    10. +
  10. 09:15 Is there a benefit in setting native-comp-compiler-options to "-mtune=native -march="?
    11. +
  11. 10:11 You mentioned native-comp coming in emacs 28. Will this be the default at build time, or will distros have to set this themselves?
    12. +
  12. 11:54 Could we avoid libgccjit.so? Or consider using another jit lib (e.g. dynasm used by luajit) et al to gain better optimization?
    13. +
  13. 14:22 How much of Emacs's C code base could be translated to emacs-lisp? What is the minimum C code base necessary?
    14. +
  14. 16:23 Could we statically type elisp code (via macros?) to provide more optimization hints to compiler?
    15. +
  15. 17:27 Elisp and Python all are dynamically typed langauge, but benchmark shows that Elisp runs slower than Python. Could we learn some best practices from the Python community?
    16. +
  16. 18:55 Did you try to optimize with Rust too? What are your thoughts on Rust for this particular optimization and security?
    17. +
  17. 21:35 Does the native compilation interface with the Emacs profiling tools?
    18. +
  18. 22:59 Where did funding for your work come from?
    19. +
  19. 27:04 What kind of application do I envision native comp enabling to work well in Emacs in the next few years, and which one would not be possible?
    20. +
  20. 28:36 Is this the first real-world practical use of libgccjit?
    21. +
  21. 29:47 Is there any task you need help with?
    22. +
  22. 33:49 What's a good way to proceed?
    23. +
  23. 38:37 What kind of packages do you think could now be practical with native comp?
    24. +
  24. 40:46 Why not implement Emacs Lisp in Guile and use Guile's compiler?
    25. +
  25. 46:29 What are some other hobbies/interests of yours besides Emacs?
    26. +
  26. 48:27 Will you be presenting at ELS or anywhere else in the next year?
    27. +
  27. 51:04 How to make Emacs more popular?
    28. +
  28. 59:46 Do you have 'wish list' features, things you long for Emacs to be able to do?
    29. +
  29. 01:02:04 From BBB chat: dickmao has a patch that makes Gnus async....
    30. +
  30. 01:05:33 Advice for anyone who wants to bring something into Emacs core
    31. +
  31. 01:10:20 Do you have any advice on how to approach the upstream development community?
    32. +
# Description -- cgit v1.2.3