Hi Sunish,

Thanks for the feedback. It is correct that for some PIC types less code is 
produced since some statements were removed that were not needed. The same 
statements that caused the skip error problem by the way.

Good to see that you also got rid of a skip error problem. I thought I was the 
only one who had it.

If you encounter any issues let me know.

Kind regards,

Rob

________________________________
Van: [email protected] <[email protected]> namens Sunish Issac 
<[email protected]>
Verzonden: zaterdag 12 oktober 2019 04:14
Aan: [email protected] <[email protected]>
Onderwerp: Re: [jallib] Looking for beta testers of the Windows JAL Compiler

Dear Rob,

A bit late in testing, but your new compiler 64bit version, windows helped me 
get rid of the skip error warning message and there's also a slight reduction 
of code size and one stack size less in hardware.

Find below the compiler outputs
Compilation started at :12-Oct-19 07:36:42
jal jalv25r2 (compiled Jan 12 2019)
173 branches checked, 0 errors
446 data accesses checked, 0 errors
[Warning] (16f1455_SBHID_password.jal) [Line 142]  skip error at 0x0470
95 skips checked, 1 errors
[Warning] (16f1455_SBHID_password.jal) [Line 142]  skip error at 0x0470
Compiler CommandLine:  
C:\Users\sunish.issac\DOWNLO~1\ELECTR~1\JALLIB~1.0BE\compiler\jalv2.exe 
"C:\Users\sunish.issac\Dropbox\Projects\HW\PIC\JAL\PasswordSender\src\16f1455\16f1455_SBHID_password.jal"
 -s 
"C:\Users\sunish.issac\Dropbox\Projects\HW\PIC\JAL\PasswordSender\src\16f1455\;C:\Users\sunish.issac\DOWNLO~1\ELECTR~1\JALLIB~1.0BE\lib"
 -no-variable-reuse

Errors :0       Warnings :1
Code   :1611/8192    Data:95/1024  Hardware Stack : 7/16  Software Stack :80


Compilation started at :12-Oct-19 07:38:10
jal jalv25r3 (compiled Sep 15 2019)
162 branches checked, 0 errors
446 data accesses checked, 0 errors
95 skips checked, 0 errors
Compiler CommandLine:  C:\jal1.3\compiler\jalv2_64.exe 
"C:\Users\sunish.issac\Dropbox\Projects\HW\PIC\JAL\PasswordSender\src\16f1455\16f1455_SBHID_password.jal"
 -s 
"C:\Users\sunish.issac\Dropbox\Projects\HW\PIC\JAL\PasswordSender\src\16f1455\;C:\Users\sunish.issac\DOWNLO~1\ELECTR~1\JALLIB~1.0BE\lib"
 -no-variable-reuse

Errors :0       Warnings :0
Code   :1569/8192    Data:95/1024  Hardware Stack : 6/16  Software Stack :80

Yet to to test on real hardware, I have some new boards to test so will update 
once its's done.

Kind regards,
Sunish

On Tue, Sep 10, 2019 at 10:50 PM Rob 
<[email protected]<mailto:[email protected]>> wrote:
Hello JAL users,

I am looking for people that want to test the new version of the JAL compiler 
under Windows (Linux is also allowed if you want to play with it). Main reason 
is that I compiled the compiler using a different c-compiler. This because the 
current JAL 32-bit Windows compiler shows random (but still correct) behavior 
assigning variables to data space. Since it is only for the 32-bit version I 
suspected Visual Studio with which I create the new JAL compiler.

So I recompiled the JAL compiler sources for Windows with a different 
c-compiler and that fixed the problem so my plan is to compile the JAL compiler 
using this c-compiler. In order not to mix up things too much I used for these 
compilers the same names as are used for the Linux versions but they have the 
extension '.exe':
jalv2-i686.exe    : Newly created Windows 32-bit binary
jalv2-x86-64.exe  : Newly created Windows 64-bit binary
You can find the compilers here:
https://github.com/jallib/jalv2compiler/tree/master/bin

What you will also see is that these compiler are smaller in size than their 
Visual Studio counterparts (jalv2.exe and jalv2_64.exe). As I mentioned earlier 
this version of the compiler also fixed this issue:
https://github.com/jallib/jalv2compiler/issues/8

If you are testing it let me know if it works or not.

Thanks for your help.

Kind regards,

Rob

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/faa077ef-7359-45c8-a691-5b2ba02162ca%40googlegroups.com<https://groups.google.com/d/msgid/jallib/faa077ef-7359-45c8-a691-5b2ba02162ca%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/CAFGw2pFCxogDsJnqSsMC35K4W%3DDMtmcT47btvyZpADwF7EQcTg%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CAFGw2pFCxogDsJnqSsMC35K4W%3DDMtmcT47btvyZpADwF7EQcTg%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/AM0PR07MB4948732F7F3B10D2BDB3248CE6960%40AM0PR07MB4948.eurprd07.prod.outlook.com.

Reply via email to