New compiler error started this morning, Monday /bin/sh: 1: arm-none-eabi-gcc: not found

Mon 2019.01.28

Using native WebIDE was able to upload "send" to Pico all weekend without error. This morning, Monday 9:00amCST noticed I am now getting the following error:

 2v00.103 (c) 2018 G.Williams
>---------------------------------------­------------
                                 COMPILER MESSAGE
----------------------------------------­-----------
/bin/sh: 1: arm-none-eabi-gcc: not found
----------------------------------------­-----------
WARNING: Function marked with "compiled" uploaded in source form

The WARNING is understood and has always been present.

Web IDE version 0.70.4

Not doing anything fancy as in these:

http://forum.espruino.com/conversations/­295704/
http://forum.espruino.com/conversations/­284713/
http://forum.espruino.com/conversations/­316998/

Just uploading a source that uses require to load modules that contain both E.compiledC( and the keyword "compiled" all of which functioned fine previously.

---cont

Sidebar: handle a related comment without a new post

Just read your response #5 use of "compiled"

http://forum.espruino.com/conversations/­330092/#comment14594247

'Honestly I think for everyone I've seen that has tried to use compiled this far it's been a huge mistake, so I would avoid it if at all possible.'

Was avoiding "compiled" a general comment or specifically related to device APA102 for that thread?

Thanks for letting me know - it should be fixed now. I'd done an update/restart on the server and there was a path issue.

Was avoiding "compiled" a general comment

Yes, it's a general comment. For instance in the modules you sent me for inclusion in EspruinoDocs the compiled functions weren't actually compiled anyway because they were inside a class declaration. In the cases I saw if you'd used some of the JS example code I'd posted up in replies to your previous questions it would have been several times faster.

Basically in all the cases I have seen so far it's just being used as a 'magic fix' - adding "compiled" to functions that you think might be slow isn't a substitute for benchmarking and taking a more analytical approach. Instead it adds an opportunity for loads of potential bugs, is slower to upload, uses up more memory, and isn't debuggable.

Using compiled should really be a last resort IMO, when you've exhausted all other approaches to improving speed. There's a reason that none of the modules I've written for Espruino use it, and even when I include JS code inside the Espruino interpreter itself, it's kept as JS and isn't compiled.