2023 EuroLLVM - Tutorial: A whirlwind tour of the LLVM optimizer

[@abuyoyo31]

I have been waiting for a talk exactly like this. Thank you!

[@AndreyBokhanko-c9y]

A really useful and easy-to-follow talk! Well done!!

[@shikharjain3536]

Thanke a lot for this exact,to the point seminar on opt

[@miladhakimi3495]

Amazing talk. Thank you!

[@zkindle3544]

OMG, really thanks. Lucky see this viedo.

[@leonid998]

Yes, the lack of de-esser is obvious, but not critical.

[@about2mount]

Very nice talk and presentation, however I cannot wrap my head around a 45 gigabyte LLVM Library when a normal Interpreter language only requires about 100 mb of package space. That is an absurdly large program just to do what Python is doing at far less cost and without wearing your machine out each time it runs. The wear on switching alone with a program that large does damage to a machine allot faster than normal operation. So really what good is having LLVM when using it and your Computer has to be replaced every five months? You guys are going backwards not forwards.

[@peterchou5370]

I'm sorry what? LLVM doesn't only contain the optimization tool it is collection of compiler tools some which you probably don't even need. The last time I compiled clang its only 120mb.

[@poyaochang3122]

You’re most likely building a debug build, worse debug build without splitting DWARF. Releasing LLVM requires you change a few CMake options.