-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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: enable unpacked-lto
tests
#120264
test: enable unpacked-lto
tests
#120264
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
r? michaelwoerister I found this while addressing #118518 |
This comment has been minimized.
This comment has been minimized.
863b6f4
to
d5811bb
Compare
They seems to create `.o` files, which are actually llvm bitcode.
d5811bb
to
39e8512
Compare
.o
unpacked-lto
tests
Thanks, @weihanglo! |
☀️ Test successful - checks-actions |
Finished benchmarking commit (6db96de): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. 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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 651.828s -> 651.67s (-0.02%) |
This enables the correct
unpacked-lto
tests.Not sure whether
.o
should be removed.They are bitcode for linker-plugin-lto, though there might be some
.o
for#[no_builtins]
?