Re: [PATCH 0/7] RFC: Accelerate xdiff and begin its rustification

From: Patrick Steinhardt <ps@pks.im>
Date: Jul 24, 2025, 10:00 UTC
Message-ID: <aIIETOdK4Nrsy5Jb@pks.im>
In-Reply-To: <7bf054a1-0196-4ad8-aaa4-a432cd2c93a5@embecosm.com>

On Thu, Jul 24, 2025 at 11:01:22AM +0200, Pierre-Emmanuel Patry wrote:

Show 10 quoted lines

> 
> On Tue, Jul 23, 2025 at 06:32:06 +0200, Patrick Steinhardt wrote:
> > It would be great to know about the general timelines of these
> > alternative implementations.
> 
> We still think we'll be able to compile libcore before the end of the
> summer, we've made great progress and few items are left. But keep in mind
> we're targeting an older version of rust (1.49) and libcore is smaller than
> the standard library. We still have a lot of testing to do and we expect
> many bugs.

Understood. Given that we don't plan to roll with the latest version of Rust anyway I think it could be a viable tradeoff for us to also consider gccrs when we determine the minimum required Rust version.

Show 6 quoted lines

> The next targeted version will probably be rust 1.78 as we want to keep up
> with rust for linux. This shouldn't be too long as most of the features are
> coming from either standard library modifications or nightly features we
> already had to support for 1.49.
> 
> We expect to be able to compile some 1.49 code correctly next year at best.

And I expect that 1.78 will be another significant effort that won't land before the year after?

> I would like to bring to your attention rustc_codegen_gcc which adds a gcc
> backend to the rustc frontend, although not a full gcc compiler it could
> help supporting some architectures that are currently not supported by llvm.

For my own understanding: is this something that the Git project would have to support or something that the distributor needs to set up?

Patrick