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.
Created attachment 15461 [details]
I have a short program that creates a delegate.
When the program is run on Windows/MS.NET everything works.
When run on mono, the delegate creation explodes.
If the multplication within the program is slightly changed, everything works properly.
Steps to reproduce:
Run mcs mulbug.cs (attaached)
This is not valid il, the mul instruction requires two arguments with the same type.
Wow, so this is actually a Microsoft bug that they accept this?
I assume that you are referring to:
Page 302 (Table III.2: Binary Numeric Operations)
I ask this because I intend in opening a bug in CoreCLR, so I would like to verify that I'm referring to the correct part of the spec...
Its not a bug in ms, a runtime can accept more code than the spec allows, but its not required, and mono is more strict in this matter.
I'm not used to MSIL / CLR being so relaxed.
Can't this lead though to unexpected results (as in generate completely unsafe code / subvert the type system etc.)?
Not in this case, ms just inserts the conversion by itself.