From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: On elisp running native Date: Tue, 31 Dec 2019 18:47:57 +0200 Message-ID: <83imlwl9vm.fsf@gnu.org> References: <83tv5mp48l.fsf@gnu.org> <83sgl0lchm.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="75747"; mail-complaints-to="usenet@blaine.gmane.org" Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 31 17:48:26 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1imKh0-000JZd-0U for ged-emacs-devel@m.gmane.org; Tue, 31 Dec 2019 17:48:26 +0100 Original-Received: from localhost ([::1]:44414 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imKgy-00089I-0C for ged-emacs-devel@m.gmane.org; Tue, 31 Dec 2019 11:48:24 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58692) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imKgP-0007jL-L8 for emacs-devel@gnu.org; Tue, 31 Dec 2019 11:47:50 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51839) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1imKgP-0004C7-81; Tue, 31 Dec 2019 11:47:49 -0500 Original-Received: from [176.228.60.248] (port=2033 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1imKgO-0006B7-Nr; Tue, 31 Dec 2019 11:47:49 -0500 In-reply-to: (message from Andrea Corallo on Tue, 31 Dec 2019 16:21:58 +0000) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243815 Archived-At: > From: Andrea Corallo > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org > Date: Tue, 31 Dec 2019 16:21:58 +0000 > > Eli Zaretskii writes: > > >> From: Andrea Corallo > >> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org > >> Date: Tue, 31 Dec 2019 10:24:37 +0000 > >> > >> For the branch name would 'gccemacs' be fine? > > > > The "emacs" part is redundant, so I'd suggest "libgccjit" instead. > > The libgccjit interface and dependency is just a part of the realized > infrastructure (also in discussion). I'd like to call it something like > "native-comp" or "native-lisp". I believe is more descriptive of what > I've done and of its scope. Thinking about is not even a jit > compiler... We are splitting hair, but... "native-SOMETHING" is too general. E.g., we already had a serious attempt to produce native code, by using libjit. We may have additional attempts; for example Paul Eggert once proposed to teach Emacs to generate C code from Lisp, and then compile it. The advantage of libgccjit is that it pinpoints the main component on which this particular implementation is based, so future attempts to do it differently will not clash with the name. That said, it's just a name. If you feel strongly about it, I won't object. > >> Should I squash all my history or keep it as it is? The branch went > >> through quite some experimentations. I'm not sure about its history > >> value. > > > > It's completely up to you, since it's your history. > > If is possible to postpone the history rework to before the eventual > merge I guess I'll prefer to do so. It's a bit messy but if it does not > bother others it does not bother me. That's fine. > - Is force push allowed in these feature branches? For such a large feature I'd prefer not to do that, assuming that some people will want to track that branch and perhaps contribute changes and patches. Why would force-push be necessary? > - Should it go in / /feature or /scratch ? Under feature/, please. Thanks.