P-E-P
P-E-P
@lucasly-ba I can't reproduce, has this been fixed ? https://godbolt.org/z/TMPxj6zn5
> Not sure if I'm doing things right, but I had to delete my previous branch to rebase to the current gccrs No this doesn't feel right. You don't have...
> Looks like there are some merge conflicts with #4322, which split `rust-parse-impl.h` into separate files. You'll probably have to manually move your changes into the file that `parse_bare_function_type` was...
@powerboat9 Any update on this PR ?
> is it possible for it to make a PR each time? instead of download artifact I think it will get lost otherwise What do you mean ? Initially I...
> 2. Add a MAX alloc limit of 2gb i think is what rustc does from reading it ages ago. > Or also put in a new constant for 2gb...
@sneaky-potato This should probably be fixed within the attribute checker (`rust/util/rust-attributes.cc`). You'll need to look for the `deprecated` attributes and when found check that their values are correct. If not,...
@0xllx0 This is not a parsing error with rustc 1.49 https://godbolt.org/z/Mr61sz5Tf
> Right, which is part of why it **is** a parsing error in `gccrs`. We should be getting warning messages similar to upstream `rustc`, instead we get parsing errors related...