rules_rust
JITWatch
Our great sponsors
rules_rust | JITWatch | |
---|---|---|
9 | 10 | |
610 | 3,015 | |
4.1% | 0.9% | |
9.6 | 6.7 | |
1 day ago | 28 days ago | |
Starlark | Java | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
rules_rust
-
NixOS: Declarative Builds and Deployments
The same reason Bazel builds avoid using Cargo when building Rust software, so I'll describe why Bazel would do this:
- Bazel wants to cache remote resources, like each respective crate's source files.
- Bazel then wants to build each crate in a sandbox, and cache the build artifacts
This is an established practice, and Nix wants to drive the build for the same reasons.
See:
- https://github.com/bazelbuild/rules_rust
- https://github.com/google/cargo-raze
-
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
To answer your question, I don't know if Soong or Bazel can reuse the files produced by an incremental Rust compilation. I tried searching the rules_rust repository and found some discussions, but nothing that clearly told me "Yes, this is supported".
-
When to Use Bazel?
Bazel doesn't allow targeting a lot of platforms (especially embedded) from Rust, even when the Rust ecosystem supports these targets. Something is off with its design if new work needs to be done for every platform that's already available behind an interface that's as consistent as what rustc gives.
What is supported needs to be inferred from this file, as far as I can tell: https://github.com/bazelbuild/rules_rust/blob/main/rust/plat...
-
Cpp-like build tools for Rust?
You might be overjoyed to learn that you can use a build tool that forces you to manually write out the dependencies between each file.
-
How to enable suggestions/autocomplete in VS Code?
I am using rules_rust and have the VS Code Bazel plugin installed, but I am still not getting autocomplete.
-
Blog Post: Fast Rust Builds
Other than that, the performance of both for builds should be determined exactly by the organization of code into separate crates and the rustc invocations. Bazel generally encourages smaller crates, but that's very subtle. There is at least 1 case I can think of where rustc is overfit to cargo, in a way that is not easily replicable by bazel, which is the metadata/rlib pipelining https://github.com/bazelbuild/rules_rust/issues/228
-
Modern C++ Won't Save Us (2019)
Rust integrates pretty seamlessly into Bazel projects via rules_rust (https://github.com/bazelbuild/rules_rust). The existing rules even allow for c calling rust and rust calling c. Example: https://github.com/bazelbuild/rules_rust/blob/main/examples/...
-
Why Zig When There Is Already C++ and Rust?
With any compiled language you can use the compiler and vendor your dependencies instead of using the language's conventional package manager. For example, nothing prevents skipping Cargo and building Rust directly with rustc the way Bazel does.
https://github.com/bazelbuild/rules_rust
JITWatch
-
It's 2023, so of course I'm learning Common Lisp
You can kind of do the same as DISASSEMBLE in Clojure.
There are some helper projects like https://github.com/Bronsa/tools.decompiler, and on the OpenJDK JitWatch (https://github.com/AdoptOpenJDK/jitwatch), other JVMs have similar tools as well.
It isn't as straightforward as in Lisp, but it is nonetheless doable.
-
How much is too much? 380+ lines of an AssertionUtil class Or Loggin classes in general.
As you have encapsulated the asserts inside methods, these will be called at runtime with the arguments evaluated (for example, creating that lambda). When assertions are disabled, the C1/C2 may inline the empty method call eventually, but I don't know whether it drops the lambda instantiation as well. You can use JITWatch to see what gets inlined. The general notion though is to not worry too much. Lazy log messages are a common pattern.
-
JIT x86 ia32
You can use jitwatch for this. To see the actual assembly code generated you will also need to use a debug build of the jvm.
-
SIMD accelerated sorting in Java – how it works and why it was 3x faster
If you use Oracle's own IDE, it will support it out of the box, as it already did on Sun's days.
Then there are other ways depending on which JVM implementation is used.
On OpenJDK's case you can load runtime plugin to do it
https://github.com/AdoptOpenJDK/jitwatch
- Equivalent of cppinsight for kotlin
-
Compiler Explorer - Java support
We use https://github.com/AdoptOpenJDK/jitwatch for this.
- How to Read Assembly Language
-
Why Zig When There Is Already C++ and Rust?
If you already know any JVM or .NET language, the first step would be to understand the full stack, you don't need C for that.
Many of us were doing systems programming with other languages before C went mainstream.
What you need to learn is computer architecture.
Getting back to JVM or .NET, you can get hold of JIT Watch, VS debug mode or play online in SharpLab.
Get to understand how some code gets translated into MSIL/JVM, and how those bytecodes end up being converted into machine code.
https://github.com/AdoptOpenJDK/jitwatch/wiki/Screenshots
https://sharplab.io/
Languages like F# and C# allow you to leave the high level comfort and also do most of the stuff you would be doing in C.
Or just pick D, which provides the same comfort and goes even further in low level capabilities.
Use them to write a toy compiler, userspace driver, talking to GPIO pins in a PI, manipulating B-Tree data stuctures directly from inodes, a TCP/IP userspace driver.
Not advocating not to learn Zig, do it still, the more languages one learns the better.
Only advocating what might be an easier transition path into learning about systems programming concepts.
-
JIT 101
You can enable a lot of debug information about how the compiler decides what to do with your code using feature flags like -XX:+UnlockDiagnosticVMOptions -XX:+PrintInlining. If you want to dive deeper into the world of the Hotspot JIT Compiler, have a look at JITWatch.
-
Is Java As Fast As C When It Comes To Stack
In what concerns HotSpot, one way would be JITWatch.
What are some alternatives?
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
JMH - "Trust no one, bench everything." - sbt plugin for JMH (Java Microbenchmark Harness)
cargo-chef - A cargo-subcommand to speed up Rust Docker builds using Docker layer caching.
SharpLab - .NET language playground
cargo-sweep - A cargo subcommand for cleaning up unused build files generated by Cargo
Sniffy - Sniffy - interactive profiler, testing and chaos engineering tool for Java
www.ziglang.org
jHiccup - jHiccup is a non-intrusive instrumentation tool that logs and records platform "hiccups" - including the JVM stalls that often happen when Java applications are executed and/or any OS or hardware platform noise that may cause the running application to not be continuously runnable.
wg-allocators - Home of the Allocators working group: Paving a path for a standard set of allocator traits to be used in collections!
LatencyUtils - Utilities for latency measurement and reporting
bazel-coverage-report-renderer - Haskell rules for Bazel.
quickperf - QuickPerf is a testing library for Java to quickly evaluate and improve some performance-related properties