unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: stefan@marxist.se, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: "Bringing GNU Emacs to Native Code" at the European Lisp Symposium
Date: Sat, 02 May 2020 23:44:51 -0400	[thread overview]
Message-ID: <E1jV5Yh-0001xQ-B0@fencepost.gnu.org> (raw)
In-Reply-To: <xjf7dxuwtuo.fsf@sdf.org> (message from Andrea Corallo on Sat, 02 May 2020 09:48:15 +0000)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > This the point.  I think we could at best make this assumption only on
  > calls to C primitives (that we assume cannot be redefined) that are
  > known to be side effect free and not to use global variable bindings in
  > general.  Any other call must have all variables spilled first.

You're concerned about the possibility of redefining Lisp functions
defined in other files, and that the new function definitions might
touch variables bound in your file.

I think it is legitimate to compile assuming they don't do that.  How
about seeing where you can get, that way?

  >   Given the discussed
  > suspect of poor performance I intentionally left this task aside to work
  > on more urgent tasks.  Nothing prevents to have a try on this later if
  > we think is really important.

That seems right to me.  I am not saying this particular issue is urgent.
Only that it should get done by and by.

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2020-05-03  3:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 17:11 "Bringing GNU Emacs to Native Code" at the European Lisp Symposium Stefan Kangas
2020-04-28 19:25 ` Andrea Corallo
2020-04-28 19:35   ` Amin Bandali
2020-04-28 20:06     ` Andrea Corallo
2020-04-28 21:13       ` Amin Bandali
2020-04-29  3:24   ` Richard Stallman
2020-04-29 18:47     ` Andrea Corallo
2020-04-28 19:36 ` tomas
2020-04-28 22:00 ` Drew Adams
2020-04-28 22:18   ` Stefan Monnier
2020-04-28 22:51     ` Drew Adams
2020-04-29  7:04     ` Eli Zaretskii
2020-04-29 12:38       ` Stefan Monnier
2020-04-29 14:02         ` Eli Zaretskii
2020-04-28 22:38   ` Dmitry Gutov
2020-04-29 10:55   ` Andrea Corallo
2020-04-29 15:35     ` Drew Adams
2020-04-29 18:57       ` Andrea Corallo
2020-04-29 19:29         ` Drew Adams
2020-04-30  1:14           ` Stefan Monnier
2020-04-30  2:27   ` Richard Stallman
2020-04-30  3:00     ` Stefan Monnier
2020-05-02  2:21       ` Richard Stallman
2020-05-02 13:43         ` Stefan Monnier
2020-04-30 20:32     ` Andrea Corallo
2020-05-02  2:27       ` Richard Stallman
2020-05-02  9:48         ` Andrea Corallo
2020-05-03  3:44           ` Richard Stallman [this message]
2020-05-03  4:28             ` Stefan Monnier
2020-05-04  3:09               ` Richard Stallman
2020-05-04  5:17                 ` Stefan Monnier
2020-05-05  2:56                   ` Richard Stallman
2020-05-05  3:18                     ` Stefan Monnier
2020-05-04 10:07             ` Andrea Corallo
2020-05-02 13:50         ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1jV5Yh-0001xQ-B0@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=akrl@sdf.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=stefan@marxist.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).