Re: Test results for gccrs on Debian unstable ia64

2347 > # of unexpected failures21 > # of expected failures 26 Would it be possible to have the corresponding .log file ? Looks like nearly all execution tests are KO (3 out of 4...). Marc -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust

Re: Test results for gccrs on Debian unstable ia64

John Paul Adrian Glaubitz writes: > Hi Marc! > > On 6/2/21 2:41 PM, Marc wrote: >>> # of expected passes2347 >>> # of unexpected failures21 >>> # of expected failures 26 >> >> Would it be possible to have the co

Re: Test results for gccrs on Debian unstable ia64

on ia64 unless it's configured to use >> the internal version. I might be able to fix that myself. > > Addendum: Building with "--with-system-libunwind" fixes the problem for me > (see below). Hi! Thanks for testing this! IIUC, this is an issue on our side, so I&#x

Re: Test results for gccrs on Debian unstable ia64

John Paul Adrian Glaubitz writes: > Hi Marc! > > On 6/2/21 6:58 PM, Marc wrote: >> Thanks for testing this! IIUC, this is an issue on our side, so I'll >> open an issue. > > Let me test a plain GCC build with just C and C++ first to make sure it'

Re: Test results for gccrs on Debian unstable s390x

CE) are the same as seen on 32-bits debian, see https://github.com/Rust-GCC/gccrs/issues/467 . Thanks for these tests! Marc -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust

[PING] [PATCH] rust: avoid clobbering LIBS

Hello, Gentle reminder for this simple autoconf patch :) Thanks, Marc

Re: [PING] [PATCH] rust: avoid clobbering LIBS

Richard Biener writes: > On Wed, Aug 28, 2024 at 11:10 AM Marc wrote: >> >> Hello, >> >> Gentle reminder for this simple autoconf patch :) > > OK. > > Note that completely wiping LIBS might remove requirements detected earlier, > like some systems

Re: bootstrapping on a new platform - chicken and egg problem

> cargo should be a rust program but without the gccrs > how I am supposed to bootstrap ? Hello! Currently, the Rust frontend can't be bootstraped. You need an existing rustc toolchain (including cargo). Marc

Re: [PATCH] Fix inner attribute parsing

k, Sent to GH: https://github.com/Rust-GCC/gccrs/pull/530 Thanks :) Marc -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust

Re: [PATCH] Suppress warning in rust-ast-lower-type.h ASTLowerGenericParam.visit.

se was causing the error... Marc -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust

Re: [PATCH] Suppress warning in rust-ast-lower-type.h ASTLowerGenericParam.visit.

Mark Wielaard writes: > On Tue, Jun 29, 2021 at 12:47:07AM +0200, Mark Wielaard wrote: >> On Tue, Jun 29, 2021 at 12:06:56AM +0200, Marc wrote: >> > Hi, >> > >> > > Translating the AST LifetimeType to the HIR LifetimeType causes a >> > > warni

Re: [PATCH 2/2] Remove unused have_more_segments from TypeCheckExpr::resolve_root_path

Mark Wielaard writes: > It isn't necessary to know whether there are more segments while > iteration through the expression segements. Both patches in GH: https://github.com/Rust-GCC/gccrs/pull/537/commits Fixed a small typo in the commit message while creating the PR :) Marc -

Re: shebang handling

Mark Wielaard writes: > [PATCH 1/2] Handle shebang line, plus any whitespace and comment > [PATCH 2/2] Remove has_shebang flag from AST and HIR Crate classes Pushed to githup: https://github.com/Rust-GCC/gccrs/pull/546 Marc -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.g

Re: UTF-8 BOM handling

arting real lexing. > > It isn't necessary to keep track of the BOM in the AST or HIR Crate > classes. So I removed the has_utf8bom flag. > > Also included are a couple of simple tests to show we handle the BOM > correctly now. Merged : https://github.com/Rust-GCC/gccrs/pull/552

Re: Buildbot failure in Wildebeest Builder on whole buildset

o figure out what > is going on. Yes, it seems Thomas did a merge in 21af490baa734a901fb798bc2ac4df62109bc895, bringing gcc's master from a few days back :) [490e23032baaece71f2ec09fa1805064b150fbc2] Marc -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust

Re: Buildbot failure in Wildebeest Builder on whole buildset

5.203557 Looks suspicious. Is it possible that the VM got stuck ? Marc -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust

Re: [PATCH] Remove lambda iterators in various HIR classes

hile I was at it), and you can see that there are some small issues with the indentation: https://github.com/Rust-GCC/gccrs/pull/726/checks?check_run_id=3841896345 You need to be logged-in to see the results. If you don't have an account, you can still apply clang-format by hand :) Marc -- Gc

Re: [PATCH Rust front-end v3 01/46] Use DW_ATE_UTF for the Rust 'char' type

Mark Wielaard writes: > https://code.wildebeest.org/git/user/mjw/gccrs/commit/?h=no-Rust-old > if someone wants to push that, to merge for a v4. Sorry, missed that part, taking care of merging it right now :) https://github.com/Rust-GCC/gccrs/pull/1649 Thanks, Marc -- Gcc-rust mailin