Hi guys, Thanks, Thomas for raising the PR it is currently being merged. We will raise the next PR to get bootstrapable builds working which will be really nice there is a GitHub automation for that at the moment.
Something I was thinking about outside of the scope of that patch was about the utf8 how do they get represented? Is it some kind of wchar_t? Thanks again --Phil On Wed, 22 Sept 2021 at 21:37, Mark Wielaard <m...@klomp.org> wrote: > Hi Thomas, > > On Wed, Sep 22, 2021 at 11:48:56AM +0200, Thomas Schwinge wrote: > > That's <https://github.com/Rust-GCC/gccrs/pull/343>. > > [...] > > That's <https://github.com/Rust-GCC/gccrs/pull/344>. > > Ah, sorry, I don't really track the github issues and had missed > those. But good to see the analysis matches. > > > Both these related to <https://github.com/Rust-GCC/gccrs/issues/336> > > "GCC '--enable-bootstrap' build". > > To make --enable-bootstrap possible (wow, that takes a long time...) > you'll also need: > https://gcc.gnu.org/pipermail/gcc-rust/2021-September/000178.html > > https://code.wildebeest.org/git/user/mjw/gccrs/commit/?h=rust-mangle-unreachable > > With this and that patch applied there are no more warnings building > the rust frontend, so a --enable-bootstrap (-Werror) build completes > successfully. > > > > > https://code.wildebeest.org/git/user/mjw/gccrs/commit/?h=bytecharstring > > > > Thanks, that's now: <https://github.com/Rust-GCC/gccrs/pull/687> > > "Fix byte char and byte string lexing code". > > Thanks, > > Mark > > -- > Gcc-rust mailing list > Gcc-rust@gcc.gnu.org > https://gcc.gnu.org/mailman/listinfo/gcc-rust >
-- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
