From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Dynamic loading progress Date: Mon, 16 Feb 2015 14:09:01 -0500 Message-ID: References: <87r3twtagf.fsf@lifelogs.com> <85siebl7ws.fsf@stephe-leake.org> <85a90ilwmm.fsf@stephe-leake.org> <83386a6f7z.fsf@gnu.org> <85h9upjz7v.fsf@stephe-leake.org> <83wq3k3kl4.fsf@gnu.org> <85bnkwil1c.fsf@stephe-leake.org> <83pp9cwky8.fsf@gnu.org> <85a90ggf2d.fsf@stephe-leake.org> <54E0A40F.5080603@dancol.org> <83sie7un20.fsf@gnu.org> <54E0D181.2080802@dancol.org> <83r3trulse.fsf@gnu.org> <54E0D7E0.305@[87.69.4.28]> <83h9unukbg.fsf@gnu.org> <54E0DEF8.7020901@dancol> <83egpruiyp.fsf@gnu.org> <54E0FF93.2000104@dancol.org> <833865vp4d.fsf@gnu.org> <54E2355A.9010900@dancol.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1424113778 7184 80.91.229.3 (16 Feb 2015 19:09:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 16 Feb 2015 19:09:38 +0000 (UTC) Cc: Eli Zaretskii , stephen_leake@stephe-leake.org, emacs-devel@gnu.org To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 16 20:09:30 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YNR2w-0002a7-06 for ged-emacs-devel@m.gmane.org; Mon, 16 Feb 2015 20:09:30 +0100 Original-Received: from localhost ([::1]:41518 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YNR2v-0001fW-81 for ged-emacs-devel@m.gmane.org; Mon, 16 Feb 2015 14:09:29 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43367) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YNR2r-0001f1-G1 for emacs-devel@gnu.org; Mon, 16 Feb 2015 14:09:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YNR2k-0004ha-Sh for emacs-devel@gnu.org; Mon, 16 Feb 2015 14:09:25 -0500 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:32852) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YNR2k-0004hP-N2; Mon, 16 Feb 2015 14:09:18 -0500 Original-Received: from pastel.home (lechon.iro.umontreal.ca [132.204.27.242]) by pruche.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id t1GJ9DGq015942; Mon, 16 Feb 2015 14:09:14 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 8E5DEF86; Mon, 16 Feb 2015 14:09:01 -0500 (EST) In-Reply-To: <54E2355A.9010900@dancol.org> (Daniel Colascione's message of "Mon, 16 Feb 2015 10:22:18 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV5219=0 X-NAI-Spam-Version: 2.3.0.9393 : core <5219> : inlines <2191> : streams <1391337> : uri <1856828> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:183174 Archived-At: >> You say "we don't lock ourselves into conservative stack-scanning >> GC", which I interpret as saying you don't want to rely on stack >> scanning to avoid a destructive GC in this case. But if we don't >> rely on that, where's the guarantee that such emacs_value will >> survive GC? > Emacs stores emacs_value values in a local reference table before > handing them to module code. I don't think this is worth the trouble. I'm perfectly OK to either require stack scanning or to require modules use the same GCPRO macros we use in core. If/when we get a new GC technology that is incompatible with our GCPROs and/or stack scanning, well, then modules will break, but so will the rest of the Emacs core code so it's only fair. Stefan "who didn't read the rest of this thread, sorry"