Skip to content
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

ICE in unsized fn params: tried to statically allocate unsized place #67981

Open
DutchGhost opened this issue Jan 7, 2020 · 5 comments
Open
Labels
A-codegen Area: Code generation C-bug Category: This is a bug. F-unsized_fn_params `#![feature(unsized_fn_params)]` requires-nightly This issue requires a nightly compiler in some way. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@DutchGhost
Copy link
Contributor

DutchGhost commented Jan 7, 2020

The following ICE's in nightly:

#![feature(unsized_fn_params)]

fn main() {
    let f: fn([u8]) = |_| {};
    
    let slice: Box<[u8]> = Box::new([1; 8]);
    
    f(*slice);
}
Backtrace:
 Compiling playground v0.0.1 (/playground)
thread 'rustc' panicked at 'tried to statically allocate unsized place', src/librustc_codegen_ssa/mir/place.rs:55:9
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:77
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1057
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1426
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:195
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:215
  10: rustc_driver::report_ice
  11: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:476
  12: std::panicking::begin_panic
  13: rustc_codegen_ssa::mir::place::PlaceRef<V>::alloca
  14: <core::iter::adapters::Map<I,F> as core::iter::traits::iterator::Iterator>::fold
  15: <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T,I>>::from_iter
  16: rustc_codegen_ssa::mir::codegen_mir
  17: <rustc::mir::mono::MonoItem as rustc_codegen_ssa::mono_item::MonoItemExt>::define
  18: rustc_codegen_llvm::base::compile_codegen_unit::module_codegen
  19: rustc::dep_graph::graph::DepGraph::with_task
  20: rustc_codegen_llvm::base::compile_codegen_unit
  21: rustc_codegen_ssa::base::codegen_crate
  22: <rustc_codegen_llvm::LlvmCodegenBackend as rustc_codegen_utils::codegen_backend::CodegenBackend>::codegen_crate
  23: rustc_interface::passes::start_codegen::{{closure}}
  24: rustc::util::common::time
  25: rustc_interface::passes::start_codegen
  26: rustc::ty::context::tls::enter_global
  27: rustc_interface::queries::Queries::ongoing_codegen
  28: rustc_interface::interface::run_compiler_in_existing_thread_pool
  29: scoped_tls::ScopedKey<T>::set
  30: syntax::with_globals
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: rustc 1.42.0-nightly (da3629b05 2019-12-29) running on x86_64-unknown-linux-gnu

note: compiler flags: -C codegen-units=1 -C debuginfo=2 --crate-type bin

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
end of query stack
error: could not compile `playground`.
@DutchGhost DutchGhost changed the title ICE in unsized locals ICE in unsized locals: tried to statically allocate unsized place Jan 7, 2020
@jonas-schievink jonas-schievink added C-bug Category: This is a bug. F-unsized_locals `#![feature(unsized_locals)]` I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ requires-nightly This issue requires a nightly compiler in some way. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. A-codegen Area: Code generation labels Jan 7, 2020
@rust-lang-glacier-bot rust-lang-glacier-bot added the glacier ICE tracked in rust-lang/glacier. label Jan 15, 2020
@DutchGhost
Copy link
Contributor Author

update,

#![feature(unsized_locals, raw_ref_op)]

fn main() {
    let f: fn([u8]) = |_| {};
}

seems already enough to cause the ICE

@JohnTitor JohnTitor added F-unsized_fn_params `#![feature(unsized_fn_params)]` and removed F-unsized_locals `#![feature(unsized_locals)]` labels Oct 29, 2020
@JohnTitor JohnTitor changed the title ICE in unsized locals: tried to statically allocate unsized place ICE in unsized fn params: tried to statically allocate unsized place Oct 29, 2020
@JohnTitor
Copy link
Member

Triage: This now occurs on unsized_fn_params.

Jules-Bertholet added a commit to Jules-Bertholet/rust that referenced this issue Apr 26, 2023
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this issue Apr 27, 2023
…ywiser

Nicer ICE for rust-lang#67981

Provides a slightly nicer ICE for rust-lang#67981, documenting the problem. A proper fix will be necessary before `#![feature(unsized_fn_params)]` can be stabilized.

The problem is that the design of the `"rust-call"` ABI is fundamentally not compatible with `unsized_fn_params`. `"rust-call"` functions need to collect their arguments into a tuple, but if the arguments are not `Sized`, said tuple is potentially not even a valid type—and if it is, it requires `alloca` to create.

`@rustbot` label +A-abi +A-codegen +F-unboxed_closures +F-unsized_fn_params
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this issue Apr 27, 2023
…ywiser

Nicer ICE for rust-lang#67981

Provides a slightly nicer ICE for rust-lang#67981, documenting the problem. A proper fix will be necessary before `#![feature(unsized_fn_params)]` can be stabilized.

The problem is that the design of the `"rust-call"` ABI is fundamentally not compatible with `unsized_fn_params`. `"rust-call"` functions need to collect their arguments into a tuple, but if the arguments are not `Sized`, said tuple is potentially not even a valid type—and if it is, it requires `alloca` to create.

``@rustbot`` label +A-abi +A-codegen +F-unboxed_closures +F-unsized_fn_params
bors added a commit to rust-lang-ci/rust that referenced this issue Apr 27, 2023
…iaskrgr

Rollup of 7 pull requests

Successful merges:

 - rust-lang#110426 (docs(style): add more let-else examples)
 - rust-lang#110804 (Remove repeated definite articles)
 - rust-lang#110814 (Sprinkle some `#[inline]` in `rustc_data_structures::tagged_ptr`)
 - rust-lang#110816 (Migrate `rustc_passes` to translatable diagnostics)
 - rust-lang#110864 (`IntoFuture::into_future` is no longer unstable)
 - rust-lang#110866 (Make `method-not-found-generic-arg-elision.rs` error message not path dependent)
 - rust-lang#110872 (Nicer ICE for rust-lang#67981)

Failed merges:

r? `@ghost`
`@rustbot` modify labels: rollup
@Jules-Bertholet
Copy link
Contributor

With #110872, this now has a slightly nicer ICE.

The issue is that unsized_fn_params is incompatible with the "rust-call" ABI that the Fn traits use. "rust-call" tries to collect all its arguments into a tuple, but when the arguments are unsized, that's not possible—the tuple might not even be a valid type! This problem can't be fixed without some new design, like explicit &move or variadics.

Jules-Bertholet added a commit to Jules-Bertholet/rust that referenced this issue May 23, 2023
The `rust-call` ABI isn't compatible with
`#![feature(unsized_fn_params)]`, so trying to use that feature with
closures leads to an ICE (rust-lang#67981). This turns that ICE into a
type-check error.
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this issue May 24, 2023
…compiler-errors

Always require closure parameters to be `Sized`

The `rust-call` ABI isn't compatible with `#![feature(unsized_fn_params)]`, so trying to use that feature with closures leads to an ICE (rust-lang#67981). This turns that ICE into a type-check error.

`@rustbot` label A-closures F-unsized_fn_params
@Jules-Bertholet
Copy link
Contributor

With #111864, this is now an error instead of an ICE.

@rustbot label -I-ICE

@rustbot rustbot removed the I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ label May 24, 2023
@JohnTitor JohnTitor added E-needs-test Call for participation: An issue has been fixed and does not reproduce, but no test has been added. and removed E-needs-test Call for participation: An issue has been fixed and does not reproduce, but no test has been added. glacier ICE tracked in rust-lang/glacier. labels Jun 4, 2023
@rust-lang-glacier-bot rust-lang-glacier-bot added the glacier ICE tracked in rust-lang/glacier. label Jun 4, 2023
@matthiaskrgr matthiaskrgr added the E-needs-test Call for participation: An issue has been fixed and does not reproduce, but no test has been added. label Jun 14, 2023
@JohnTitor
Copy link
Member

#111864 added a relevant test, dropping E-needs-test cc @matthiaskrgr

@JohnTitor JohnTitor removed E-needs-test Call for participation: An issue has been fixed and does not reproduce, but no test has been added. glacier ICE tracked in rust-lang/glacier. labels Jun 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-codegen Area: Code generation C-bug Category: This is a bug. F-unsized_fn_params `#![feature(unsized_fn_params)]` requires-nightly This issue requires a nightly compiler in some way. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

7 participants