Re: MPS: native comp

["Gerd Möllmann" <gerd.moellmann@gmail.com>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: emacs-devel missing value <emacs-devel@gnu.org>
>> Date: Mon, 29 Apr 2024 07:35:05 +0200
>> 
>> So, it looks like the string constant "Eager..." is a reference that is
>> not traced. Can you please tell me where I can find these string
>> constants in native cu data structures?
>
> I'm not Andrea, but (risking to tell you what you already know): The
> string "Eager macro-expansion failure: %S" comes from the function
> internal-macroexpand-for-load, defined in macroexp.el.  It is the
> error message shown when we signal an error from that function.
> internal-macroexpand-for-load is called from
> lread.c:readevalloop_eager_expand_eval, which is called from readevalloop.
>
> Why that string is not traced, I don't know, since it comes from Lisp.
> Do we do something special with string constants in the calls to
> 'error', when we compile such Lisp code?

My model of this is that constants contained in the Lisp program that is
being natived-compiled, land in the dylib, somewhere in the data
segment. Like for C, say. I think Andrea confirmed that.

Then, in some way Andrea sets up Lisp_Objects for what we have in the
dylib when it is loaded and these land in data_vec.

But... I'm already tracing data_vec, so there must be something else...