-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Add test for Apple's -weak_framework
linker argument
#118644
Conversation
r? @b-naber (rustbot has picked a reviewer for you, use r? to override) |
ba0a077
to
c1718e3
Compare
I guess a test that runs |
Not your reviewer, but I added tests like that for deployment targets so I don't see why not. |
c1718e3
to
8442f62
Compare
I've added such tests now, thanks for the input |
8442f62
to
d63d1a1
Compare
@bors r+ rollup |
…=b-naber Add test for Apple's `-weak_framework` linker argument The [`-weak_framework`](https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/WeakLinking.html) linker argument can sometimes be useful to reduce startup times, and to link newer frameworks while still having older deployment targets. So I made a test to ensure that it continues to work. Discussed in rust-lang#99427.
…iaskrgr Rollup of 3 pull requests Successful merges: - rust-lang#118644 (Add test for Apple's `-weak_framework` linker argument) - rust-lang#118828 (Remove dead codes in rustc_codegen_gcc) - rust-lang#119001 (rustdoc-search: remove parallel searchWords array) r? `@ghost` `@rustbot` modify labels: rollup
…=b-naber Add test for Apple's `-weak_framework` linker argument The [`-weak_framework`](https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/WeakLinking.html) linker argument can sometimes be useful to reduce startup times, and to link newer frameworks while still having older deployment targets. So I made a test to ensure that it continues to work. Discussed in rust-lang#99427.
…llaumeGomez Rollup of 5 pull requests Successful merges: - rust-lang#118644 (Add test for Apple's `-weak_framework` linker argument) - rust-lang#118828 (Remove dead codes in rustc_codegen_gcc) - rust-lang#118830 (Add support for `--env` on `tracked_env::var`) - rust-lang#119001 (rustdoc-search: remove parallel searchWords array) - rust-lang#119020 (remove `hex` dependency in bootstrap) r? `@ghost` `@rustbot` modify labels: rollup
I think it failed in #119027. |
…-naber Add test for Apple's `-weak_framework` linker argument The [`-weak_framework`](https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/WeakLinking.html) linker argument can sometimes be useful to reduce startup times, and to link newer frameworks while still having older deployment targets. So I made a test to ensure that it continues to work. Discussed in rust-lang#99427.
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
…ompiler-errors Add test for Apple's `-weak_framework` linker argument The [`-weak_framework`](https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/WeakLinking.html) linker argument can sometimes be useful to reduce startup times, and to link newer frameworks while still having older deployment targets. So I made a test to ensure that it continues to work. Discussed in rust-lang#99427.
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
47cab49
to
440fce1
Compare
The test, as I'd written it before, replaced the string based on the architecture name |
@bors r+ |
@@ -0,0 +1,23 @@ | |||
# only-macos |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Since this seems like a new run-make
test) Does this test need to be written in Makefile? Can it be written in rmake.rs
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It probably could - didn't know about rmake.rs
, I think I made this PR before that was available
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, the timing was a bit unfortunate, but that's okay, we added a tidy check now
☀️ Test successful - checks-actions |
Finished benchmarking commit (47ecded): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 671.136s -> 669.555s (-0.24%) |
This test was introduced in rust-lang#118644, but was over-specified in that it assumed the path of the linker was always `cc`.
…st, r=fmease Relax framework linking test This test was introduced by myself in rust-lang#118644, but was over-specified in that it assumed the path of the linker was always `cc`, which [causes a test failure for Chromium](https://issues.chromium.org/issues/332562251).
Rollup merge of rust-lang#123410 - madsmtm:relax-framework-linking-test, r=fmease Relax framework linking test This test was introduced by myself in rust-lang#118644, but was over-specified in that it assumed the path of the linker was always `cc`, which [causes a test failure for Chromium](https://issues.chromium.org/issues/332562251).
The
-weak_framework
linker argument can sometimes be useful to reduce startup times, and to link newer frameworks while still having older deployment targets.So I made a test to ensure that it continues to work.
Discussed in #99427.