From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: GNU is looking for Google Summer of Code Projects Date: Thu, 19 Mar 2020 21:45:43 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="14869"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) Cc: Rocky Bernstein , emacs-devel To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 19 22:46:37 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jF2zt-0003m0-1a for ged-emacs-devel@m.gmane-mx.org; Thu, 19 Mar 2020 22:46:37 +0100 Original-Received: from localhost ([::1]:43510 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jF2zs-00019u-4o for ged-emacs-devel@m.gmane-mx.org; Thu, 19 Mar 2020 17:46:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53564) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jF2z7-0000k6-6n for emacs-devel@gnu.org; Thu, 19 Mar 2020 17:45:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jF2z3-0006hG-UH for emacs-devel@gnu.org; Thu, 19 Mar 2020 17:45:48 -0400 Original-Received: from mx.sdf.org ([205.166.94.20]:49560) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jF2z3-0006ga-Bg; Thu, 19 Mar 2020 17:45:45 -0400 Original-Received: from sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 02JLji5Z003122 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Thu, 19 Mar 2020 21:45:44 GMT Original-Received: (from akrl@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 02JLjhtH021349; Thu, 19 Mar 2020 21:45:43 GMT In-Reply-To: (Stefan Monnier's message of "Thu, 19 Mar 2020 17:26:24 -0400") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 205.166.94.20 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:245592 Archived-At: Stefan Monnier writes: >> Do we really need some dedicated low level object? > > I don't know what you mean, sorry. > >> This should be all overhead that disappears with compilation anyway. > > I get the impression that you were referring to the part where I talked > about the "object description" for the runtime system. Compilation is > of no help here. It's already all happening in C code. > > Maybe rewriting in a language with a bit more introspection might make > an "object description" more-or-less readily available (maybe the > Remacs work might qualify), but we'd still need to connect that with > a GC and with pdump etc... Ops I now understand, we are talking about 4 different problems: 1 source location going through the compilation pipeline 2 debug information into bytecode to debug 3 autogenerate GC and pdumper code from obj description 4 GC Clear to me thanks. Andrea -- akrl@sdf.org