[Mono-bugs] [Bug 54303][Nor] Changed - FIX: generated inverted floating point comparisons are not correct

[bugzilla-daemon@bugzilla.ximian.com]

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 bmaurer@users.sf.net.

http://bugzilla.ximian.com/show_bug.cgi?id=54303

--- shadow/54303	2004-02-27 07:22:55.000000000 -0500
+++ shadow/54303.tmp.6493	2004-02-27 08:00:00.000000000 -0500
@@ -1,16 +1,16 @@
 Bug#: 54303
-Product: Mono/Compilers
+Product: Mono/Runtime
 Version: unspecified
 OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
 Severity: Unknown
 Priority: Normal
-Component: C#
+Component: misc
 AssignedTo: bmaurer@users.sf.net                            
 ReportedBy: vargaz@freemail.hu               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
@@ -73,6 +73,18 @@
 
 ------- Additional Comments From vargaz@freemail.hu  2004-02-27 07:22 -------
 The comparisons must be tested using Nan or infinity, since this is
 where bne and bne.un differs. I think there is a bug in the runtime too
 since the test runs fine with the code generated by mcs, but if you
 run the mcs generated code on the MS runtime, you get different results.
+
+------- Additional Comments From bmaurer@users.sf.net  2004-02-27 07:59 -------
+Ok, so I am moving this over to runtime. Once we have a fix there, we 
+can put a test in the mcs test folder (as well as the mono regression 
+set), and get this thing closed.
+
+Thanks for reminding of this, Miguel, it had almost fallen off my 
+radar.
+
+Also, a little item for thought: this has the potential to break 
+applications that have been compiled without the fix. Not sure if 
+there is anything we can do here, sadly.