"error: linking with cc failed: exit code: 1" regression in release build with const generics
#73298
Labels
A-const-generics
Area: const generics (parameters and arguments)
A-lazy-normalization
Area: Lazy normalization (tracking issue: #60471)
A-linkage
Area: linking into static, shared libraries and binaries
C-bug
Category: This is a bug.
F-generic_const_exprs
`#![feature(generic_const_exprs)]`
requires-nightly
This issue requires a nightly compiler in some way.
Comments
jonas-schievink
added
A-const-generics
lcnr
added
the
E-needs-mcve
|
I reduced it.
#![feature(const_generics)]
use std::convert::AsMut;
use std::default::Default;
trait Foo: Sized {
type Baz: Default + AsMut<[u8]>;
fn bar() {
Self::Baz::default().as_mut();
}
}
impl Foo for () {
type Baz = [u8; 1 * 1];
//type Baz = [u8; 1];
}
fn main() {
<() as Foo>::bar();
}In both release and debug, it yields approximate the same error as before on: But compiles successfully on: |
varkor
removed
the
E-needs-mcve
|
This fails with |
|
This appears to be working now. I'll add a test. |
varkor
added
the
E-needs-test
varkor
added a commit
to varkor/rust
that referenced
this issue
Oct 21, 2020
Dylan-DPC-zz
pushed a commit
to Dylan-DPC-zz/rust
that referenced
this issue
Oct 22, 2020
Add regression test for rust-lang#73298 Closes rust-lang#73298. r? @lcnr
varkor
added
E-needs-mcve
|
Note that on latest nightly, I am still encountering this issue. (Any time I use the Error: |
|
Sorry to keep bumping. I continue to encounter this issue when I attempt to use CodeErrorrustc --version --verbose |
|
Reliably reproduces for me using latest code. @rustbot modify labels: -E-needs-mcve +E-needs-test |
rustbot
added
E-needs-test
|
I encountered a different trigger for what I am guessing is the same underlying bug. Error message is ~identical. To work around, do one of:
#![feature(generic_const_exprs)]
use std::marker::PhantomData;
pub trait Foo {
type Quiz;
fn bar() -> Self::Quiz;
}
#[derive(Clone, Debug)]
struct Corge<const K: usize> {}
impl<const K: usize> Foo for Corge<K>
where
[(); K + 0]:,
{
type Quiz = [u16; K + 0];
fn bar() -> Self::Quiz {
[0u16; K + 0]
}
}
struct Gork<R: Foo> {
t: PhantomData<R>,
}
impl<R: Foo> Gork<R> {
fn baz(self) -> Vec<R::Quiz> {
vec![R::bar()]
}
//fn baz(self) -> [R::Quiz; 1] {
// [R::bar()]
//}
}
fn main() {
let x = Gork::<Corge<3>> { t: PhantomData::default() };
let _ = x.baz();
}rustc --version --verbose: |
|
Different trigger. Allocating with #![feature(generic_const_exprs)]
use std::marker::PhantomData;
use std::mem::MaybeUninit;
pub trait Foo {
type Quiz;
fn bar() -> Self::Quiz;
}
#[derive(Clone, Debug)]
struct Corge<const K: usize> {}
impl<const K: usize> Foo for Corge<K>
where
[(); K + 0]:,
{
type Quiz = [u8; K + 0];
fn bar() -> Self::Quiz {
[0u8; K + 0]
}
}
struct Gork<R: Foo> {
t: PhantomData<R>,
}
impl<R: Foo> Gork<R>
where
R::Quiz: Copy,
{
fn baz() {
unsafe { MaybeUninit::<[R::Quiz; 1]>::uninit().assume_init() };
//[R::bar(); 1];
}
}
fn main() {
Gork::<Corge<3>>::baz()
} |
lcnr
removed
the
E-needs-test
This comment was marked as off-topic.
This comment was marked as off-topic.
tmiasko
added
the
A-lazy-normalization
BoxyUwU
added
F-generic_const_exprs
#![feature(generic_const_exprs)]
use std::convert::AsMut;
use std::default::Default;
trait Foo: Sized {
type Baz: Default + AsMut<[u8]>;
fn bar() {
Self::Baz::default().as_mut();
}
}
impl Foo for () {
type Baz = [u8; 1 * 1];
//type Baz = [u8; 1];
}
fn main() {
<() as Foo>::bar();
}still causes a linker error but passes with I assume we end up mangling an unevaluated constant somewhere with |
This was referenced Aug 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Const generics and release mode and Hc128Rng::seed_from_u64 and rustc 1.45.0-nightly (4bd32c9 2020-05-29) or later cause cc linking error.
To avoid the error, do any of:
#![feature(const_generics)]Hc128Rng::seed_from_u64(42)lineI'm guessing that Hc128Rng::seed_from_u64 is not the only thing that will trigger this, but I have not been able to find any other examples.
Source code
Dependancies
Error:
Version
The text was updated successfully, but these errors were encountered: