From: Thierry L. <thi...@in...> - 2010-03-17 17:34:41
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> Hi all,<br> <br> 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.<br> If we use the binutils with this version of Mono, then it warns that it cannot find the correct "runtime version".<br> <br> In CFile.cs, if we replace:<br> <font color="#660000"><tt> Assembly = AssemblyFactory.DefineAssembly (name, name,<br> <b>TargetRuntime.NET_1_0</b>,<br> kind);<br> </tt></font>by<br> <font color="#660000"><tt> Assembly = AssemblyFactory.DefineAssembly (name, name,<br> <b>TargetRuntime.NET_2_0</b>,<br> kind);<br> </tt></font>then it works fine.<br> <br> 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.<br> <br> What do you think?<br> <br> Regards,<br> <pre class="moz-signature" cols="72">Thierry Lafage. </pre> </body> </html> |
From: Thierry L. <thi...@in...> - 2010-03-22 11:05:12
Attachments:
binutils-ld.patch
|
Hi all, Here is a patch for binutils/ld which enables the possibility to specifiy the runtime version for ld (1.0 (default), 1.1 or 2.0). This is useful if you want to use eg. a trunk/head mono version (which does not contain 1.0 anymore) and still run the gcc tests (which fails when runtime warnings occur). Note that, by default, the behavior is not changed. If no one has comment on it, I should commit it soon. Regards, Thierry Lafage. Thierry Lafage a écrit : > 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 > |
From: Andrea C. O. <and...@gm...> - 2010-03-22 15:24:53
|
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 > > |
From: Thierry L. <thi...@in...> - 2010-03-22 16:08:23
|
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 >> >> >> |
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 > |