-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test Report from OpenDAL #27
Comments
Trying to build Looking at the log reveals some interesting things. Currently, there are 2244 codegen panics in the build log. Those 2 groups total in 1568 panics(70%). Other issues cause much fewer errors, 676(~30%). While I am almost certain there are other issues which are not currently picked up, this suggests that a lot of progress can ReifyFnPointerThe issue with d2d4ca1 allows creation of function pointers (but functions with alternative calling conventions / marked with the #[track_caller] attribute don't work properly yet). 5946c83 adds the ability to call those function pointers. There are some function pointer related things that still need some consideration. For example, distinguishing between managed and unmanged function pointers has huge performance benefits, but could potentially introduce runtime issues if not done right. But even with those minor issues unresolved, calling/creating function pointers should work now, reducing the amount of codegen panics. DSTsThose also cause trouble in DSTs are a bit more tricky, since they require revamping some of the code handling fat pointers. The newest set of patches greatly improves support for DSTs, and a large chunk of them should now work, but there are still some issues. Due to Getting the address of a dynamically sized field of a DST currently should copy the address and metadata of the field, but this currently does not happen, creating fat pointers with garbage addresses/metadata, causing runtime issues. Once those issues get resolved, a large chunk of errors should disappear. Admittedly, those are probably the low-hanging fruit, but this should be a good step forward. MaturityThis is a small clarification about where the project is headed. Also, I would not say that the project will be close to being mature when it is capable of properly building OpenDAL. Mainly:
I know those are just nitpicky semantics (and I hope I don't come off as rude), but I am rather cautious when it comes to those things. I would like the project to be in a near-prefect state before calling it mature. I don't want to claim the project is more ready than it is - I would not want someone to assume it is fully working, only to surprise them with hidden issues. |
NOTE: This test report is for informational purposes only and does not suggest any immediate need for repair.
Following the instructions at #25, I attempted to use
rustc_codegen_clr
with opendal. OpenDAL is a REAL Rust crate that facilitates IO, networking, and asynchronous operations. If we successfully compile OpenDAL and integrate it with CLR,rustc_codegen_clr
will be nearing maturity.cargo test compile_test::opendal_test::cargo_release
Worth of mention:
The text was updated successfully, but these errors were encountered: