Re: MPS: native comp

[Andrea Corallo <acorallo@gnu.org>]

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
>> That promises to become fun :-/
>
> Sometimes one needs a bit of luck. Another try landed me in an abort in
> set_internal, and I could see that we have another case of a symbol
> pointing to a tombstone. So, we have another reference in the
> compilation unit that we don't trace.

Maybe you can make it more reproducible building at -J1?

> @Andrea: Any intuition where else references could lurk, perhaps? I'm
> currently doing this:
>
> static mps_res_t
> fix_comp_unit (mps_ss_t ss, struct Lisp_Native_Comp_Unit *u)
> {
>   MPS_SCAN_BEGIN (ss)
>   {
>     IGC_FIX_CALL_FN (ss, struct Lisp_Vector, u, fix_vectorlike);
>     if (u->data_imp_relocs)
>       {
> 	size_t n = ASIZE (u->data_impure_vec);
> 	IGC_FIX12_NOBJS (ss, u->data_imp_relocs, n);
>       }
>     if (u->data_relocs)
>       {
> 	size_t n = ASIZE (u->data_vec);
> 	IGC_FIX12_NOBJS (ss, u->data_relocs, n);
>       }
>   }
>   MPS_SCAN_END (ss);
>   return MPS_RES_OK;
> }
>
> Maybe there's something wrong with that (the ASIZEs maybe?)

I think the size should be fine, it would be very interesting to know
which one is the symbol that was actually killed by the GC.  This would
give us strong indications.  Maybe we can use the watchpoint strategy to
identify it?

  Andrea