From: Bruce <ill...@gm...> - 2007-07-29 06:32:53
|
Hey Ya'll: Because the AOT is very massive, a few of us are in agreement that the AOT needs to be tested as thoroughly as possible. I have posted, on the Wiki, a short guide to writing tests for the AOT: http://sharpos.sourceforge.net/cgi-bin/trac.cgi/wiki/HowTo%3A%20AOT%20Unit%20Testing<I%20have%20posted,%20on%20the%20Wiki,%20a%20short%20guide%20to%20writing%20tests%20for%20the%20AOT:%20http://sharpos.sourceforge.net/cgi-bin/trac.cgi/wiki/HowTo%253A%2520AOT%2520Unit%2520Testing> The guide does not go into detail as to the granularity of tests, or the necessity of any particular tests or types of tests - just simply how a test is written. It can be expanded either by the rest of you folks, or as suggestions are made I will maintain the article myself. -Bruce aka Illuminus |
From: Darx K. <dar...@gm...> - 2007-07-29 10:33:35
|
Hi The HowTo is really great and I am glad we have it finally. :D There is only one thing that should be changed and that is the Test Case Example. The AOT already does some basic constant folding that means that when it finds something like 1+2 then it computes that so the if statement becomes if (3 == 3). Other optimizations will come later and the whole code can be reduced to "return 1;". So it would be great if the CMP method calls another one that does the test and CMP only compares the result and returns 1 or 0. Something like this: public unsafe static uint Misc2 (uint granularity) { switch (granularity) { case 0: return 4096; case 1: return 131072; default: return 0xFFFFFFFF; } } public unsafe static uint CMPMisc2a () { if (Misc2 (0) == 4096) return 1; return 0; } That way there will be no such optimizations and the test will be more reliable. Chriss. Bruce wrote: > Hey Ya'll: > > Because the AOT is very massive, a few of us are in agreement that the > AOT needs to be tested as thoroughly as possible. > > I have posted, on the Wiki, a short guide to writing tests for the > AOT: > http://sharpos.sourceforge.net/cgi-bin/trac.cgi/wiki/HowTo%3A%20AOT%20Unit%20Testing > <I%20have%20posted,%20on%20the%20Wiki,%20a%20short%20guide%20to%20writing%20tests%20for%20the%20AOT:%20http://sharpos.sourceforge.net/cgi-bin/trac.cgi/wiki/HowTo%253A%2520AOT%2520Unit%2520Testing> > > The guide does not go into detail as to the granularity of tests, or > the necessity of any particular tests or types of tests - just simply > how a test is written. It can be expanded either by the rest of you > folks, or as suggestions are made I will maintain the article myself. > > -Bruce > aka Illuminus > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ------------------------------------------------------------------------ > > _______________________________________________ > SharpOS-Developers mailing list > Sha...@li... > https://lists.sourceforge.net/lists/listinfo/sharpos-developers > |
From: William L. <xfu...@gm...> - 2007-07-29 16:17:15
|
The test kernel still fails to compile for me. On 7/29/07, Darx Kies <dar...@gm...> wrote: > Hi > > The HowTo is really great and I am glad we have it finally. :D > > There is only one thing that should be changed and that is the Test Case > Example. > The AOT already does some basic constant folding that means that when it > finds something like 1+2 > then it computes that so the if statement becomes if (3 == 3). Other > optimizations will come later > and the whole code can be reduced to "return 1;". > > So it would be great if the CMP method calls another one that does the > test and CMP only compares the result and returns 1 or 0. > Something like this: > > public unsafe static uint Misc2 (uint granularity) > { > switch (granularity) { > case 0: > return 4096; > case 1: > return 131072; > default: > return 0xFFFFFFFF; > } > } > > public unsafe static uint CMPMisc2a () > { > if (Misc2 (0) == 4096) > return 1; > > return 0; > } > > That way there will be no such optimizations and the test will be more > reliable. > > Chriss. > > Bruce wrote: > > Hey Ya'll: > > > > Because the AOT is very massive, a few of us are in agreement that the > > AOT needs to be tested as thoroughly as possible. > > > > I have posted, on the Wiki, a short guide to writing tests for the > > AOT: > > http://sharpos.sourceforge.net/cgi-bin/trac.cgi/wiki/HowTo%3A%20AOT%20Unit%20Testing > > <I%20have%20posted,%20on%20the%20Wiki,%20a%20short%20guide%20to%20writing%20tests%20for%20the%20AOT:%20http://sharpos.sourceforge.net/cgi-bin/trac.cgi/wiki/HowTo%253A%2520AOT%2520Unit%2520Testing> > > > > The guide does not go into detail as to the granularity of tests, or > > the necessity of any particular tests or types of tests - just simply > > how a test is written. It can be expanded either by the rest of you > > folks, or as suggestions are made I will maintain the article myself. > > > > -Bruce > > aka Illuminus > > ------------------------------------------------------------------------ > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > SharpOS-Developers mailing list > > Sha...@li... > > https://lists.sourceforge.net/lists/listinfo/sharpos-developers > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > SharpOS-Developers mailing list > Sha...@li... > https://lists.sourceforge.net/lists/listinfo/sharpos-developers > -- fury long name: William Lahti handle :: fury freenode :: xfury blog :: http://xfurious.blogspot.com/ |
From: Darx K. <dar...@gm...> - 2007-07-29 18:54:02
|
Hi I just checked it and it works for me. What is the error? What are you using? Mono or .NET? And with what parameters do you run the AOT? Chriss. William Lahti wrote: > The test kernel still fails to compile for me. > > On 7/29/07, Darx Kies <dar...@gm...> wrote: > >> Hi >> >> The HowTo is really great and I am glad we have it finally. :D >> >> There is only one thing that should be changed and that is the Test Case >> Example. >> The AOT already does some basic constant folding that means that when it >> finds something like 1+2 >> then it computes that so the if statement becomes if (3 == 3). Other >> optimizations will come later >> and the whole code can be reduced to "return 1;". >> >> So it would be great if the CMP method calls another one that does the >> test and CMP only compares the result and returns 1 or 0. >> Something like this: >> >> public unsafe static uint Misc2 (uint granularity) >> { >> switch (granularity) { >> case 0: >> return 4096; >> case 1: >> return 131072; >> default: >> return 0xFFFFFFFF; >> } >> } >> >> public unsafe static uint CMPMisc2a () >> { >> if (Misc2 (0) == 4096) >> return 1; >> >> return 0; >> } >> >> That way there will be no such optimizations and the test will be more >> reliable. >> >> Chriss. >> >> Bruce wrote: >> >>> Hey Ya'll: >>> >>> Because the AOT is very massive, a few of us are in agreement that the >>> AOT needs to be tested as thoroughly as possible. >>> >>> I have posted, on the Wiki, a short guide to writing tests for the >>> AOT: >>> http://sharpos.sourceforge.net/cgi-bin/trac.cgi/wiki/HowTo%3A%20AOT%20Unit%20Testing >>> <I%20have%20posted,%20on%20the%20Wiki,%20a%20short%20guide%20to%20writing%20tests%20for%20the%20AOT:%20http://sharpos.sourceforge.net/cgi-bin/trac.cgi/wiki/HowTo%253A%2520AOT%2520Unit%2520Testing> >>> >>> The guide does not go into detail as to the granularity of tests, or >>> the necessity of any particular tests or types of tests - just simply >>> how a test is written. It can be expanded either by the rest of you >>> folks, or as suggestions are made I will maintain the article myself. >>> >>> -Bruce >>> aka Illuminus >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> SharpOS-Developers mailing list >>> Sha...@li... >>> https://lists.sourceforge.net/lists/listinfo/sharpos-developers >>> >>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> SharpOS-Developers mailing list >> Sha...@li... >> https://lists.sourceforge.net/lists/listinfo/sharpos-developers >> >> > > > |
From: Bruce <ill...@gm...> - 2007-07-30 01:10:19
|
> > The test kernel still fails to compile for me. *sigh* I think I'm going to set up a continuous integration system for us. Then, anyone that breaks any of the codebase, can get an automated e-mail telling them what they did! *wink* But in all honesty, I am thinking about setting one up. I'm quite fond of, and familiar with, CruiseControl.NET. I think I could set it up on a computer at home, and we can push reports to SourceForge, (or rather, have SourceForge pull the reports using a crontab). But I might be wrong... And we can set up the test kernel to write test results to the emulated "serial port", which Bochs et al can direct to a file which can be parsed. Eh? Eh? Any thoughts? |
From: Darx K. <dar...@gm...> - 2007-07-30 10:30:25
|
Hi That is really a very great idea! And I don't like it now that it stops after the first error and sending the whole report over the serial port sounds like a very great idea! Implementing the serial support would be fun too. :D Chriss. Bruce wrote: > > The test kernel still fails to compile for me. > > > *sigh* I think I'm going to set up a continuous integration system for us. > > Then, anyone that breaks any of the codebase, can get an automated > e-mail telling them what they did! *wink* > > But in all honesty, I am thinking about setting one up. I'm quite fond > of, and familiar with, CruiseControl.NET. > > I think I could set it up on a computer at home, and we can push > reports to SourceForge, (or rather, have SourceForge pull the reports > using a crontab). But I might be wrong... > > And we can set up the test kernel to write test results to the > emulated "serial port", which Bochs et al can direct to a file which > can be parsed. Eh? Eh? > > Any thoughts? > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ------------------------------------------------------------------------ > > _______________________________________________ > SharpOS-Developers mailing list > Sha...@li... > https://lists.sourceforge.net/lists/listinfo/sharpos-developers > |
From: Bruce <ill...@gm...> - 2007-07-30 01:02:53
|
On 7/29/07, Darx Kies <dar...@gm...> wrote: > > Hi > > The HowTo is really great and I am glad we have it finally. :D > > There is only one thing that should be changed and that is the Test Case > Example. > The AOT already does some basic constant folding that means that when it > finds something like 1+2 > then it computes that so the if statement becomes if (3 == 3). Other > optimizations will come later > and the whole code can be reduced to "return 1;". > > So it would be great if the CMP method calls another one that does the > test and CMP only compares the result and returns 1 or 0. > Something like this: > > public unsafe static uint Misc2 (uint granularity) > { > switch (granularity) { > case 0: > return 4096; > case 1: > return 131072; > default: > return 0xFFFFFFFF; > } > } > > public unsafe static uint CMPMisc2a () > { > if (Misc2 (0) == 4096) > return 1; > > return 0; > } > > That way there will be no such optimizations and the test will be more > reliable. I will ammend the Wiki as soon as I get the chance. |