Hi Seb,
Sebastien Lelong wrote: >> I read about the issue Wouter had and Kyle his response. Has this >> impact on our next release? >> >> > I did not observe such slow compile time. Even on a big/fat piece of code: > my motor controller is more than 2800 bytes long (on 16F88), it compiles the > same with 2.4i and 2.4j, I don't know how big is Wouter's code, and it's > probably not related to how big it is. I compiled the Wisp648 firmware (output is about 3800 code words) and see the same compiler behaviour. With 2.4j the compile takes here about 80 seconds, with 2.4i only about 2 seconds (on an AMD Athlon 64 3800 X2 using only 1 of the 2 CPUs). With the -no-variable-reuse option the compile time with 2.4j becomes about the same as with 2.4i. I have no other Jal programs of any substantial size to compare. > Anyway I guess a release won't occur within 2 weeks (?), so we should > hopefully have news on this by this time. I think too that it will take Kyle quite some time to fix this. We might copy Kyle's recommendation (using the -no-variable-reuse option) in the announcement or README when releasing the next Jallib. Regards, Rob. -- Rob Hamerling, Vianen, NL (http://www.robh.nl/) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
