Add rust support for introspector about fuzz-introspector HOT 4 OPEN

This sounds great!

Let me go a bit more over this and assist with scoping out for Rust. See LanguageImplementation for details on how to add a new language.

Rust relies on LLVM/Clang? Do you know if regular LLVM LTO passes can run on Rust code? We may be able to use the existing LLVM frontend

from fuzz-introspector.

Let me go a bit more over this and assist with scoping out for Rust. See LanguageImplementation for details on how to add a new language.

Cool I missed that, I'll take a read over the next few days.

Rust relies on LLVM/Clang? Do you know if regular LLVM LTO passes can run on Rust code? We may be able to use the existing LLVM frontend

I've never tried this, and tbh I'm not really up to speed on how LTO passes work beyond them just being a plugin for the linker. But I did come across something that sounds like what you are mentioning, while looking at LTO with rust/c++. Reading over it a gain it looks somewhat promising but I'd have to a do a deeper dive.

from fuzz-introspector.

So after reading over that doc that you've mentioned, I had missed a couple of things in my original assesment. The only open question I have is, how we would implement the branch profiles section of the project wide yaml file. Evaluating control flow in rust is reasonably complex with things like;

• match statements
• macros
• "standard" control flow (if/else, loops etc.)

One approach would be to expand out each macro e.g. cargo expand path::to::module but that has other issues; like which line do you attribute the branch to in the non-expanded source code.

from fuzz-introspector.

In terms of control flow, then ideally because Rust is based on LLVM we could do the analysis directly on LLVM IR and use the logic from https://github.com/ossf/fuzz-introspector/tree/main/frontends/llvm to do all of the control-flow analysis -- I could take a look at this sometime in Feb I think.

from fuzz-introspector.