[Mono-dev] Update strangeness

Neale Ferguson neale at sinenomine.net
Thu Jul 30 10:46:33 UTC 2015

9ffebc9d4e13bebe456b05fad1fd85e4f3c7f0d2 (May 12) introduced this piece of
-               else
-                       start = get_delegate_invoke_impl (TRUE, 0, NULL,
+               } else
+                       MonoTrampInfo *info;
+                       start = get_delegate_invoke_impl (&info, TRUE, 0,
+                       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
< Method Tests:.cctor () (code length 202) [objects.exe]
> Method Tests:.cctor () (code length 196) [objects.exe]
< 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

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.


More information about the Mono-devel-list mailing list