From: Jonathon McKitrick via "Emacs development discussions." <emacs-devel@gnu.org>
To: Pip Cet <pipcet@protonmail.com>
Cc: "Jonathon McKitrick via \"Emacs development discussions.\""
<emacs-devel@gnu.org>
Subject: Re: Helping with MPS
Date: Tue, 20 Aug 2024 20:41:28 +0000 [thread overview]
Message-ID: <ZsT_eKIzFvLZV0qU@SDF.ORG> (raw)
In-Reply-To: <877ccbb3a9.fsf@protonmail.com>
On Tue, Aug 20, 2024 at 03:52:01PM +0000, Pip Cet wrote:
: "Jonathon McKitrick via \"Emacs development discussions.\"" <emacs-devel@gnu.org> writes:
: Thank you, that's great to hear! May I ask which operating system and
: CPU architecture they use?
MacOS on arm64
: 'M-x igc-stats RET s' should also work, and show a snapshot of MPS
: allocations. Just leaning on 'c' for a while in that buffer (which
: triggers a collection) has produced crashes in the past...
I'm not getting igc stats, and (featurep 'mps) returns nil.
So I thought this build was mps enabled, but apparently it's not.
I'm building again, and this time egrep finds 'with.mps' throughout
the configure script and a couple of other non-source code files.
I assume this is a source-built feature and not a linked library,
right? I don't understand why I don't see any references in .c files.
Jonathon McKitrick
--
'My other computer is your Windows box.'
next prev parent reply other threads:[~2024-08-20 20:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 15:37 Helping with MPS Jonathon McKitrick via Emacs development discussions.
2024-08-20 15:52 ` Pip Cet
2024-08-20 20:41 ` Jonathon McKitrick via Emacs development discussions. [this message]
2024-08-20 20:44 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 6:31 ` Helmut Eller
2024-08-21 6:56 ` Gerd Möllmann
2024-08-21 8:02 ` Pip Cet
2024-08-21 9:23 ` Helmut Eller
2024-08-21 13:53 ` Eli Zaretskii
2024-08-21 14:36 ` Helmut Eller
2024-08-21 14:44 ` Eli Zaretskii
2024-08-21 15:10 ` Helmut Eller
2024-08-21 15:34 ` Eli Zaretskii
2024-08-21 17:44 ` Helmut Eller
2024-08-21 18:06 ` Eli Zaretskii
2024-08-20 16:05 ` Helmut Eller
2024-08-20 21:42 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 3:46 ` Gerd Möllmann
2024-08-21 5:59 ` Helmut Eller
2024-08-21 6:28 ` Arash Esbati
2024-08-21 6:54 ` Gerd Möllmann
2024-08-21 14:10 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 14:48 ` Gerd Möllmann
2024-08-21 15:08 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 15:40 ` Gerd Möllmann
2024-08-21 15:46 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 16:23 ` Gerd Möllmann
2024-08-21 18:00 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 18:04 ` Gerd Möllmann
2024-08-21 18:20 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 18:43 ` Gerd Möllmann
2024-08-21 20:42 ` Jonathon McKitrick via Emacs development discussions.
2024-08-22 4:02 ` Gerd Möllmann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZsT_eKIzFvLZV0qU@SDF.ORG \
--to=emacs-devel@gnu.org \
--cc=jcm@SDF.ORG \
--cc=pipcet@protonmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).