gccrs icon indicating copy to clipboard operation
gccrs copied to clipboard

GCC Front-End for Rust

Results 608 gccrs issues
Sort by recently updated
recently updated
newest added

gcc/rust/ChangeLog: * backend/rust-compile-expr.cc (lvalue_p): Created a function that checks the lvalue. (CompileExpr::visit): Modified the function to check the lvalue using the above mentioned function and also checks the type of...

diagnostic
merge conflicts

auto-reduced (treereduce-rust): ````rust //@compile-flags: -frust-incomplete-and-experimental-compiler-do-not-use enum E { A = { enum F { Foo { a: usize, b: usize }, Bar(usize, usize), } 0 }, } ```` original: ````rust...

bug

You can use `RANGE_EXPR` as an index -- that might be outside the scope of this PR though _Originally posted by @powerboat9 in https://github.com/Rust-GCC/gccrs/issues/3751#issuecomment-2813683919_

### Summary When compiling a Rust program that attempts to add two very large arrays, GCCRS terminates with a fatal error (`gccrs: fatal error: Killed signal terminated program`), while Rustc...

### Summary Closures automatically implement the fn trait so this needs fixed ### Reproducer I tried this code: ```rust #[lang = "sized"] pub trait Sized {} #[lang = "fn_once"] pub...

bug

According to rust, the valid repr attributes are `Rust` (default), `C`, `align`, `packed`, `transparent`, `simd`, `i8`, `u8`, `i16`, `u16`, `i32`, `u32`, `i64`, `u64`, `i128`, `u128`, `isize` and `usize`. But gccrs...

bug
typechecking
codegen

### Summary When compiling a Rust program containing a macro that matches the meta fragment specifier, GCCRS exceeds the processing time limit and is terminated with SIGKILL. The same code...

### Summary When compiling the attached Rust code with GCCRS, the compiler gets terminated with SIGKILL due to processing time exceeded, while rustc correctly reports the missing Display trait implementation....

### Summary When compiling code containing match expressions with a macro-expanded tuple struct pattern (ApplicationTy(TypeCtor::X)) or equivalent OR patterns, gccrs fails to terminate and gets killed (SIGKILL). The same code...

### Summary When compiling code with deeply nested macro_rules! expansions (e.g., x10!{x10!{x10!{...}}}), GCCRS consumes excessive resources and gets killed by the OS (SIGKILL), while Rustc handles it gracefully. ### Reproducer...