[Mono-bugs] [Bug 40827][Nor] New - mcs fails using certain optimizations for mini
bugzilla-daemon@rocky.ximian.com
bugzilla-daemon@rocky.ximian.com
Sun, 6 Apr 2003 03:32:42 -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 mathpup@mylinuxisp.com.
http://bugzilla.ximian.com/show_bug.cgi?id=40827
--- shadow/40827 Sun Apr 6 03:32:42 2003
+++ shadow/40827.tmp.15713 Sun Apr 6 03:32:42 2003
@@ -0,0 +1,70 @@
+Bug#: 40827
+Product: Mono/Runtime
+Version: unspecified
+OS:
+OS Details:
+Status: NEW
+Resolution:
+Severity:
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs@ximian.com
+ReportedBy: mathpup@mylinuxisp.com
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL:
+Cc:
+Summary: mcs fails using certain optimizations for mini
+
+Description of Problem:
+
+I did not notice this problem when running small test programs with mini, but when
+I used ran mcs.exe under mini and tried to compile a very large program like Qt#, I
+ran into some problems with some optimization options.
+
+The basic command line was
+
+mini -O=$opt /usr/local/bin/mcs.exe -nowarn:0108 -nowarn:0114 -target:library
+-optimize+ $list
+
+where $opt was the particular optimization selected and $list was the list of source
+files.
+
+With $opt=deadce, compilation aborted with
+** ERROR **: unknown operator: local
+aborting...
+Aborted
+
+With $opt=shared, mcs did not even start the compilation, but instead printed its
+option summary. I believe that the command arguments somehow got corrupted.
+
+With $opt=all, I got a different error:
+Exception caught by the compiler while compiling:
+ Block that caused the problem begin at: QtSupport.cs: (335)
+
+Unhandled Exception: System.NullReferenceException: A null value was found where
+an object instance was required
+
+If I used all optimization options except deadce and shared, so $opt=
+peephole,branch,inline,cfold,consprop,copyprop,linears,cmov,sched,instrins,tailc,loop,fcmov
+compilation was successful.
+
+Steps to reproduce the problem:
+1. See above.
+
+
+Actual Results:
+
+
+Expected Results:
+
+
+How often does this happen?
+
+Always
+
+
+Additional Information:
+
+If you want more specific information on reproducing the problem with Qt#, let me
+know.