Alex, this is not the point. One day LLVM will inject trojan code, because US government, by law, tells them to do so!
With Cloud Act and Patriot Act US government can advise any US company or organisation to implement evil code. Can you do a full code review at every update coming for LLVM? I can't! Nobody can! 2.5 million lines is out of anybody's reach! 100 bytes more in a binary can make a *huge difference* from security oint of view. Do you always know, why LLVM suddenly is generating bigger code? Can be everything. E.g. this: https://gist.github.com/DGivney/5917914 TCC, i can review any time .... code is so tiny. Well ok, TCC binary code is not as highly optimized in terms of speed, but AMD processor microcode does compensate that. Differences to GCC -O3 or LLVM - in practice - have become negligible. TCC always is fast enough. And i repeat: Stop using US software stacks! Best regards, Guido Stepken Am Sonntag, 19. April 2020 schrieb Alexander Burger <a...@software-lab.de>: > Hi Guido, > >> Look at LLVM generated bloat and compare with Nokolisp. Less is more!!! In >> terms of size as well as of security. > > True, LLVM is huge (as is gcc, and other equivalent systems), but this is > irrelevant because I *use* it only to translate *my* code. > > The generated pil21 'picolisp' binary is only a few percent larger than the > assembly version of pil64. > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
