Hi Seb, Please provide me the unittest file(s) (and a short description what you want to test/expect), and I will try to make it work with Picshell Regards
On Jan 29, 9:19 pm, Sebastien Lelong <[email protected]> wrote: > Hi Albert, > > I think this issue isn't related to PICShell, nor to the compiler... From > what I can understand, compiler 2.4m better optimizes variables than 2.4l. > This means some variables used in unittests weren't found in ASM, so > PICShell can't link jal code to ASM code. > > In order to fix this, I update "unittest.jal" library. This basically uses > the tested value, so it's not optimized away anymore. See diff: > > http://code.google.com/p/jallib/source/detail?r=1594 > > I can't see how this could be fixed in PICShell... > > PS: I can remember having seen an issue in Kyle's list talking about > generating a more readable ASM code. This may break PICShell's unittests, > and should be regularly checked > > PPS: I tried to write unittests to test TRIS ports for 18F4550, but they > didn't seem to work. I tested the code in real life, yet PICShell seems not > be able to test every thing. Can I bother you with that ? Not an emergency > for me, I kind of give up about these unittests, but it would ideally be > better to dig this... I sometimes have problems to run unittests, should I > report every time ? Let me know :) > > Cheers, > Seb > > 2010/1/29 AlbertF <[email protected]> > > > > > > > Hi Seb, > > Is this issue already resolved, if not, is it related to Picshell > > Albert > > > On Jan 13, 5:02 pm, Sebastien Lelong <[email protected]> > > wrote: > > > Hi guys, > > > > It seems unittests can't be run anymore with last 2.4m compiler: > > > > $ jallib unittest test/unittest/16f877_adc.jalt > > > /tmp/jallib_HV2Lc8_test_combo_1vref_6an.jal compiled, running tests... > > > Can't run test 'test_test' because var 'a' can't be found > > > Can't run test 'test_pcfg_combo' because var 'adcon1_temp' can't be found > > > Can't run test 'test_pcfg_combo' because var 'adcon1_temp' can't be found > > > ... > > > > I think it's due to some optimizations the compiler does, making some > > > variables fade away... > > > This hasn't revealed with buildbot because unitests aren't run at all, > > and > > > exit code is 0 (I fixed this). > > > > I need to check this some more... > > > > Cheers, > > > Seb > > > -- > > > Sébastien Lelonghttp://www.sirloon.nethttp://sirbot.org > > > -- > > You received this message because you are subscribed to the Google Groups > > "jallib" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<jallib%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/jallib?hl=en. > > -- > Sébastien Lelonghttp://www.sirloon.nethttp://sirbot.org -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
