From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Rocky Bernstein Newsgroups: gmane.emacs.devel Subject: Re: GNU is looking for Google Summer of Code Projects Date: Thu, 19 Mar 2020 19:07:23 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f8ac5805a13d3bea" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="100835"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Monnier , emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Mar 20 00:08:28 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 1jF4H6-000Pyk-Pc for ged-emacs-devel@m.gmane-mx.org; Fri, 20 Mar 2020 00:08:28 +0100 Original-Received: from localhost ([::1]:44202 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jF4Gw-0001TD-7n for ged-emacs-devel@m.gmane-mx.org; Thu, 19 Mar 2020 19:08:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39990) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jF4GI-00013J-4a for emacs-devel@gnu.org; Thu, 19 Mar 2020 19:07:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jF4GG-0002W8-W3 for emacs-devel@gnu.org; Thu, 19 Mar 2020 19:07:38 -0400 Original-Received: from mail-lj1-f177.google.com ([209.85.208.177]:34406) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jF4GG-0002Ss-Oq for emacs-devel@gnu.org; Thu, 19 Mar 2020 19:07:36 -0400 Original-Received: by mail-lj1-f177.google.com with SMTP id s13so4493552ljm.1 for ; Thu, 19 Mar 2020 16:07:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:cc; bh=5ktuswCaLtddV67orMOhTnwWfGAaJYyDekbNprtYWns=; b=qIFIHR423/+eorGD/hjG8XZk+U48Iznb26LgBk/84Qw+qeEoGF0ROcfo7LAvqwA7Al njjiCUY8Os0ts819r8wdrfuqbsdlEfeVSN8pYi9dIBNaMWfzCYVr5KPW3wOIhu85jGsz 6iRuaG11nxmze9w71eMaFgKe8fBIP+9qmiB6jeOI8/07CnCdZg0eGv8jVK+uyUaIXhGA 6Dt/EH48H/hBVjGuwTzBN7g3EYxyy80+oeVFsRCt/PZHzKEmq+6uu0i2VP6AqwzO3za6 kbE6a+ZTK9czUAMGDOzbnZm0YDBvzu0qamg7Rom8SF6uI4Vnjoo5ZXwjEDmLFR9E1+9T K4Xw== X-Gm-Message-State: ANhLgQ1mRyzZjFmxfJ46malRY2nysU7uJEle1lXzSgiJT4hIp4DwNEqA FzITBNj6x6TH7eflbsjUNy3pWO9mzR3sEADuyg4= X-Received: by 2002:a05:651c:20b:: with SMTP id y11mt201559ljn.252.1584659254615; Thu, 19 Mar 2020 16:07:34 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.208.177 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:245595 Archived-At: --000000000000f8ac5805a13d3bea Content-Type: text/plain; charset="UTF-8" On Thu, Mar 19, 2020 at 5:45 PM Andrea Corallo wrote: > 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 > The above two I think a summer student could do. Clarification of item 2. There is *reporting* location information especially in traceback information on an error, which I suppose could be considered "to debug". 3 autogenerate GC and pdumper code from obj description > 4 GC > > Clear to me thanks. > > Andrea > > -- > akrl@sdf.org > --000000000000f8ac5805a13d3bea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Mar 19, 2020 at 5:45 PM Andre= a Corallo <akrl@sdf.org> wrote:
Stefan Monnier &l= t;monnier@iro= .umontreal.ca> 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 anywa= y.
>
> I get the impression that you were referring to the part where I talke= d
> about the "object description" for the runtime system.=C2=A0= Compilation is
> of no help here.=C2=A0 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 (mayb= e the
> Remacs work might qualify), but we'd still need to connect that wi= th
> 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

<= div>The above two I think a summer student could do.=C2=A0
Clarif= ication of item 2. There is=C2=A0reporting=C2=A0location information= especially in traceback information on an error, which I suppose could be = considered "to debug".=C2=A0

3 autogenerate GC and pdumper code from obj description
4 GC

Clear to me thanks.

=C2=A0 Andrea

--
akrl@sdf.org
--000000000000f8ac5805a13d3bea--