Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Casts from unsigned integer to double result in incorrect values.
Steps to reproduce: Start Mono shell (csharp).
pi@raspberrypi ~ $ csharp
Mono C# Shell, type "help;" for help
Enter statements below.
csharp> uint u = 10;
csharp> double d = u;
csharp> double d = (double)u;
(the same occurs in actual (compiled) csharp programs.)
Actual results: unsigned integer 10 is castet to a negative double value
Expected results: unsigned interger 10 should be castet to double value 10.0
Hardware platform: ARM (RaspberryPi)
Mono Version: 22.214.171.124 (Debian 126.96.36.199-5) in Raspbian (Wheezy)
Linux kernel: Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012 armv6l GNU/Linux
Does not occur on other hardware platforms (x86, x86-64) with same Mono version
I can't reproduce this using mono master, whats the output of mono --version ?
pi@raspberrypi ~ $ mono --version
Mono JIT compiler version 188.8.131.52 (Debian 184.108.40.206-5)
Copyright (C) 2002-2011 Novell, Inc, Xamarin, Inc and Contributors. www.mono-project.com
LLVM: supported, not enabled.
GC: Included Boehm (with typed GC and Parallel Mark)
Probably a dup of
Yes, it seems so. The problem does not occur on Debian Wheezy with softfp.
*** This bug has been marked as a duplicate of bug 7938 ***