LLVM Tutorial #1: Introduction

Показать описание

Toby Ho

Рекомендации по теме

Комментарии

nice the first time i understand something about llvm, thanks toby!

gharbimohamed

Thank you for your presentation. In 2011, I wrote a compiler that uses a slightly different work flow. It might not be able to make use of LLVM because it is quite a bit more advanced. It uses full Unicode source code, it has extensive parallel features and it supports a new hardware architecture I call ϕEngine. There are other features that are not supported by LLVM. Standard programming languages are very scalar in their nature.

Tapajara

LLVM used to mean Low Level Virutal Machine, but since the concept has far outgrown that meaning, they decided to no longer treat the term LLVM as an acronym.

TheHighlander

I read elsewhere that LLVM stands for "Low-Level Virtual Machine." I suspected that was what it stands for.

richardmaduka

LLVM stands for “Lower Level Virtual Machine”.

wanderingknight

would like to know the name of the software that draws pictures on the computer screen, thank you very much！😁

zcd-cb

Very helpful, but the video was a bit hard to watch because of how laggy it is.

oglothenerd

Hi. This is really a great presentation especially for the people like me who just got interested in how low level languages interacting with cpu and all that. One question. The reason llvm came out reminds me about the jvm, though I know it's far more high level virtual machine for cross-os build for java, but the logic of purpose seems similar. Python also uses its own vm to run their code no matter the environment it runs on. Those high level language are known for relatively slow performance because of those vm layer at runtime. Do you think Could it be also true for llvm in some way? "Run your code no matter what the cpu architecture is as long as it goes with llvm" sounds cool but it anyways adds another layer between machinary code and human readable code. Or maybe I misunderstood something?

bordertone_