From: Mark Wielaard <mark@klomp.org>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: [PATCH] Fix byte char and byte string lexing code
Date: Wed, 22 Sep 2021 22:37:38 +0200 [thread overview]
Message-ID: <YUuUEnzWnUMmjFhg@wildebeest.org> (raw)
In-Reply-To: <87k0j9ym7r.fsf@euler.schwinge.homeip.net>
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
next prev parent reply other threads:[~2021-09-22 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 22:54 Mark Wielaard
2021-09-22 9:48 ` Thomas Schwinge
2021-09-22 20:37 ` Mark Wielaard [this message]
2021-09-23 11:43 ` Philip Herron
2021-09-23 14:10 ` Arthur Cohen
2021-09-23 20:53 ` byte/char string representation (Was: [PATCH] Fix byte char and byte string lexing code) Mark Wielaard
2021-09-24 11:01 ` Philip Herron
2021-09-25 11:53 ` Mark Wielaard
2021-09-30 10:46 ` Philip Herron
2021-10-03 22:04 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YUuUEnzWnUMmjFhg@wildebeest.org \
--to=mark@klomp.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=thomas@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).