Looking for beta testers of the Windows JAL Compiler

[Rob]

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

[Gilles BARTHELEMY]

Hello,

I tried this new version, by modifying and compiling several programs more or less complex with no bug.

It seems Ok to me.

Regards,

gilles

[Gilles BARTHELEMY]

Sorry I was not precise enough...

Test done under Windows 10 /64. 

I compared the produced "hex" sizes  with both old and new version of the compiler, it was exactly the same. I sent code to 16F877A, 16F628A, 12F675, 16F15376. All went Ok.

[Rob CJ]

Hello Gilles,

Thanks for your elaborate feedback. I created a new release on GitHub and removed the temporary versions.

Kind regards,

Rob

---

Van: jal...@googlegroups.com <jal...@googlegroups.com> namens Gilles BARTHELEMY <bar...@gmail.com>
Verzonden: maandag 16 september 2019 09:33
Aan: jallib <jal...@googlegroups.com>
Onderwerp: [jallib] Re: Looking for beta testers of the Windows JAL Compiler

 

Sorry I was not precise enough...

Test done under Windows 10 /64. 

I compared the produced "hex" sizes  with both old and new version of the compiler, it was exactly the same. I sent code to 16F877A, 16F628A, 12F675, 16F15376. All went Ok.

--
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 jallib+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/1cd70ce0-27d9-4238-a1f0-405ca83a718f%40googlegroups.com.

[Sunish Issac]

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

--

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 jallib+un...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/faa077ef-7359-45c8-a691-5b2ba02162ca%40googlegroups.com.

[Rob CJ]

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: jal...@googlegroups.com <jal...@googlegroups.com> namens Sunish Issac <sunis...@gmail.com>
Verzonden: zaterdag 12 oktober 2019 04:14
Aan: jal...@googlegroups.com <jal...@googlegroups.com>
Onderwerp: Re: [jallib] Looking for beta testers of the Windows JAL Compiler

 

To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/CAFGw2pFCxogDsJnqSsMC35K4W%3DDMtmcT47btvyZpADwF7EQcTg%40mail.gmail.com.

[Zet Weeh]

Hi Rob

I tested the 32 and 64 version on two different computers with W10-32 bit and W10-64 bit.

I used 3 JAL programs on each computer with blinking leds, PWM and writing to a memory chip.

All was working well and without problems.

I have a suggestion about the name.

I understand this is a totaly new build. So call it 'jalv3_32' and 'jalv3_64'.

So it is clear for everybody that this is the latest version.

Kind regards,

Peter

Op dinsdag 10 september 2019 19:20:21 UTC+2 schreef Rob:

[Rob CJ]

Hi Zet,

Thanks for testing this and sharing your results.

There is a reason for not changing the file name and that is that when you install a new Jallib version and you are using JALEdit or JALIDE you do not have to change anything since the compiler name remains the same. Next to that quite some Python scripts use the JAL compiler for verification and release and we do not want to change the scripts for every version change of the compiler. 

As you know the compiler shows its version when you use it:  jal jalv25r3 (compiled Sep 15 2019).

Again, thank for sharing the info and your suggestion. 

Kind regards,

Rob

---

Van: jal...@googlegroups.com <jal...@googlegroups.com> namens Zet Weeh <zet....@gmail.com>
Verzonden: zaterdag 9 november 2019 23:44
Aan: jallib <jal...@googlegroups.com>
Onderwerp: [jallib] Re: Looking for beta testers of the Windows JAL Compiler

 

--

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 jallib+un...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/a2c4945d-14ee-488d-b6f0-18fd7a692755%40googlegroups.com.

[vasi vasi]

Under UNIX(MAC OS X)/Linux/HaikuOS world, symlinks should be the solution. The symlink name remains the same, but the link can be edited - this should help when working with various versions (I do this with gcc).

To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/AM0PR07MB494876979E3F0FAB02CC5629E6750%40AM0PR07MB4948.eurprd07.prod.outlook.com.

--

Vasi