From: Keith David Bershatsky <esq@lawlist.com>
To: Alex Gramiak <agrambot@gmail.com>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: NS port: How to debug excessive garbage collection?
Date: Mon, 15 Apr 2019 22:51:46 -0700 [thread overview]
Message-ID: <m2r2a2zedp.wl%esq@lawlist.com> (raw)
Thank you, Alex, for pinpointing my error in the call to memset.
Greatly appreciated!
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> Date: [04-15-2019 22:26:05] <15 Apr 2019 23:26:05 -0600>
> From: Alex Gramiak <agrambot@gmail.com>
> To: Keith David Bershatsky <esq@lawlist.com>
> Cc: eliz@gnu.org, emacs-devel@gnu.org
> Subject: Re: NS port: How to debug excessive garbage collection?
>
> * * *
>
> The problem here is that since you changed the single struct cache to an
> array of caches, you need to also change the memset call to match it.
> Right now you are setting the pointer variable to 0/NULL. It should now
> be:
>
> memset (w->mc_elts, 0, w->mc_nelts * (sizeof *w->mc_elts));
>
> Which sets the memory block of mc_nelts cache structs pointed to
> by mc_elts to 0.
next reply other threads:[~2019-04-16 5:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 5:51 Keith David Bershatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-16 2:57 NS port: How to debug excessive garbage collection? Keith David Bershatsky
2019-04-16 5:26 ` Alex Gramiak
2019-04-15 5:19 Keith David Bershatsky
2019-04-15 2:55 Keith David Bershatsky
2019-04-15 3:44 ` Alex Gramiak
2019-04-14 19:46 Keith David Bershatsky
2019-04-14 23:31 ` Alex Gramiak
2019-04-14 7:41 Keith David Bershatsky
2019-04-13 18:07 Keith David Bershatsky
2019-04-13 21:41 ` Alex Gramiak
2019-04-14 3:47 ` Daniel Colascione
2019-04-13 16:31 Keith David Bershatsky
2019-04-13 17:02 ` Alex Gramiak
2019-04-13 5:55 Keith David Bershatsky
2019-04-13 6:48 ` Eli Zaretskii
2019-04-11 23:04 Keith David Bershatsky
2019-04-12 9:30 ` Eli Zaretskii
2019-04-11 3:27 Keith David Bershatsky
2019-04-11 14:14 ` Eli Zaretskii
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=m2r2a2zedp.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=agrambot@gmail.com \
--cc=eliz@gnu.org \
--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.