[Mono-dev] Update strangeness
Alexander Köplinger
alex.koeplinger at outlook.com
Thu Jul 30 11:06:49 UTC 2015
Please note that even though that commit was authored on May 12, it only went into master with https://github.com/mono/mono/pull/1929 about 9 hours ago.
-- Alex
> From: neale at sinenomine.net
> To: mono-devel-list at lists.ximian.com
> Date: Thu, 30 Jul 2015 10:46:33 +0000
> Subject: [Mono-dev] Update strangeness
>
> 9ffebc9d4e13bebe456b05fad1fd85e4f3c7f0d2 (May 12) introduced this piece of
> code:
> - else
> - start = get_delegate_invoke_impl (TRUE, 0, NULL,
> FALSE);
> + } else
> + MonoTrampInfo *info;
> + start = get_delegate_invoke_impl (&info, TRUE, 0,
> FALSE);
> + mono_tramp_info_register (info);
> + }
>
> I have no idea how it's been being built cleanly ever since. I am adding
> the '{' and will commit shortly, but I am puzzled.
>
> I'm also seeing these failures during make check for the first time:
>
> Checking unintended native code changes in objects.exe without AOT
> 23c23
> < Method Tests:.cctor () (code length 202) [objects.exe]
> ---
> > Method Tests:.cctor () (code length 196) [objects.exe]
> 40c40
> < Method Tests:int_to_r4_inner (int) (code length 142) [objects.exe]
> —
>
>
> Other than that the other tests are passing except for
> delegate-async-exit.exe which is segving in
> major_copy_or_mark_object_no_evacuation during System.Environment.Exit
> processing.
>
> The reason I am raising these issues to the list is that I note there has
> been a bit of reverting/reapplying that seem to have affected architecture
> dependent code.
>
> Neale
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20150730/b0c8551e/attachment.html>
More information about the Mono-devel-list
mailing list