From: Andrea Corallo <acorallo@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Helmut Eller <eller.helmut@gmail.com>,
Emacs Devel <emacs-devel@gnu.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: MPS: Please check if scratch/igc builds with native compilation
Date: Thu, 23 May 2024 08:15:19 -0400 [thread overview]
Message-ID: <yp1r0dsybag.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m25xv46d9v.fsf@pro2.fritz.box> ("Gerd Möllmann"'s message of "Thu, 23 May 2024 12:19:56 +0200")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Helmut Eller <eller.helmut@gmail.com> writes:
>
>> On Thu, May 23 2024, Gerd Möllmann wrote:
>>
>>> Not for me :-(.
>>
>> Can something like
>>
>> for (EMACS_INT i = 0; i < d_vec_len; i++)
>> data_relocs[i] = AREF (comp_u->data_vec, i);
>>
>> trigger a GC flip in the middle of the array?
>
> Hm.
>
>> Maybe only on macOS? Maybe we should be extra
>> careful and register the roots before writing to data_relocs?
>
> Could be.
>
> Even nices would we if things like struct Lisp_X *d_reloc|[123] were
> struct Lisp_X **d_reloc. Then one could just set a pointer, for example
> to v->contents of a vector that is currently there anyway. No idea why
> that isn't the case.
I don't think we want an indirection more there, generated code would be
slower.
Andrea
next prev parent reply other threads:[~2024-05-23 12:15 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 14:00 MPS: Please check if scratch/igc builds with native compilation Gerd Möllmann
2024-05-21 16:57 ` Andrea Corallo
2024-05-21 17:02 ` Gerd Möllmann
2024-05-21 17:06 ` Gerd Möllmann
2024-05-21 17:57 ` Andrea Corallo
2024-05-21 18:09 ` Gerd Möllmann
2024-05-21 18:17 ` Andrea Corallo
2024-05-21 19:00 ` Gerd Möllmann
2024-05-21 19:05 ` Andrea Corallo
2024-05-21 19:08 ` Gerd Möllmann
2024-05-21 19:20 ` Andrea Corallo
2024-05-21 19:21 ` Eli Zaretskii
2024-05-21 19:23 ` Gerd Möllmann
2024-05-21 18:35 ` Eli Zaretskii
2024-05-21 18:34 ` Helmut Eller
2024-05-21 18:46 ` Andrea Corallo
2024-05-21 19:10 ` Helmut Eller
2024-05-21 19:17 ` Andrea Corallo
2024-05-21 19:35 ` Andrea Corallo
2024-05-21 19:38 ` Gerd Möllmann
2024-05-21 19:50 ` Andrea Corallo
2024-05-21 19:22 ` Eli Zaretskii
2024-05-21 19:28 ` Andrea Corallo
2024-05-22 5:43 ` Helmut Eller
2024-05-22 6:07 ` Gerd Möllmann
2024-05-22 6:27 ` Gerd Möllmann
2024-05-22 6:34 ` Helmut Eller
2024-05-22 6:56 ` Gerd Möllmann
2024-05-22 7:59 ` Helmut Eller
2024-05-22 8:46 ` Gerd Möllmann
2024-05-22 18:03 ` Gerd Möllmann
2024-05-23 6:12 ` Gerd Möllmann
2024-05-23 6:38 ` Helmut Eller
2024-05-23 6:58 ` Gerd Möllmann
2024-05-23 6:40 ` Helmut Eller
2024-05-23 6:58 ` Gerd Möllmann
2024-05-23 7:12 ` Helmut Eller
2024-05-23 7:35 ` Gerd Möllmann
2024-05-23 7:38 ` Andrea Corallo
2024-05-23 7:50 ` Andrea Corallo
2024-05-23 7:52 ` Gerd Möllmann
2024-05-23 7:57 ` Gerd Möllmann
2024-05-23 8:12 ` Helmut Eller
2024-05-23 8:18 ` Gerd Möllmann
2024-05-23 8:42 ` Andrea Corallo
2024-05-23 9:06 ` Helmut Eller
2024-05-23 9:14 ` Gerd Möllmann
2024-05-23 9:39 ` Helmut Eller
2024-05-23 10:19 ` Gerd Möllmann
2024-05-23 10:35 ` Ihor Radchenko
2024-05-23 11:27 ` Gerd Möllmann
2024-05-23 12:15 ` Andrea Corallo [this message]
2024-05-23 14:46 ` Helmut Eller
2024-05-23 16:40 ` Gerd Möllmann
2024-05-23 18:26 ` Helmut Eller
2024-05-24 3:10 ` Gerd Möllmann
2024-05-24 13:01 ` Gerd Möllmann
2024-05-24 14:19 ` Helmut Eller
2024-05-25 7:37 ` Gerd Möllmann
2024-05-25 14:38 ` Gerd Möllmann
2024-05-25 15:02 ` Andrea Corallo
2024-05-25 15:07 ` Gerd Möllmann
2024-05-25 15:26 ` Andrea Corallo
2024-05-25 15:29 ` Gerd Möllmann
2024-05-25 20:04 ` Andrea Corallo
2024-05-25 15:11 ` Eli Zaretskii
2024-05-26 7:39 ` Gerd Möllmann
2024-05-23 12:09 ` Andrea Corallo
2024-05-23 8:30 ` Ihor Radchenko
2024-05-22 8:18 ` Helmut Eller
2024-05-22 8:39 ` Gerd Möllmann
2024-06-03 5:35 ` 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=yp1r0dsybag.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.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).