llvm-propeller
cargo-xtask
Our great sponsors
llvm-propeller | cargo-xtask | |
---|---|---|
6 | 26 | |
332 | 736 | |
0.9% | - | |
0.0 | 3.0 | |
7 months ago | 10 months ago | |
Shell | ||
Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
llvm-propeller
-
Speed of Rust vs. C
> In theory, Rust allows even better optimizations than C thanks to stricter immutability and aliasing rules, but in practice this doesn't happen yet. Optimizations beyond what C does are a work-in-progress in LLVM, so Rust still hasn't reached its full potential.
Really glad to see this mentioned, I search for it in every post like this.
LLVM should follow now that the mutable noalias bugs appear to be fixed. Remember when it was a meme that every time it gets enabled in rustc, it has to be disabled again in the next .1 release? It's been left enabled for years.
The biggest challenge here is that most people aren't looking for optimizations beyond what they were already getting with C. Like when Google was switching from GCC to Clang, they'd pick apart the asm and report bugs for Clang and LLVM to converge on GCC. That was a big part of why the performance gap closed over the years. But that was closing a gap, not speculatively overtaking them.
Then there's a whole other angle; we now know just how much machine code layout can affect real-world performance, in most cases much more than aliasing rules, but we still haven't made it a seamless part of our build tooling. PGO is now fairly easy, but BOLT is still a pain to integrate for no clear reason, and PROPELLER has been left in an embarrassing state where even its own PDF link is broken [1]. (To be fair, it may not be Google's highest priority at this time.)
[1] https://github.com/google/llvm-propeller
-
LLVM Now Using PGO for Its x86_64 Windows Release Binaries: ~22% Faster Builds
Propeller does this: https://github.com/google/llvm-propeller/blob/main/Docs/Opti...
-
Speeding up the Rust compiler without changing its code
Looks like they deleted their branches. The latest commit I could find (via pr#11) seems to have the PDF. https://github.com/google/llvm-propeller/tree/424c3b885e60d8ff9446b16df39d84fbf6596aec
-
Performance variation when moving functions between files
Google also wrote PROPELLER which claims to be even better than BOLT, but I don't know why they didn't drive it all the way to upstream. BOLT got merged after PROPELLER claimed to obsolete it. I can only assume there was a lot more to the story than anyone is saying in public.
- AV1 related job offer :O
cargo-xtask
-
🏃♂️ Use task.go for your Go project scripts
💡 Inspired by matklad/cargo-xtask and based on 🏃♂️ Write your Rust project scripts in task.rs from the Rust ecosystem.
-
clap_completion help requested
Using a cargo-xtask task to generate them as a manual step (inlyne currently does this)
- Cargo xtask: extend cargo with custom commands written in Rust
-
Including a cargo command as a dev dependency
As someone else said just is good for that job, or you could implement an xtask helper for these things and setup a suitable development environment with that: https://github.com/matklad/cargo-xtask/
- Cargo xtask: extend stock, stable cargo with custom commands written in Rust
-
Going beyond build.rs: introducing cargo-px
Well tools like cornucopia, prisma-rust-client, protoc-gen-tonic, they don't generate in build.rs, but instead provide either a cli to be called ahead of time, or provide a library that can be called by your own binary (which should generally follow the xtask pattern)
- Hey Rustaceans! Got a question? Ask here (17/2023)!
-
Best way to include a utility command for my crate?
If I understand, this is a tool for when working on the project itself? Akin to a helper script? You could go the cargo install route as already pointed out but there is also the xtask convention.
-
We have getrandom at home
For simple cli apps for internal use, such as cargo-xtasks, I prefer pico_args due to its fast compile times.
-
Rust for Web Development | An Honest Evaluation
For developer-oriented stuff, there's tools like xshell and cargo-xtask. For operator tasks that need to run in a deployed environment, it's not usually a big lift to add CLI subcommands to your binary. It's certainly more boilerplate and inertia than doing stuff in a live REPL, though, and sometimes difficult to recommend for truly one-off situations.
What are some alternatives?
BOLT - Binary Optimization and Layout Tool - A linux command-line utility used for optimizing performance of binaries
just - 🤖 Just a command runner
coz - Coz: Causal Profiling
cargo-make - Rust task runner and build tool.
cargo-pgo - Cargo subcommand for optimizing Rust binaries/libraries with PGO and BOLT.
bors-ng - 👁 A merge bot for GitHub Pull Requests
rust - Empowering everyone to build reliable and efficient software.
waihona - Rust crate for performing cloud storage CRUD actions across major cloud providers e.g aws
fzf - :cherry_blossom: A command-line fuzzy finder
zoxide - A smarter cd command. Supports all major shells.
config-rs - ⚙️ Layered configuration system for Rust applications (with strong support for 12-factor applications).
neuronika - Tensors and dynamic neural networks in pure Rust.