all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: pdumper's performance
Date: Tue, 04 Sep 2018 17:49:25 -0400	[thread overview]
Message-ID: <jwvwos1aqpo.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 282958d399469f8d3631f5bee14d857f.squirrel@dancol.org

>> Hm... there's a misunderstanding: the issue is not one of performance
>> problem, but of separation of concerns.  Moving the markbits elsewhere
>> should be done in a separate patch (before or after the pdumper patch).
> There is no separation-of-concerns problem. The mark bit thing isn't some
> unrelated bonus feature of pdumper.

Then I don't understand yet: could you explain why pdumper needs to put
the markbits elsewhere for pdump'd objects than for non-pdump'd objects?

Since the layout of the markbits was designed without thinking of the
pdumper case, I can imagine that maybe the current placement of markbits is
inconvenient for the pdumper case (tho I don't actually which part is
inconvenient).

But surely there should be a way to layout the markbits such that it's
convenient both for pdump'd and the non-pdump'd objects.


        Stefan




  reply	other threads:[~2018-09-04 21:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 20:29 pdumper's performance Stefan Monnier
2018-08-29 22:10 ` Daniel Colascione
2018-08-30  2:14   ` Stefan Monnier
2018-08-30  5:19     ` Daniel Colascione
2018-09-04 16:26       ` Stefan Monnier
2018-09-04 16:42         ` Daniel Colascione
2018-09-04 19:30           ` Stefan Monnier
2018-09-04 19:35             ` Daniel Colascione
2018-09-04 20:58               ` Stefan Monnier
2018-09-04 21:20                 ` Daniel Colascione
2018-09-04 21:49                   ` Stefan Monnier [this message]
2018-09-04 21:33                 ` 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

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

  git send-email \
    --in-reply-to=jwvwos1aqpo.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.