On Tue, 2010-01-05 at 00:10 +0200, A.M. Abdelaziz wrote:
> I also didn't know that there are two mscorlib.dll one in mono/2.0/
> and another in /mono/4.0/
There would be 3, as the 1.0 mscorlib.dll is also different, but we
dropped 1.0 profile support for 2.8.
> and when comparing with gui-compa
Background is below, but the pertinent question for mono-devel-list is
this: should monodoc.dll follow the framework version numbering scheme
(Consts.FxVersion) or do something else? The lack of a
compiler-dependent version in monodoc is breaking use under the 2.0
profile.
On Mon, 2010-01-04 at 2
Doing loop unrolling in a profitable way is a lot harder than it looks,
specially in a JIT scenario, with constrained
execution budget.
I guess that you're underestimating the complexity of either doing
profitable unrolling or auto-vectorization. It took
the GCC people more than 3 years to get int
Because doing so is so expensive, i was thinking of only two optimizations.
One is loop unrolling when moving over arrays.
The next one is tailored to known programing patterns in C#, vectorizing
only the homogeneous structs of size 16.
The idea is that these optimizations may be cheep enough to
On Sun, Jan 3, 2010 at 10:40 PM, Jerry Maine - KF5ADY wrote:
> I have been thinking of implementing some autovectorization capabilities
> to mono, and I was wondering the opinion of the community here.
>
> I was thinking of three different ways of implementing it:
>
> IL -> IL transformation usin
