2019 LLVM Developers’ Meeting: J. Paquette & F. Hahn “Getting Started With LLVM: Basics”

[@bhagyalakshmi1053]

I32 is a 32bit,i64 is a 64bit,aarch files is ( zip code colr add, copy -past is a massage sund 👍🤝) thank you this apachecte

[@bhagyalakshmi1053]

Nice explain 🤝

[@haizhushao9640]

Hi, Could you share the slides, thank you.

[@rabingaire]

at 16:10 use is before def (for bb.1 and bb.2), few slides back he said uses should be reachable from def I am confused since these are basic blocks are they defined already before entry starts executing?

[@pervognsen_bitwise]

The constraint is that a def should dominate all its uses, i.e. every path from the entry point to a use must pass through the def (for phi you have to define it a little more carefully). It's not enough that a use should be reachable from a def since there could be alternate paths to that use which bypass the def. Anyway, basic blocks/labels aren't run-time values and so don't really have defs and uses in this sense. What he's talking about at 16:10 is just a convenient way of reusing the use/def tracking. I can see how it could be confusing.

[@rabingaire]

Bitwise thank you for the response, I was confused with this, It feels great to know that it was an analogy to explain things

[@diegonayalazo]

Thanks

[@bhagyalakshmi1053]

Plugins and sessions never to explaining