From: Thierry L. <thi...@in...> - 2010-03-23 10:19:21
|
Hi all, I've just commited the patch (with 2.0 as default) to https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/trunk Erven and I have switched to this binutils version to take advantage of the recent fixes (thanks Aco! ;-) ). I should not commit this patch to gcc/binutils unless someone explicitely asks for. Regards, Thierry Lafage. Thierry Lafage a écrit : > Hi, > > Andrea, ok to set the default to 2.0. > > If there's no complain about that, I'll ci it in a few days. > > Thierry Lafage. > > > > Andrea Carlo Ornstein a écrit : > >> Hi, >> >> It was set to profile 1.0 because we had a virtual machine (PVM) that >> did not support generics. >> Erven knows about it. >> >> I would change the default to 2.0 >> and add an option to force it to the old profile when needed (to support PVM) >> I think also the VM from Politecnico di Milano supports only profile >> 1.0 (we need the option) >> >> Andrea >> >> On Wed, Mar 17, 2010 at 6:34 PM, Thierry Lafage <thi...@in...> wrote: >> >> >>> Hi all, >>> >>> Here at IRISA, we are currently using the head of the svn trunk version of >>> Mono. In this version, .Net profile 1.0 support has been removed. >>> If we use the binutils with this version of Mono, then it warns that it >>> cannot find the correct "runtime version". >>> >>> In CFile.cs, if we replace: >>> Assembly = AssemblyFactory.DefineAssembly (name, name, >>> >>> TargetRuntime.NET_1_0, >>> kind); >>> by >>> Assembly = AssemblyFactory.DefineAssembly (name, name, >>> >>> TargetRuntime.NET_2_0, >>> kind); >>> then it works fine. >>> >>> I don't know the consequences on other's code of such a change. To minimize >>> it, I propose to add a flag to the binutils command lines like eg. >>> -profile=2 and to let 1.0 be the default case. >>> >>> What do you think? >>> >>> Regards, >>> >>> Thierry Lafage. >>> >>> ------------------------------------------------------------------------------ >>> Download Intel® Parallel Studio Eval >>> Try the new software tools for yourself. Speed compiling, find bugs >>> proactively, and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >>> _______________________________________________ >>> Gcc4cli-devel mailing list >>> Gcc...@li... >>> https://lists.sourceforge.net/lists/listinfo/gcc4cli-devel >>> >>> >>> >>> > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Gcc4cli-devel mailing list > Gcc...@li... > https://lists.sourceforge.net/lists/listinfo/gcc4cli-devel > |