ili9341-rs VS cargo-asm

[package] name = "experiment" version = "0.23.0" authors = ["garse"] edition = "2018" categories = ["embedded", "hardware-support"] keywords = ["embedded", "svc", "idf", "esp-idf", "esp32"] description = "A demo binary crate for the ESP32 and ESP-IDF, which connects to WiFi, Ethernet, drives a small HTTP server and draws on a LED screen" repository = "https://github.com/ivmarkov/rust-esp32-std-demo" license = "MIT OR Apache-2.0" readme = "README.md" [patch.crates-io] smol = { git = "https://github.com/esp-rs-compat/smol" } polling = { git = "https://github.com/esp-rs-compat/polling" } socket2 = { git = "https://github.com/esp-rs-compat/socket2" } getrandom = { version = "0.2", git = "https://github.com/esp-rs-compat/getrandom.git" } #getrandom1 = { version = "0.1", git = "https://github.com/esp-rs-compat/getrandom.git", package = "getrandom", branch = "0.1" } [profile.release] opt-level = "s" [profile.dev] debug = true # Symbols are nice and they don't increase the size on Flash opt-level = "z" [features] default = ["experimental"] # Enable this feature for the build to use ESP-IDF native tooling instead of PlatformIO under the hood native = ["esp-idf-sys/native"] # Enable this feature if you are building for QEMU qemu = [] # Enable this feature in case you have a Kaluga board and would like to see a LED screen demo kaluga = [] # Enable this feature in case you have a TTGO board and would like to see a LED screen demo ttgo = [] # Enable this feature in case you have an ESP32S3-USB-OTG board and would like to see a LED screen demo heltec = [] # Enable this feature in case you have a generic SSD1306 Display connected via SPI to pins 3, 4, 5, 16, 18, 23 (SPI3) of your board ssd1306g_spi = [] # Enable this feature in case you have a generic SSD1306 screen connected to pins 14, 22 and 21 of your board ssd1306g = [] esp32s3_usb_otg = [] # Enable this feature in case you have an RMII IP101 Ethernet adapter ip101 = [] # Enable this feature in case you have an SPI W5500 Ethernet adapter w5500 = [] # Enable this feature in case you have a Waveshare board and 4.2" e-paper waveshare_epd = [] experimental = ["esp-idf-svc/experimental", "esp-idf-hal/experimental", "embedded-svc/experimental"] [dependencies] anyhow = {version = "1", features = ["backtrace"]} log = "0.4" url = "2" esp-idf-sys = { version = "0.30.6", features = ["binstart"] } esp-idf-svc = "0.37.2" esp-idf-hal = "0.33.1" embedded-svc = "0.17.2" embedded-hal = "0.2" embedded-graphics = "0.7" display-interface = "0.4" display-interface-spi = "0.4" st7789 = "0.6" ili9341 = { version = "0.5", git = "https://github.com/yuri91/ili9341-rs" } ssd1306 = "0.7" epd-waveshare = "0.5.0" smol = "1.2" rand = "*" [build-dependencies] embuild = "0.28" anyhow = "1"

ili9341 = { git = "https://github.com/yuri91/ili9341-rs.git", branch = "master", features=["graphics"] } embedded-hal = "0.2.3" embedded-graphics="0.7.1" display-interface-spi = "0.4.1" heapless = "0.7.7" profont = "0.5.0"

cargo asm might be useful here (if you can't use godbolt).

They should be inlined in release mode. You'd have to verify by checking the assembly, though, which could be done directly in the Rust playground or with a tool like cargo-asm.

You can use cargo asm - not sure if you can integrate it with VSCode, but even from a terminal it's a pretty convenient tool.

There's probably a built-in one somewhere, but I suspect it'd be easier just to install https://github.com/gnzlbg/cargo-asm

I don't know if there's a way to do a side by side comparison but cargo-asm uses the source mapping information from rustc to annotate chunks of assembly with it's respective rust code, though it's an imperfect process.

After that you would need some tools to help figure out how to achieve improvements. That will depend on your system and personal preferences. As the other commenter suggested, perf is a good choice on linux. I personally like to look at the generated assembly, using either cargo asm, godbolt, or just rust playground.

Doesn't this already exist? https://github.com/gnzlbg/cargo-asm

From the flamegraph, we knew which function was taking the majority of the time, which we briefly described above. We started by looking at the assembly code it generated to see if there were any opportunities to make it faster. We did this with cargo-asm.

You're best bet at the moment is probably using cargo-asm to inspect the function assembly to see when it is performing the correct TCO.