Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by lupus@ximian.com.http://bugzilla.ximian.com/show_bug.cgi?id=58279
--- shadow/58279 2004-05-13 07:15:32.000000000 -0400
+++ shadow/58279.tmp.23546 2004-05-13 11:01:09.000000000 -0400
@@ -387,6 +387,19 @@
Building Mono packages should come from the `mono' tarball.
------- Additional Comments From uli@suse.de 2004-05-13 07:15 -------
The fact that the runtime SIGILLs on every CPU except the G4 is
quite obviously a bug _in the runtime_.
+
+------- Additional Comments From lupus@ximian.com 2004-05-13 11:01 -------
+Ulrich, we agree there is a bug in the runtime, though it's not really
+specific to the non-G4: I regularly test on a double G5, though
+running under macosx. It would be useful if you can run mcs in the
+runtime and report the instruction address where the SIGILL happens:
+disassemble that point and a few dozen instructions before and after
+(run with mono -v so we can see which method the IP belongs to).
+The cache hint may be helpful, too: could you try changing
+MIN_CACHE_LINE in mono/mono/mini-ppc.c to 4 (from 8), recompile and
+retry? You may also want to try mono from cvs: there were a number of
+updates since the release.
+Thanks.