[Mono-bugs] [Bug 41954][Nor] Changed - mcs uses ldind.ref instead of ldind.i

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
Sun, 27 Apr 2003 07:20:50 -0400 (EDT)

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.


--- shadow/41954	Sat Apr 26 00:05:05 2003
+++ shadow/41954.tmp.5238	Sun Apr 27 07:20:50 2003
@@ -1,23 +1,23 @@
 Bug#: 41954
-Product: Mono/Runtime
+Product: Mono/MCS
 Version: unspecified
+OS: unknown
 OS Details: 
 Status: NEW   
+Severity: Unknown
 Priority: Normal
-Component: misc
+Component: Misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: miguel@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
-Summary: Mini regression.
+Summary: mcs uses ldind.ref instead of ldind.i
 The following program fails to run on mini, it works on mono and on .NET
 1.0 and 1.1:
 // this tests making a pointer to a pointer
@@ -76,6 +76,15 @@
         IL_0009: ldstr "*c == b : {0}"
         IL_000e: ldloc.0 
         IL_000f: ldind.ref 
         IL_0010: ldloc.2 
         IL_0011: ceq 
         IL_0013: box [mscorlib]System.Boolean
+------- Additional Comments From lupus@ximian.com  2003-04-27 07:20 -------
+I changed mini to allow the compare in unsafe mode since the MS
+runtime allows it as well.
+The code produced my mcs is still wrong, though: it generates a
+ldind.ref instead of ldind.i to dereference the int* pointer.
+Since there is no reference type involved, ldind.ref should not be
+used (in a more complex program this could generate random failures
+with a moving GC).