-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Migrate 8 very similar FFI run-make
tests to rmake
#127491
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
The run-make-support library was changed cc @jieyouxu This PR modifies cc @jieyouxu |
This comment has been minimized.
This comment has been minimized.
Yikes. According to some quick research, this has something to do with the AR command... I've seen a suggestion to use |
|
I don't mind switching back from |
85fd830
to
89c1b4a
Compare
This comment has been minimized.
This comment has been minimized.
5cb5fc3
to
cb6f6a9
Compare
cb6f6a9
to
69006f2
Compare
☔ The latest upstream changes (presumably #127760) made this pull request unmergeable. Please resolve the merge conflicts. |
69006f2
to
c68d25b
Compare
@rustbot review |
@bors r+ rollup=iffy (c builds) |
Rollup of 7 pull requests Successful merges: - rust-lang#127491 (Migrate 8 very similar FFI `run-make` tests to rmake) - rust-lang#127687 (Const-to-pattern-to-MIR cleanup) - rust-lang#127822 (Migrate `issue-85401-static-mir`, `missing-crate-dependency` and `unstable-flag-required` `run-make` tests to rmake) - rust-lang#127842 (Remove `TrailingToken`.) - rust-lang#127864 (cleanup: remove support for 3DNow! cpu features) - rust-lang#127899 (Mark myself as on leave) - rust-lang#127901 (Add missing GHA group for building `llvm-bitcode-linker`) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#127491 - Oneirical:bulletproof-test, r=jieyouxu Migrate 8 very similar FFI `run-make` tests to rmake Part of rust-lang#121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). There are some more of these, but while the code is almost always the same, I want to keep the number reasonable so my doc comments can be inspected for potential inaccuracies. Tell me if 8 is too much, I can cut this down. For the tracking issue: - issue-25581 - extern-fn-with-extern-types - extern-fn-struct-passing-abi - longjmp-across-rust - static-extern-type - extern-fn-explicit-align - extern-fn-with-packed-struct - extern-fn-mangle
Part of #121876 and the associated Google Summer of Code project.
There are some more of these, but while the code is almost always the same, I want to keep the number reasonable so my doc comments can be inspected for potential inaccuracies. Tell me if 8 is too much, I can cut this down.
For the tracking issue: