-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Revert #131669 due to ICEs #134064
Revert #131669 due to ICEs #134064
Conversation
Revert <rust-lang#131669> due to ICE reports: - <rust-lang#134059> (real-world) - <rust-lang#134060> (fuzzing) The changes can be re-landed with those cases addressed. This reverts commit 703bb98, reversing changes made to f415c07.
Mostly just to check that the lint impl doesn't ICE from an easy case.
@bors r+ |
@bors p=1 (revert PR) |
@bors rollup |
Revert rust-lang#131669 due to ICEs Revert [lint: change help for pointers to dyn types in FFI rust-lang#131669](rust-lang#131669) due to ICE reports: - <rust-lang#134059> (real-world) - <rust-lang#134060> (fuzzing) Closes rust-lang#134060. The revert criteria I used to assess whether to post this revert was: 1. It's not trivial to fix-forward. (1) The implementation itself is tricky due to `tcx.is_sized` query not being very trivial. (2) It will need more extensive test coverage for different ty kinds. 2. It is impacting real-world crates, i.e. rust-lang#134059. 3. `improper_ctypes_definitions` is a warn-by-default lint. This revert is without prejudice to relanding the changes. The changes can be re-landed with those cases addressed and stronger test coverage. A rough regression test corresponding to the fuzzed example reported in rust-lang#134060 is added to check that the revert worked, it is not sufficient for the lint test coverage when the lint improvements are to be relanded. Please feel free to improve the test in the reland. r? `@workingjubilee` (or compiler) cc `@niacdoial` (PR author)
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry |
@bors p=6 (interleaving between rollups) |
Revert rust-lang#131669 due to ICEs Revert [lint: change help for pointers to dyn types in FFI rust-lang#131669](rust-lang#131669) due to ICE reports: - <rust-lang#134059> (real-world) - <rust-lang#134060> (fuzzing) Closes rust-lang#134060. The revert criteria I used to assess whether to post this revert was: 1. It's not trivial to fix-forward. (1) The implementation itself is tricky due to `tcx.is_sized` query not being very trivial. (2) It will need more extensive test coverage for different ty kinds. 2. It is impacting real-world crates, i.e. rust-lang#134059. 3. `improper_ctypes_definitions` is a warn-by-default lint. This revert is without prejudice to relanding the changes. The changes can be re-landed with those cases addressed and stronger test coverage. A rough regression test corresponding to the fuzzed example reported in rust-lang#134060 is added to check that the revert worked, it is not sufficient for the lint test coverage when the lint improvements are to be relanded. Please feel free to improve the test in the reland. r? `@workingjubilee` (or compiler) cc `@niacdoial` (PR author)
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
No idea what this is, npm temporarily unavailable...? @bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (a224f38): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -1.4%, secondary -3.6%)This 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: 767.969s -> 767.262s (-0.09%) |
on one hand, I am disappointed I didn't anticipate this. on the other hand, I am honestly not surprised the improper ctypes lint is virtually unfixable by partial measures. |
I'll probably get a v2 of those changes soon-ish, but I'm currently creating a test that goes through as many ty_kinds as possible, both directly and through indirections |
Revert lint: change help for pointers to dyn types in FFI #131669 due to ICE reports:
we shouldn't be trying to determine if this is unsized for a reason or another
#134060 (fuzzing)Closes #134060.
The revert criteria I used to assess whether to post this revert was:
tcx.is_sized
query not being very trivial. (2) It will need more extensive test coverage for different ty kinds.improper_ctypes_definitions
is a warn-by-default lint.This revert is without prejudice to relanding the changes. The changes can be re-landed with those cases addressed and stronger test coverage.
A rough regression test corresponding to the fuzzed example reported in #134060 is added to check that the revert worked, it is not sufficient for the lint test coverage when the lint improvements are to be relanded. Please feel free to improve the test in the reland.
r? @workingjubilee (or compiler)
cc @niacdoial (PR author)