Menu
▾
▴
gcc4cli-devel — Discussions on development issues of the project
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(17) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(6) |
Feb
(4) |
Mar
(46) |
Apr
(2) |
May
|
Jun
(4) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(21) |
Mar
(2) |
Apr
|
May
(19) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Thierry L. <thi...@in...> - 2010-04-12 09:21:48
|
Commited. Thierry Lafage. |
|
From: Erven R. <erv...@in...> - 2010-04-01 09:47:26
|
FYI: I checked-in a few changes in the front-end. It could not process binaries generated with the Mono binutils. The .init and .fini functions from libstd map to empty functions. Not sure it is ideal, but at least we can run some applications. Ciao, -- Erven. |
|
From: Thierry L. <thi...@in...> - 2010-03-29 14:45:02
|
Hi, Here is a patch that adds source location information (.line) for function definitions in CIL code when -g is activated. This information is needed for ilasm (with the patch I sent to mono-devel-list) to build up debug info correctly. Otherwise, ilasm debug info is wrong. As usual, feel free to comment, and, if there is nothing to change and since it's a minor patch, I should commit in a few days. Regards, Thierry Lafage. |
|
From: Andrea C. O. <and...@gm...> - 2010-03-24 13:25:31
|
ok. On Tue, Mar 23, 2010 at 2:24 PM, Thierry Lafage <thi...@in...> wrote: > Yes, sorry. > Here is the complete patch with CSObject.cs cleanup. > > Sorry for the "noise", > > Thierry Lafage. > > > > Andrea Carlo Ornstein a écrit : >> >> No, I wasn't clear :) >> Something like this: >> >> -o) >> - PARAM="$PARAM $1$2"; >> + PARAM="$PARAM -output $2"; >> shift >> shift >> ;; >> and remove the sed at the end >> >> the script keeps the same input options >> but there is no need of the sed at the end, we just rewrite the option >> when we recognize it >> >> On Tue, Mar 23, 2010 at 2:06 PM, Thierry Lafage <thi...@in...> >> wrote: >> >>> >>> Andrea Carlo Ornstein a écrit : >>> >>>> >>>> Hi, >>>> >>>> I would just use -output in the switch and remove the sed at the end >>>> (keeping the extra arguments '-dll -quiet') >>>> The hack of no space after -o was there just to simplify the sed at >>>> the end of the script, now it is not needed. >>>> >>>> >>> >>> Ok, but I'll have to modify gcc (cil32.h) to make it pass -output to 'as' >>> instead of -o. Do you really want me to introduce such a version >>> dependency? >>> (personnally, I don't mind). >>> >>> >>>> >>>> If you remove that part, you should cleanup also >>>> >>>> >>>> http://clibinutils.svn.sourceforge.net/viewvc/clibinutils/mono-based-binutils/trunk/tools/gcc4cli/utils/CObject.cs?revision=12&view=markup >>>> There is a hack to fixup an error on varargs methods generated by pnet >>>> ilasm. >>>> just remove fix_DOTGNU_Errors() >>>> >>>> >>> >>> Ok, I'll check that. >>> >>> Regards, >>> Thierry. >>> >>>> >>>> Andrea >>>> >>>> On Tue, Mar 23, 2010 at 11:34 AM, Thierry Lafage >>>> <thi...@in...> wrote: >>>> >>>> >>>>> >>>>> Hi Andrea, >>>>> >>>>> Here is a simpler patch for as that is meant to be commited in >>>>> >>>>> >>>>> https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/trunk >>>>> >>>>> Since the svn url says that it is a mono-based version, the test for >>>>> Pnet >>>>> ilasm is surely not worth anymore. >>>>> I also added a space between -o and the ouput file in order not to >>>>> confuse >>>>> with potential -opt or -o<something> ilasm arguments. Otherwise, >>>>> calling >>>>> as >>>>> with -opt gives: "ilasm /ouput:pt" >>>>> >>>>> Comparing to my former patch, I don't propose anymore the -O case >>>>> because, >>>>> since the short bytecode optimizations are done in ld, there is no more >>>>> need >>>>> for the moment to activate optimizations in the assembly pass. >>>>> >>>>> Tell me if it's ok for you, then I'll commit. >>>>> >>>>> Regards, >>>>> >>>>> Thierry Lafage. >>>>> >>>>> >>>>> >>>>> Andrea Carlo Ornstein a écrit : >>>>> >>>>> >>>>>> >>>>>> At the beginning when I did the binutils there was a bug in the >>>>>> release of ilasm. >>>>>> Only the one from Mono trunk was working. >>>>>> That is the only reason why the binutils could use also the Pnet ilasm >>>>>> (You could avoid the build of ilasm from Mono trunk). >>>>>> >>>>>> If it is not the case anymore we can switch all to Mono tools and >>>>>> remove the check in the script. >>>>>> >>>>>> Andrea >>>>>> >>>>>> On Mon, Mar 22, 2010 at 12:11 PM, Thierry Lafage >>>>>> <thi...@in...> wrote: >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> I forgot to mention that (Mono) ilasm does not complains (not even a >>>>>>> warning) if you pass it an unknown option; so this should be ok with >>>>>>> older version of ilasm. >>>>>>> Regarding "Pnet ilasm", I don't know, but I've been told that this >>>>>>> option would be abandonned. If this is really the case, then we >>>>>>> should >>>>>>> also remove the "if [ `$ILASM --version | ..." test. Tell me: I can >>>>>>> do >>>>>>> it in this commit. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Thierry Lafage. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thierry Lafage a écrit : >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Here is a patch for our binutils/as script which converts -O option >>>>>>>> into forthcoming '-opt:ldc' ilasm option. >>>>>>>> >>>>>>>> Since the default behavior is not changed, I should commit soon if >>>>>>>> nobody complains. >>>>>>>> >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> Index: scripts/as.in >>>>> =================================================================== >>>>> --- scripts/as.in (revision 14) >>>>> +++ scripts/as.in (working copy) >>>>> @@ -23,7 +23,7 @@ >>>>> shift >>>>> ;; >>>>> -o) >>>>> - PARAM="$PARAM $1$2"; >>>>> + PARAM="$PARAM $1 $2"; >>>>> shift >>>>> shift >>>>> ;; >>>>> @@ -34,13 +34,7 @@ >>>>> esac >>>>> done >>>>> >>>>> -if test "x`$ILASM --version | grep Mono | wc -l`" = "x0"; then >>>>> - #needed by Pnet ilasm >>>>> - PARAM=`echo "--format dll $PARAM" | sed 's? -o? -o ?'`; >>>>> -else >>>>> - #needed by Mono ilasm >>>>> - PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o? -output:?'`; >>>>> -fi >>>>> +PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o ? -output:?'`; >>>>> >>>>> CMD="$ILASM $PARAM" >>>>> if test -n "$VERBOSE"; then >>>>> >>>>> >>>>> >>>>> > > Index: tools/gcc4cli/utils/CObject.cs > =================================================================== > --- tools/gcc4cli/utils/CObject.cs (revision 14) > +++ tools/gcc4cli/utils/CObject.cs (working copy) > @@ -15,8 +15,6 @@ > { > MainType = Module.Types["<Module>"]; > FillTables (); > - if (ref_types.Contains ("<ModuleExtern>")) > - fix_DOTGNU_Errors (); > } > > internal CObject (string name, AssemblyResolver asm_resolver) > @@ -30,30 +28,6 @@ > Module.Types.Add (MainType); > } > > - void fix_DOTGNU_Errors () > - { > - foreach (MethodDefinition method in MainType.Methods) { > - foreach (Instruction instr in method.Body.Instructions) { > - if ( instr.OpCode.OperandType == > OperandType.InlineMethod > - || (instr.OpCode.OperandType == > OperandType.InlineTok && instr.Operand is MethodReference)) { > - MethodReference mref = instr.Operand as > MethodReference; > - if (mref.DeclaringType.Name == "<ModuleExtern>") { > - string m_name = mref.Name; > - if (def_symbols.Contains (m_name)) { > - mref.DeclaringType = > ((MethodReference)def_symbols[m_name]).DeclaringType; > - } > - else if (private_symbols.Contains (m_name)) { > - mref.DeclaringType = > ((MethodReference)private_symbols[m_name]).DeclaringType; > - } > - else > - throw new Exception ("Error in hack for > DOTGNU"); > - } > - } > - } > - } > - ref_types.Remove ("<ModuleExtern>"); > - } > - > static int renamer_id = 0; > > bool MethodIsVarArg(MethodReference method) > Index: scripts/as.in > =================================================================== > --- scripts/as.in (revision 14) > +++ scripts/as.in (working copy) > @@ -23,7 +23,7 @@ > shift > ;; > -o) > - PARAM="$PARAM $1$2"; > + PARAM="$PARAM -output:$2"; > shift > shift > ;; > @@ -34,13 +34,7 @@ > esac > done > > -if test "x`$ILASM --version | grep Mono | wc -l`" = "x0"; then > - #needed by Pnet ilasm > - PARAM=`echo "--format dll $PARAM" | sed 's? -o? -o ?'`; > -else > - #needed by Mono ilasm > - PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o? -output:?'`; > -fi > +PARAM="-dll -quiet $PARAM" > > CMD="$ILASM $PARAM" > if test -n "$VERBOSE"; then > > |
|
From: Andrea C. O. <and...@gm...> - 2010-03-24 13:25:06
|
The creation of the sourceforge projects with mailinglists. Andrea On Tue, Mar 23, 2010 at 3:31 PM, Erven Rohou <erv...@in...> wrote: > I think it is not too bad: July 2009. > > Since then, we could add: > > > 2010-03 > Move binutils to a new repository. > Cleanup of binutils: improved code size thanks to the use of the > short forms of ldc/ldloc/stloc/ldarg and branch opcodes. > Several bug fixes. > 2010-01 > Emission source location when -g is active. > > > > Anything else? > > -- > Erven. > > Andrea Carlo Ornstein a écrit : >> >> http://gcc.gnu.org/projects/cli.html >> It is probably a little out of date :) >> >> On Tue, Mar 23, 2010 at 2:50 PM, Erven Rohou <erv...@in...> wrote: >>> >>> Andrea Carlo Ornstein a écrit : >>>> >>>> I already changed the wiki on sourceforge >>>> https://sourceforge.net/apps/mediawiki/gcc4cli/index.php?title=Main_Page >>>> I cannot change the README and the html pages on gcc from here. >>> >>> I just updated the README. >>> What HTML page are you talking about? >>> >>>> I am ok with the changes and also having the mono based one as >>>> preferred. >>>> >>>> After a short period of transition I would like to empty the dirs >>>> svn://gcc.gnu.org/svn/gcc/branches/st/binutils and >>>> svn://gcc.gnu.org/svn/gcc/branches/st/mono-based-binutils and keep >>>> there (in both) just a README file saying that the code has been moved >>>> to the sourceforge project with the proper links >>> >>> Fine with me. >>> >>>> Erven, you know better than me who are the users at this point, >>>> I let you decide how long is this 'short period' :) >>> >>> I think we mostly have IBM Haifa, INRIA, and Politecnico di Milano (ie >>> Harvard). >>> I am going to tell them. >>> >>> -- >>> Erven. >>> >>>> I will create a couple of mailing list also for cli binutils (one for >>>> the ci and one for the development discussions) >>>> >>>> Andrea >>>> >>>> On Tue, Mar 23, 2010 at 8:40 AM, Erven Rohou <erv...@in...> >>>> wrote: >>>>> >>>>> Ciao Andrea, >>>>> >>>>> Many thanks for the various fixes. >>>>> Probably, we should update the README in gcc.../branches/st/README to >>>>> reflect >>>>> the new binutils location. >>>>> >>>>> I am also tempted to change the order of the sections: first the build >>>>> instructions for the Mono toolchain, then DotGnu. Maybe we can also say >>>>> the Mono >>>>> is the preferred way? >>>>> >>>>> -- >>>>> Erven. >> > > |
|
From: Erven R. <erv...@in...> - 2010-03-23 14:31:16
|
I think it is not too bad: July 2009. Since then, we could add: 2010-03 Move binutils to a new repository. Cleanup of binutils: improved code size thanks to the use of the short forms of ldc/ldloc/stloc/ldarg and branch opcodes. Several bug fixes. 2010-01 Emission source location when -g is active. Anything else? -- Erven. Andrea Carlo Ornstein a écrit : > http://gcc.gnu.org/projects/cli.html > It is probably a little out of date :) > > On Tue, Mar 23, 2010 at 2:50 PM, Erven Rohou <erv...@in...> wrote: >> Andrea Carlo Ornstein a écrit : >>> I already changed the wiki on sourceforge >>> https://sourceforge.net/apps/mediawiki/gcc4cli/index.php?title=Main_Page >>> I cannot change the README and the html pages on gcc from here. >> I just updated the README. >> What HTML page are you talking about? >> >>> I am ok with the changes and also having the mono based one as preferred. >>> >>> After a short period of transition I would like to empty the dirs >>> svn://gcc.gnu.org/svn/gcc/branches/st/binutils and >>> svn://gcc.gnu.org/svn/gcc/branches/st/mono-based-binutils and keep >>> there (in both) just a README file saying that the code has been moved >>> to the sourceforge project with the proper links >> Fine with me. >> >>> Erven, you know better than me who are the users at this point, >>> I let you decide how long is this 'short period' :) >> I think we mostly have IBM Haifa, INRIA, and Politecnico di Milano (ie >> Harvard). >> I am going to tell them. >> >> -- >> Erven. >> >>> I will create a couple of mailing list also for cli binutils (one for >>> the ci and one for the development discussions) >>> >>> Andrea >>> >>> On Tue, Mar 23, 2010 at 8:40 AM, Erven Rohou <erv...@in...> wrote: >>>> Ciao Andrea, >>>> >>>> Many thanks for the various fixes. >>>> Probably, we should update the README in gcc.../branches/st/README to >>>> reflect >>>> the new binutils location. >>>> >>>> I am also tempted to change the order of the sections: first the build >>>> instructions for the Mono toolchain, then DotGnu. Maybe we can also say >>>> the Mono >>>> is the preferred way? >>>> >>>> -- >>>> Erven. > |
|
From: Andrea C. O. <and...@gm...> - 2010-03-23 14:08:46
|
http://gcc.gnu.org/projects/cli.html It is probably a little out of date :) On Tue, Mar 23, 2010 at 2:50 PM, Erven Rohou <erv...@in...> wrote: > Andrea Carlo Ornstein a écrit : >> >> I already changed the wiki on sourceforge >> https://sourceforge.net/apps/mediawiki/gcc4cli/index.php?title=Main_Page >> I cannot change the README and the html pages on gcc from here. > > I just updated the README. > What HTML page are you talking about? > >> I am ok with the changes and also having the mono based one as preferred. >> >> After a short period of transition I would like to empty the dirs >> svn://gcc.gnu.org/svn/gcc/branches/st/binutils and >> svn://gcc.gnu.org/svn/gcc/branches/st/mono-based-binutils and keep >> there (in both) just a README file saying that the code has been moved >> to the sourceforge project with the proper links > > Fine with me. > >> >> Erven, you know better than me who are the users at this point, >> I let you decide how long is this 'short period' :) > > I think we mostly have IBM Haifa, INRIA, and Politecnico di Milano (ie > Harvard). > I am going to tell them. > > -- > Erven. > >> >> I will create a couple of mailing list also for cli binutils (one for >> the ci and one for the development discussions) >> >> Andrea >> >> On Tue, Mar 23, 2010 at 8:40 AM, Erven Rohou <erv...@in...> wrote: >>> >>> Ciao Andrea, >>> >>> Many thanks for the various fixes. >>> Probably, we should update the README in gcc.../branches/st/README to >>> reflect >>> the new binutils location. >>> >>> I am also tempted to change the order of the sections: first the build >>> instructions for the Mono toolchain, then DotGnu. Maybe we can also say >>> the Mono >>> is the preferred way? >>> >>> -- >>> Erven. > |
|
From: Erven R. <erv...@in...> - 2010-03-23 13:51:03
|
Andrea Carlo Ornstein a écrit : > I already changed the wiki on sourceforge > https://sourceforge.net/apps/mediawiki/gcc4cli/index.php?title=Main_Page > I cannot change the README and the html pages on gcc from here. I just updated the README. What HTML page are you talking about? > I am ok with the changes and also having the mono based one as preferred. > > After a short period of transition I would like to empty the dirs > svn://gcc.gnu.org/svn/gcc/branches/st/binutils and > svn://gcc.gnu.org/svn/gcc/branches/st/mono-based-binutils and keep > there (in both) just a README file saying that the code has been moved > to the sourceforge project with the proper links Fine with me. > > Erven, you know better than me who are the users at this point, > I let you decide how long is this 'short period' :) I think we mostly have IBM Haifa, INRIA, and Politecnico di Milano (ie Harvard). I am going to tell them. -- Erven. > > I will create a couple of mailing list also for cli binutils (one for > the ci and one for the development discussions) > > Andrea > > On Tue, Mar 23, 2010 at 8:40 AM, Erven Rohou <erv...@in...> wrote: >> Ciao Andrea, >> >> Many thanks for the various fixes. >> Probably, we should update the README in gcc.../branches/st/README to reflect >> the new binutils location. >> >> I am also tempted to change the order of the sections: first the build >> instructions for the Mono toolchain, then DotGnu. Maybe we can also say the Mono >> is the preferred way? >> >> -- >> Erven. |
|
From: Thierry L. <thi...@in...> - 2010-03-23 13:24:17
|
Yes, sorry. Here is the complete patch with CSObject.cs cleanup. Sorry for the "noise", Thierry Lafage. Andrea Carlo Ornstein a écrit : > No, I wasn't clear :) > Something like this: > > -o) > - PARAM="$PARAM $1$2"; > + PARAM="$PARAM -output $2"; > shift > shift > ;; > and remove the sed at the end > > the script keeps the same input options > but there is no need of the sed at the end, we just rewrite the option > when we recognize it > > On Tue, Mar 23, 2010 at 2:06 PM, Thierry Lafage <thi...@in...> wrote: > >> Andrea Carlo Ornstein a écrit : >> >>> Hi, >>> >>> I would just use -output in the switch and remove the sed at the end >>> (keeping the extra arguments '-dll -quiet') >>> The hack of no space after -o was there just to simplify the sed at >>> the end of the script, now it is not needed. >>> >>> >> Ok, but I'll have to modify gcc (cil32.h) to make it pass -output to 'as' >> instead of -o. Do you really want me to introduce such a version dependency? >> (personnally, I don't mind). >> >> >>> If you remove that part, you should cleanup also >>> >>> http://clibinutils.svn.sourceforge.net/viewvc/clibinutils/mono-based-binutils/trunk/tools/gcc4cli/utils/CObject.cs?revision=12&view=markup >>> There is a hack to fixup an error on varargs methods generated by pnet >>> ilasm. >>> just remove fix_DOTGNU_Errors() >>> >>> >> Ok, I'll check that. >> >> Regards, >> Thierry. >> >>> Andrea >>> >>> On Tue, Mar 23, 2010 at 11:34 AM, Thierry Lafage >>> <thi...@in...> wrote: >>> >>> >>>> Hi Andrea, >>>> >>>> Here is a simpler patch for as that is meant to be commited in >>>> >>>> https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/trunk >>>> >>>> Since the svn url says that it is a mono-based version, the test for Pnet >>>> ilasm is surely not worth anymore. >>>> I also added a space between -o and the ouput file in order not to >>>> confuse >>>> with potential -opt or -o<something> ilasm arguments. Otherwise, calling >>>> as >>>> with -opt gives: "ilasm /ouput:pt" >>>> >>>> Comparing to my former patch, I don't propose anymore the -O case >>>> because, >>>> since the short bytecode optimizations are done in ld, there is no more >>>> need >>>> for the moment to activate optimizations in the assembly pass. >>>> >>>> Tell me if it's ok for you, then I'll commit. >>>> >>>> Regards, >>>> >>>> Thierry Lafage. >>>> >>>> >>>> >>>> Andrea Carlo Ornstein a écrit : >>>> >>>> >>>>> At the beginning when I did the binutils there was a bug in the >>>>> release of ilasm. >>>>> Only the one from Mono trunk was working. >>>>> That is the only reason why the binutils could use also the Pnet ilasm >>>>> (You could avoid the build of ilasm from Mono trunk). >>>>> >>>>> If it is not the case anymore we can switch all to Mono tools and >>>>> remove the check in the script. >>>>> >>>>> Andrea >>>>> >>>>> On Mon, Mar 22, 2010 at 12:11 PM, Thierry Lafage >>>>> <thi...@in...> wrote: >>>>> >>>>> >>>>> >>>>>> I forgot to mention that (Mono) ilasm does not complains (not even a >>>>>> warning) if you pass it an unknown option; so this should be ok with >>>>>> older version of ilasm. >>>>>> Regarding "Pnet ilasm", I don't know, but I've been told that this >>>>>> option would be abandonned. If this is really the case, then we should >>>>>> also remove the "if [ `$ILASM --version | ..." test. Tell me: I can do >>>>>> it in this commit. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Thierry Lafage. >>>>>> >>>>>> >>>>>> >>>>>> Thierry Lafage a écrit : >>>>>> >>>>>> >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Here is a patch for our binutils/as script which converts -O option >>>>>>> into forthcoming '-opt:ldc' ilasm option. >>>>>>> >>>>>>> Since the default behavior is not changed, I should commit soon if >>>>>>> nobody complains. >>>>>>> >>>>>>> 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 >>>>>> >>>>>> >>>>>> >>>>>> >>>> Index: scripts/as.in >>>> =================================================================== >>>> --- scripts/as.in (revision 14) >>>> +++ scripts/as.in (working copy) >>>> @@ -23,7 +23,7 @@ >>>> shift >>>> ;; >>>> -o) >>>> - PARAM="$PARAM $1$2"; >>>> + PARAM="$PARAM $1 $2"; >>>> shift >>>> shift >>>> ;; >>>> @@ -34,13 +34,7 @@ >>>> esac >>>> done >>>> >>>> -if test "x`$ILASM --version | grep Mono | wc -l`" = "x0"; then >>>> - #needed by Pnet ilasm >>>> - PARAM=`echo "--format dll $PARAM" | sed 's? -o? -o ?'`; >>>> -else >>>> - #needed by Mono ilasm >>>> - PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o? -output:?'`; >>>> -fi >>>> +PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o ? -output:?'`; >>>> >>>> CMD="$ILASM $PARAM" >>>> if test -n "$VERBOSE"; then >>>> >>>> >>>> >>>> |
|
From: Andrea C. O. <and...@gm...> - 2010-03-23 13:22:51
|
Ok for me. On Tue, Mar 23, 2010 at 2:21 PM, Thierry Lafage <thi...@in...> wrote: > Sorry, I misunderstood your point with -output. > Here is the (final?) patch. > I wait for your approval to commit. > > Regards, > > Thierry Lafage. > > > > Thierry Lafage a écrit : >> >> Andrea Carlo Ornstein a écrit : >> >>> >>> Hi, >>> >>> I would just use -output in the switch and remove the sed at the end >>> (keeping the extra arguments '-dll -quiet') >>> The hack of no space after -o was there just to simplify the sed at >>> the end of the script, now it is not needed. >>> >> >> Ok, but I'll have to modify gcc (cil32.h) to make it pass -output to 'as' >> instead of -o. Do you really want me to introduce such a version dependency? >> (personnally, I don't mind). >> >> >>> >>> If you remove that part, you should cleanup also >>> >>> http://clibinutils.svn.sourceforge.net/viewvc/clibinutils/mono-based-binutils/trunk/tools/gcc4cli/utils/CObject.cs?revision=12&view=markup >>> There is a hack to fixup an error on varargs methods generated by pnet >>> ilasm. >>> just remove fix_DOTGNU_Errors() >>> >> >> Ok, I'll check that. >> >> Regards, >> Thierry. >> >>> >>> Andrea >>> >>> On Tue, Mar 23, 2010 at 11:34 AM, Thierry Lafage >>> <thi...@in...> wrote: >>> >>>> >>>> Hi Andrea, >>>> >>>> Here is a simpler patch for as that is meant to be commited in >>>> >>>> https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/trunk >>>> >>>> Since the svn url says that it is a mono-based version, the test for >>>> Pnet >>>> ilasm is surely not worth anymore. >>>> I also added a space between -o and the ouput file in order not to >>>> confuse >>>> with potential -opt or -o<something> ilasm arguments. Otherwise, calling >>>> as >>>> with -opt gives: "ilasm /ouput:pt" >>>> >>>> Comparing to my former patch, I don't propose anymore the -O case >>>> because, >>>> since the short bytecode optimizations are done in ld, there is no more >>>> need >>>> for the moment to activate optimizations in the assembly pass. >>>> >>>> Tell me if it's ok for you, then I'll commit. >>>> >>>> Regards, >>>> >>>> Thierry Lafage. >>>> >>>> >>>> >>>> Andrea Carlo Ornstein a écrit : >>>> >>>>> >>>>> At the beginning when I did the binutils there was a bug in the >>>>> release of ilasm. >>>>> Only the one from Mono trunk was working. >>>>> That is the only reason why the binutils could use also the Pnet ilasm >>>>> (You could avoid the build of ilasm from Mono trunk). >>>>> >>>>> If it is not the case anymore we can switch all to Mono tools and >>>>> remove the check in the script. >>>>> >>>>> Andrea >>>>> >>>>> On Mon, Mar 22, 2010 at 12:11 PM, Thierry Lafage >>>>> <thi...@in...> wrote: >>>>> >>>>> >>>>>> >>>>>> I forgot to mention that (Mono) ilasm does not complains (not even a >>>>>> warning) if you pass it an unknown option; so this should be ok with >>>>>> older version of ilasm. >>>>>> Regarding "Pnet ilasm", I don't know, but I've been told that this >>>>>> option would be abandonned. If this is really the case, then we should >>>>>> also remove the "if [ `$ILASM --version | ..." test. Tell me: I can do >>>>>> it in this commit. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Thierry Lafage. >>>>>> >>>>>> >>>>>> >>>>>> Thierry Lafage a écrit : >>>>>> >>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Here is a patch for our binutils/as script which converts -O option >>>>>>> into forthcoming '-opt:ldc' ilasm option. >>>>>>> >>>>>>> Since the default behavior is not changed, I should commit soon if >>>>>>> nobody complains. >>>>>>> >>>>>>> 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 >>>>>> >>>>>> >>>>>> >>>> >>>> Index: scripts/as.in >>>> =================================================================== >>>> --- scripts/as.in (revision 14) >>>> +++ scripts/as.in (working copy) >>>> @@ -23,7 +23,7 @@ >>>> shift >>>> ;; >>>> -o) >>>> - PARAM="$PARAM $1$2"; >>>> + PARAM="$PARAM $1 $2"; >>>> shift >>>> shift >>>> ;; >>>> @@ -34,13 +34,7 @@ >>>> esac >>>> done >>>> >>>> -if test "x`$ILASM --version | grep Mono | wc -l`" = "x0"; then >>>> - #needed by Pnet ilasm >>>> - PARAM=`echo "--format dll $PARAM" | sed 's? -o? -o ?'`; >>>> -else >>>> - #needed by Mono ilasm >>>> - PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o? -output:?'`; >>>> -fi >>>> +PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o ? -output:?'`; >>>> >>>> CMD="$ILASM $PARAM" >>>> if test -n "$VERBOSE"; then >>>> >>>> >>>> >> >> >> ------------------------------------------------------------------------------ >> 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 >> > > Index: scripts/as.in > =================================================================== > --- scripts/as.in (revision 14) > +++ scripts/as.in (working copy) > @@ -23,7 +23,7 @@ > shift > ;; > -o) > - PARAM="$PARAM $1$2"; > + PARAM="$PARAM -output:$2"; > shift > shift > ;; > @@ -34,13 +34,7 @@ > esac > done > > -if test "x`$ILASM --version | grep Mono | wc -l`" = "x0"; then > - #needed by Pnet ilasm > - PARAM=`echo "--format dll $PARAM" | sed 's? -o? -o ?'`; > -else > - #needed by Mono ilasm > - PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o? -output:?'`; > -fi > +PARAM="-dll -quiet $PARAM" > > CMD="$ILASM $PARAM" > if test -n "$VERBOSE"; then > > |
|
From: Andrea C. O. <and...@gm...> - 2010-03-23 13:21:43
|
No, I wasn't clear :)
Something like this:
-o)
- PARAM="$PARAM $1$2";
+ PARAM="$PARAM -output $2";
shift
shift
;;
and remove the sed at the end
the script keeps the same input options
but there is no need of the sed at the end, we just rewrite the option
when we recognize it
On Tue, Mar 23, 2010 at 2:06 PM, Thierry Lafage <thi...@in...> wrote:
> Andrea Carlo Ornstein a écrit :
>>
>> Hi,
>>
>> I would just use -output in the switch and remove the sed at the end
>> (keeping the extra arguments '-dll -quiet')
>> The hack of no space after -o was there just to simplify the sed at
>> the end of the script, now it is not needed.
>>
>
> Ok, but I'll have to modify gcc (cil32.h) to make it pass -output to 'as'
> instead of -o. Do you really want me to introduce such a version dependency?
> (personnally, I don't mind).
>
>> If you remove that part, you should cleanup also
>>
>> http://clibinutils.svn.sourceforge.net/viewvc/clibinutils/mono-based-binutils/trunk/tools/gcc4cli/utils/CObject.cs?revision=12&view=markup
>> There is a hack to fixup an error on varargs methods generated by pnet
>> ilasm.
>> just remove fix_DOTGNU_Errors()
>>
>
> Ok, I'll check that.
>
> Regards,
> Thierry.
>>
>> Andrea
>>
>> On Tue, Mar 23, 2010 at 11:34 AM, Thierry Lafage
>> <thi...@in...> wrote:
>>
>>>
>>> Hi Andrea,
>>>
>>> Here is a simpler patch for as that is meant to be commited in
>>>
>>> https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/trunk
>>>
>>> Since the svn url says that it is a mono-based version, the test for Pnet
>>> ilasm is surely not worth anymore.
>>> I also added a space between -o and the ouput file in order not to
>>> confuse
>>> with potential -opt or -o<something> ilasm arguments. Otherwise, calling
>>> as
>>> with -opt gives: "ilasm /ouput:pt"
>>>
>>> Comparing to my former patch, I don't propose anymore the -O case
>>> because,
>>> since the short bytecode optimizations are done in ld, there is no more
>>> need
>>> for the moment to activate optimizations in the assembly pass.
>>>
>>> Tell me if it's ok for you, then I'll commit.
>>>
>>> Regards,
>>>
>>> Thierry Lafage.
>>>
>>>
>>>
>>> Andrea Carlo Ornstein a écrit :
>>>
>>>>
>>>> At the beginning when I did the binutils there was a bug in the
>>>> release of ilasm.
>>>> Only the one from Mono trunk was working.
>>>> That is the only reason why the binutils could use also the Pnet ilasm
>>>> (You could avoid the build of ilasm from Mono trunk).
>>>>
>>>> If it is not the case anymore we can switch all to Mono tools and
>>>> remove the check in the script.
>>>>
>>>> Andrea
>>>>
>>>> On Mon, Mar 22, 2010 at 12:11 PM, Thierry Lafage
>>>> <thi...@in...> wrote:
>>>>
>>>>
>>>>>
>>>>> I forgot to mention that (Mono) ilasm does not complains (not even a
>>>>> warning) if you pass it an unknown option; so this should be ok with
>>>>> older version of ilasm.
>>>>> Regarding "Pnet ilasm", I don't know, but I've been told that this
>>>>> option would be abandonned. If this is really the case, then we should
>>>>> also remove the "if [ `$ILASM --version | ..." test. Tell me: I can do
>>>>> it in this commit.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Thierry Lafage.
>>>>>
>>>>>
>>>>>
>>>>> Thierry Lafage a écrit :
>>>>>
>>>>>
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Here is a patch for our binutils/as script which converts -O option
>>>>>> into forthcoming '-opt:ldc' ilasm option.
>>>>>>
>>>>>> Since the default behavior is not changed, I should commit soon if
>>>>>> nobody complains.
>>>>>>
>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>
>>> Index: scripts/as.in
>>> ===================================================================
>>> --- scripts/as.in (revision 14)
>>> +++ scripts/as.in (working copy)
>>> @@ -23,7 +23,7 @@
>>> shift
>>> ;;
>>> -o)
>>> - PARAM="$PARAM $1$2";
>>> + PARAM="$PARAM $1 $2";
>>> shift
>>> shift
>>> ;;
>>> @@ -34,13 +34,7 @@
>>> esac
>>> done
>>>
>>> -if test "x`$ILASM --version | grep Mono | wc -l`" = "x0"; then
>>> - #needed by Pnet ilasm
>>> - PARAM=`echo "--format dll $PARAM" | sed 's? -o? -o ?'`;
>>> -else
>>> - #needed by Mono ilasm
>>> - PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o? -output:?'`;
>>> -fi
>>> +PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o ? -output:?'`;
>>>
>>> CMD="$ILASM $PARAM"
>>> if test -n "$VERBOSE"; then
>>>
>>>
>>>
>
|
|
From: Thierry L. <thi...@in...> - 2010-03-23 13:21:12
|
Sorry, I misunderstood your point with -output. Here is the (final?) patch. I wait for your approval to commit. Regards, Thierry Lafage. Thierry Lafage a écrit : > Andrea Carlo Ornstein a écrit : > >> Hi, >> >> I would just use -output in the switch and remove the sed at the end >> (keeping the extra arguments '-dll -quiet') >> The hack of no space after -o was there just to simplify the sed at >> the end of the script, now it is not needed. >> >> > > Ok, but I'll have to modify gcc (cil32.h) to make it pass -output to > 'as' instead of -o. Do you really want me to introduce such a version > dependency? (personnally, I don't mind). > > >> If you remove that part, you should cleanup also >> http://clibinutils.svn.sourceforge.net/viewvc/clibinutils/mono-based-binutils/trunk/tools/gcc4cli/utils/CObject.cs?revision=12&view=markup >> There is a hack to fixup an error on varargs methods generated by pnet ilasm. >> just remove fix_DOTGNU_Errors() >> >> > > Ok, I'll check that. > > Regards, > Thierry. > >> Andrea >> >> On Tue, Mar 23, 2010 at 11:34 AM, Thierry Lafage >> <thi...@in...> wrote: >> >> >>> Hi Andrea, >>> >>> Here is a simpler patch for as that is meant to be commited in >>> https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/trunk >>> >>> Since the svn url says that it is a mono-based version, the test for Pnet >>> ilasm is surely not worth anymore. >>> I also added a space between -o and the ouput file in order not to confuse >>> with potential -opt or -o<something> ilasm arguments. Otherwise, calling as >>> with -opt gives: "ilasm /ouput:pt" >>> >>> Comparing to my former patch, I don't propose anymore the -O case because, >>> since the short bytecode optimizations are done in ld, there is no more need >>> for the moment to activate optimizations in the assembly pass. >>> >>> Tell me if it's ok for you, then I'll commit. >>> >>> Regards, >>> >>> Thierry Lafage. >>> >>> >>> >>> Andrea Carlo Ornstein a écrit : >>> >>> >>>> At the beginning when I did the binutils there was a bug in the >>>> release of ilasm. >>>> Only the one from Mono trunk was working. >>>> That is the only reason why the binutils could use also the Pnet ilasm >>>> (You could avoid the build of ilasm from Mono trunk). >>>> >>>> If it is not the case anymore we can switch all to Mono tools and >>>> remove the check in the script. >>>> >>>> Andrea >>>> >>>> On Mon, Mar 22, 2010 at 12:11 PM, Thierry Lafage >>>> <thi...@in...> wrote: >>>> >>>> >>>> >>>>> I forgot to mention that (Mono) ilasm does not complains (not even a >>>>> warning) if you pass it an unknown option; so this should be ok with >>>>> older version of ilasm. >>>>> Regarding "Pnet ilasm", I don't know, but I've been told that this >>>>> option would be abandonned. If this is really the case, then we should >>>>> also remove the "if [ `$ILASM --version | ..." test. Tell me: I can do >>>>> it in this commit. >>>>> >>>>> Regards, >>>>> >>>>> Thierry Lafage. >>>>> >>>>> >>>>> >>>>> Thierry Lafage a écrit : >>>>> >>>>> >>>>> >>>>>> Hi, >>>>>> >>>>>> Here is a patch for our binutils/as script which converts -O option >>>>>> into forthcoming '-opt:ldc' ilasm option. >>>>>> >>>>>> Since the default behavior is not changed, I should commit soon if >>>>>> nobody complains. >>>>>> >>>>>> 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 >>>>> >>>>> >>>>> >>>>> >>> Index: scripts/as.in >>> =================================================================== >>> --- scripts/as.in (revision 14) >>> +++ scripts/as.in (working copy) >>> @@ -23,7 +23,7 @@ >>> shift >>> ;; >>> -o) >>> - PARAM="$PARAM $1$2"; >>> + PARAM="$PARAM $1 $2"; >>> shift >>> shift >>> ;; >>> @@ -34,13 +34,7 @@ >>> esac >>> done >>> >>> -if test "x`$ILASM --version | grep Mono | wc -l`" = "x0"; then >>> - #needed by Pnet ilasm >>> - PARAM=`echo "--format dll $PARAM" | sed 's? -o? -o ?'`; >>> -else >>> - #needed by Mono ilasm >>> - PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o? -output:?'`; >>> -fi >>> +PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o ? -output:?'`; >>> >>> CMD="$ILASM $PARAM" >>> if test -n "$VERBOSE"; then >>> >>> >>> >>> > > ------------------------------------------------------------------------------ > 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 13:06:57
|
Andrea Carlo Ornstein a écrit : > Hi, > > I would just use -output in the switch and remove the sed at the end > (keeping the extra arguments '-dll -quiet') > The hack of no space after -o was there just to simplify the sed at > the end of the script, now it is not needed. > Ok, but I'll have to modify gcc (cil32.h) to make it pass -output to 'as' instead of -o. Do you really want me to introduce such a version dependency? (personnally, I don't mind). > If you remove that part, you should cleanup also > http://clibinutils.svn.sourceforge.net/viewvc/clibinutils/mono-based-binutils/trunk/tools/gcc4cli/utils/CObject.cs?revision=12&view=markup > There is a hack to fixup an error on varargs methods generated by pnet ilasm. > just remove fix_DOTGNU_Errors() > Ok, I'll check that. Regards, Thierry. > Andrea > > On Tue, Mar 23, 2010 at 11:34 AM, Thierry Lafage > <thi...@in...> wrote: > >> Hi Andrea, >> >> Here is a simpler patch for as that is meant to be commited in >> https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/trunk >> >> Since the svn url says that it is a mono-based version, the test for Pnet >> ilasm is surely not worth anymore. >> I also added a space between -o and the ouput file in order not to confuse >> with potential -opt or -o<something> ilasm arguments. Otherwise, calling as >> with -opt gives: "ilasm /ouput:pt" >> >> Comparing to my former patch, I don't propose anymore the -O case because, >> since the short bytecode optimizations are done in ld, there is no more need >> for the moment to activate optimizations in the assembly pass. >> >> Tell me if it's ok for you, then I'll commit. >> >> Regards, >> >> Thierry Lafage. >> >> >> >> Andrea Carlo Ornstein a écrit : >> >>> At the beginning when I did the binutils there was a bug in the >>> release of ilasm. >>> Only the one from Mono trunk was working. >>> That is the only reason why the binutils could use also the Pnet ilasm >>> (You could avoid the build of ilasm from Mono trunk). >>> >>> If it is not the case anymore we can switch all to Mono tools and >>> remove the check in the script. >>> >>> Andrea >>> >>> On Mon, Mar 22, 2010 at 12:11 PM, Thierry Lafage >>> <thi...@in...> wrote: >>> >>> >>>> I forgot to mention that (Mono) ilasm does not complains (not even a >>>> warning) if you pass it an unknown option; so this should be ok with >>>> older version of ilasm. >>>> Regarding "Pnet ilasm", I don't know, but I've been told that this >>>> option would be abandonned. If this is really the case, then we should >>>> also remove the "if [ `$ILASM --version | ..." test. Tell me: I can do >>>> it in this commit. >>>> >>>> Regards, >>>> >>>> Thierry Lafage. >>>> >>>> >>>> >>>> Thierry Lafage a écrit : >>>> >>>> >>>>> Hi, >>>>> >>>>> Here is a patch for our binutils/as script which converts -O option >>>>> into forthcoming '-opt:ldc' ilasm option. >>>>> >>>>> Since the default behavior is not changed, I should commit soon if >>>>> nobody complains. >>>>> >>>>> 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 >>>> >>>> >>>> >> Index: scripts/as.in >> =================================================================== >> --- scripts/as.in (revision 14) >> +++ scripts/as.in (working copy) >> @@ -23,7 +23,7 @@ >> shift >> ;; >> -o) >> - PARAM="$PARAM $1$2"; >> + PARAM="$PARAM $1 $2"; >> shift >> shift >> ;; >> @@ -34,13 +34,7 @@ >> esac >> done >> >> -if test "x`$ILASM --version | grep Mono | wc -l`" = "x0"; then >> - #needed by Pnet ilasm >> - PARAM=`echo "--format dll $PARAM" | sed 's? -o? -o ?'`; >> -else >> - #needed by Mono ilasm >> - PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o? -output:?'`; >> -fi >> +PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o ? -output:?'`; >> >> CMD="$ILASM $PARAM" >> if test -n "$VERBOSE"; then >> >> >> |
|
From: Andrea C. O. <and...@gm...> - 2010-03-23 11:34:54
|
Hi, I would just use -output in the switch and remove the sed at the end (keeping the extra arguments '-dll -quiet') The hack of no space after -o was there just to simplify the sed at the end of the script, now it is not needed. If you remove that part, you should cleanup also http://clibinutils.svn.sourceforge.net/viewvc/clibinutils/mono-based-binutils/trunk/tools/gcc4cli/utils/CObject.cs?revision=12&view=markup There is a hack to fixup an error on varargs methods generated by pnet ilasm. just remove fix_DOTGNU_Errors() Andrea On Tue, Mar 23, 2010 at 11:34 AM, Thierry Lafage <thi...@in...> wrote: > Hi Andrea, > > Here is a simpler patch for as that is meant to be commited in > https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/trunk > > Since the svn url says that it is a mono-based version, the test for Pnet > ilasm is surely not worth anymore. > I also added a space between -o and the ouput file in order not to confuse > with potential -opt or -o<something> ilasm arguments. Otherwise, calling as > with -opt gives: "ilasm /ouput:pt" > > Comparing to my former patch, I don't propose anymore the -O case because, > since the short bytecode optimizations are done in ld, there is no more need > for the moment to activate optimizations in the assembly pass. > > Tell me if it's ok for you, then I'll commit. > > Regards, > > Thierry Lafage. > > > > Andrea Carlo Ornstein a écrit : >> >> At the beginning when I did the binutils there was a bug in the >> release of ilasm. >> Only the one from Mono trunk was working. >> That is the only reason why the binutils could use also the Pnet ilasm >> (You could avoid the build of ilasm from Mono trunk). >> >> If it is not the case anymore we can switch all to Mono tools and >> remove the check in the script. >> >> Andrea >> >> On Mon, Mar 22, 2010 at 12:11 PM, Thierry Lafage >> <thi...@in...> wrote: >> >>> >>> I forgot to mention that (Mono) ilasm does not complains (not even a >>> warning) if you pass it an unknown option; so this should be ok with >>> older version of ilasm. >>> Regarding "Pnet ilasm", I don't know, but I've been told that this >>> option would be abandonned. If this is really the case, then we should >>> also remove the "if [ `$ILASM --version | ..." test. Tell me: I can do >>> it in this commit. >>> >>> Regards, >>> >>> Thierry Lafage. >>> >>> >>> >>> Thierry Lafage a écrit : >>> >>>> >>>> Hi, >>>> >>>> Here is a patch for our binutils/as script which converts -O option >>>> into forthcoming '-opt:ldc' ilasm option. >>>> >>>> Since the default behavior is not changed, I should commit soon if >>>> nobody complains. >>>> >>>> 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 >>> >>> > > Index: scripts/as.in > =================================================================== > --- scripts/as.in (revision 14) > +++ scripts/as.in (working copy) > @@ -23,7 +23,7 @@ > shift > ;; > -o) > - PARAM="$PARAM $1$2"; > + PARAM="$PARAM $1 $2"; > shift > shift > ;; > @@ -34,13 +34,7 @@ > esac > done > > -if test "x`$ILASM --version | grep Mono | wc -l`" = "x0"; then > - #needed by Pnet ilasm > - PARAM=`echo "--format dll $PARAM" | sed 's? -o? -o ?'`; > -else > - #needed by Mono ilasm > - PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o? -output:?'`; > -fi > +PARAM=`echo "-dll -quiet $PARAM" | sed 's? -o ? -output:?'`; > > CMD="$ILASM $PARAM" > if test -n "$VERBOSE"; then > > |
|
From: Andrea C. O. <and...@gm...> - 2010-03-23 11:26:47
|
I already changed the wiki on sourceforge https://sourceforge.net/apps/mediawiki/gcc4cli/index.php?title=Main_Page I cannot change the README and the html pages on gcc from here. I am ok with the changes and also having the mono based one as preferred. After a short period of transition I would like to empty the dirs svn://gcc.gnu.org/svn/gcc/branches/st/binutils and svn://gcc.gnu.org/svn/gcc/branches/st/mono-based-binutils and keep there (in both) just a README file saying that the code has been moved to the sourceforge project with the proper links Erven, you know better than me who are the users at this point, I let you decide how long is this 'short period' :) I will create a couple of mailing list also for cli binutils (one for the ci and one for the development discussions) Andrea On Tue, Mar 23, 2010 at 8:40 AM, Erven Rohou <erv...@in...> wrote: > Ciao Andrea, > > Many thanks for the various fixes. > Probably, we should update the README in gcc.../branches/st/README to reflect > the new binutils location. > > I am also tempted to change the order of the sections: first the build > instructions for the Mono toolchain, then DotGnu. Maybe we can also say the Mono > is the preferred way? > > -- > Erven. > > ------------------------------------------------------------------------------ > 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:35:04
|
Hi Andrea, Here is a simpler patch for as that is meant to be commited in https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/trunk Since the svn url says that it is a mono-based version, the test for Pnet ilasm is surely not worth anymore. I also added a space between -o and the ouput file in order not to confuse with potential -opt or -o<something> ilasm arguments. Otherwise, calling as with -opt gives: "ilasm /ouput:pt" Comparing to my former patch, I don't propose anymore the -O case because, since the short bytecode optimizations are done in ld, there is no more need for the moment to activate optimizations in the assembly pass. Tell me if it's ok for you, then I'll commit. Regards, Thierry Lafage. Andrea Carlo Ornstein a écrit : > At the beginning when I did the binutils there was a bug in the > release of ilasm. > Only the one from Mono trunk was working. > That is the only reason why the binutils could use also the Pnet ilasm > (You could avoid the build of ilasm from Mono trunk). > > If it is not the case anymore we can switch all to Mono tools and > remove the check in the script. > > Andrea > > On Mon, Mar 22, 2010 at 12:11 PM, Thierry Lafage > <thi...@in...> wrote: > >> I forgot to mention that (Mono) ilasm does not complains (not even a >> warning) if you pass it an unknown option; so this should be ok with >> older version of ilasm. >> Regarding "Pnet ilasm", I don't know, but I've been told that this >> option would be abandonned. If this is really the case, then we should >> also remove the "if [ `$ILASM --version | ..." test. Tell me: I can do >> it in this commit. >> >> Regards, >> >> Thierry Lafage. >> >> >> >> Thierry Lafage a écrit : >> >>> Hi, >>> >>> Here is a patch for our binutils/as script which converts -O option >>> into forthcoming '-opt:ldc' ilasm option. >>> >>> Since the default behavior is not changed, I should commit soon if >>> nobody complains. >>> >>> 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 >> >> |
|
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 > |
|
From: Erven R. <erv...@in...> - 2010-03-23 07:40:58
|
Ciao Andrea, Many thanks for the various fixes. Probably, we should update the README in gcc.../branches/st/README to reflect the new binutils location. I am also tempted to change the order of the sections: first the build instructions for the Mono toolchain, then DotGnu. Maybe we can also say the Mono is the preferred way? -- Erven. |
|
From: Erven R. <erv...@in...> - 2010-03-22 18:46:57
|
Andrea Carlo Ornstein a écrit : > Hi all, > > I think we should do the ci and solve the problems for the time being. Just committed. > The real point here is that we have just one target description. > My initial idea was to have different machine types: > 32bit vs 64bit > targeting a VM vs using cil as intermediate representation > > something like > cil32-ir > cil64-ir > cil32-vm > cil64-vm This is a good idea! We should work on it sometime... ;-) Ciao, -- Erven. > > and even more variants if we consider endianness > > 32 vs 64 changes the machine description and gimple_to_cil > > IR vs VM changes mostly the runtime environment: > what do we do with setjump/longjump, signals, (in C++ exceptions), and so on > > when targetting a VM we map them on the CLI runtime services > when using it as an IR we may keep them as calls that are recognized > properly by the users of the code produced. > > Andrea > > On Fri, Feb 19, 2010 at 11:38 AM, Erven Rohou <erv...@in...> wrote: >> Gabriele Svelto a écrit : >>> 2010/2/19 Erven Rohou <erv...@in...>: >>>> Ciao, >>>> >>>> Many benchmarks (unfortunately) use setjmp and longjmp, which we do not >>>> support. >>>> However, longjmp is often used to handle exceptional situations, mostly >>>> errors. >>>> Here is a proposal: we could define setjmp to return 0, and longjmp to >>>> abort (or >>>> print a message and abort,...) We could compile and run benchmarks that >>>> do not >>>> have errors. Probably we keep a warning in the header file. >>>> What do you think? >>> Sounds like a good idea, I believe most of the stuff will work well >>> under normal conditions. >>> >>> Gabriele >>> >> Here is a patch for libstd. Please let me know if you have any comment. >> As usual I am having problems with automake/autoconf/etc. >> I modified Makefile.am to add the file setjmp.c. autoreconf generated lots >> of stuff that breaks my build. So I patched Makefile.in by hand. It seems >> that some tool also modified config.h.in and configure. >> Anyway, if somebody has an idea, I am willing do it properly. :-) >> >> -- >> Erven. >> > |
|
From: Andrea C. O. <and...@gm...> - 2010-03-22 16:29:15
|
It changes a lot of files because there is a change in the autotools version you are using. Originally we used autoconf 2.59 (quite old) you are using 2.63 It probably changes all Makefile.in configure and config.h and aclocal.m4 It's fine. I think we can move to a new version. I even use 2.65 now :) Andrea On Fri, Feb 19, 2010 at 11:38 AM, Erven Rohou <erv...@in...> wrote: > Gabriele Svelto a écrit : >> >> 2010/2/19 Erven Rohou <erv...@in...>: >>> >>> Ciao, >>> >>> Many benchmarks (unfortunately) use setjmp and longjmp, which we do not >>> support. >>> However, longjmp is often used to handle exceptional situations, mostly >>> errors. >>> Here is a proposal: we could define setjmp to return 0, and longjmp to >>> abort (or >>> print a message and abort,...) We could compile and run benchmarks that >>> do not >>> have errors. Probably we keep a warning in the header file. >>> What do you think? >> >> Sounds like a good idea, I believe most of the stuff will work well >> under normal conditions. >> >> Gabriele >> > > Here is a patch for libstd. Please let me know if you have any comment. > As usual I am having problems with automake/autoconf/etc. > I modified Makefile.am to add the file setjmp.c. autoreconf generated lots > of stuff that breaks my build. So I patched Makefile.in by hand. It seems > that some tool also modified config.h.in and configure. > Anyway, if somebody has an idea, I am willing do it properly. :-) > > -- > Erven. > |
|
From: Andrea C. O. <and...@gm...> - 2010-03-22 16:20:08
|
Hi all, I think we should do the ci and solve the problems for the time being. The real point here is that we have just one target description. My initial idea was to have different machine types: 32bit vs 64bit targeting a VM vs using cil as intermediate representation something like cil32-ir cil64-ir cil32-vm cil64-vm and even more variants if we consider endianness 32 vs 64 changes the machine description and gimple_to_cil IR vs VM changes mostly the runtime environment: what do we do with setjump/longjump, signals, (in C++ exceptions), and so on when targetting a VM we map them on the CLI runtime services when using it as an IR we may keep them as calls that are recognized properly by the users of the code produced. Andrea On Fri, Feb 19, 2010 at 11:38 AM, Erven Rohou <erv...@in...> wrote: > Gabriele Svelto a écrit : >> >> 2010/2/19 Erven Rohou <erv...@in...>: >>> >>> Ciao, >>> >>> Many benchmarks (unfortunately) use setjmp and longjmp, which we do not >>> support. >>> However, longjmp is often used to handle exceptional situations, mostly >>> errors. >>> Here is a proposal: we could define setjmp to return 0, and longjmp to >>> abort (or >>> print a message and abort,...) We could compile and run benchmarks that >>> do not >>> have errors. Probably we keep a warning in the header file. >>> What do you think? >> >> Sounds like a good idea, I believe most of the stuff will work well >> under normal conditions. >> >> Gabriele >> > > Here is a patch for libstd. Please let me know if you have any comment. > As usual I am having problems with automake/autoconf/etc. > I modified Makefile.am to add the file setjmp.c. autoreconf generated lots > of stuff that breaks my build. So I patched Makefile.in by hand. It seems > that some tool also modified config.h.in and configure. > Anyway, if somebody has an idea, I am willing do it properly. :-) > > -- > Erven. > |
|
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: Andrea C. O. <and...@gm...> - 2010-03-22 15:36:24
|
Hi, Some time ago we created a sourceforge project for the cli binutils https://sourceforge.net/projects/clibinutils/ The intention was to create specific mailing list and to move there the code. It is unusual to have the binutils on the gcc repository. Even more if they are written in C#. I start to move them to the new repository but never announced it becouse you all were working on the paper I did not want to break things. But if we start modifying them .... At the moment they are in sync, or there is same extra update in the sourceforge repository. If we do not move now, at least we can duplicate the ci in sourceforge. Let me know what you think is the best solution. Andrea |
|
From: Andrea C. O. <and...@gm...> - 2010-03-22 15:29:02
|
At the beginning when I did the binutils there was a bug in the release of ilasm. Only the one from Mono trunk was working. That is the only reason why the binutils could use also the Pnet ilasm (You could avoid the build of ilasm from Mono trunk). If it is not the case anymore we can switch all to Mono tools and remove the check in the script. Andrea On Mon, Mar 22, 2010 at 12:11 PM, Thierry Lafage <thi...@in...> wrote: > I forgot to mention that (Mono) ilasm does not complains (not even a > warning) if you pass it an unknown option; so this should be ok with > older version of ilasm. > Regarding "Pnet ilasm", I don't know, but I've been told that this > option would be abandonned. If this is really the case, then we should > also remove the "if [ `$ILASM --version | ..." test. Tell me: I can do > it in this commit. > > Regards, > > Thierry Lafage. > > > > Thierry Lafage a écrit : >> Hi, >> >> Here is a patch for our binutils/as script which converts -O option >> into forthcoming '-opt:ldc' ilasm option. >> >> Since the default behavior is not changed, I should commit soon if >> nobody complains. >> >> 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 > |
|
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 > > |
