News for hackers. Stuff that matters.
Re:Apple announces it will switch to its own processors for ... by Teknoman117 on Monday June 22, 2020 @05:22PM (#23606868)
Why do feel that Rust is behind on ARM? I can't comment on the performance, but everything that I used that was purely written in Rust compiled and ran perfectly on my PineBook Pro. (with the exception of alacritty, but that's because PBP doesn't support OpenGL 3.x)

Go does have the (platform) advantage (?) of preferring the "rewrite everything in Go" approach, so those just transition when the tooling supports a new architecture. Rust is intentionally going with a interop design, rather than telling people the only answer to to rewrite all their favorite libraries.

Re:Apple announces it will switch to its own processors for ... by steveklabnik on Monday June 22, 2020 @05:33PM (#23607015)
Rust and ARM is just fine. For example, Cloudflare famously keeps their entire stack cross-compilable to ARM, and even ships Rust on iPhones.

There's two areas where I believe you could call it second-class at the moment, though:

1. There is no ARM targets in Rust's "Tier 1" platform support.

2. std::arch doesn't have ARM intrinsics in stable.

For 1, ARM targets are in a weird space; they aren't Tier 1, but they're closer than most of the other Tier 2 targets. Several ARM targets are Tier 1 for Firefox, for example, so they get a bunch of work done there.

For 2, well, there hasn't been as much demand before. I expect that to change because of this.

... we'll see what the future holds :)

Re:Apple announces it will switch to its own processors for ... by sroussey on Monday June 22, 2020 @08:55PM (#23608832)
Sounds like this will cost Mozilla some time and money, but they will have to support it.
Re:Apple announces it will switch to its own processors for ... by steveklabnik on Monday June 22, 2020 @09:12PM (#23608920)
I’m not sure why. As I said, they’ve been using Rust on ARM (as part of Firefox) for a long time; I’m not aware of them being unsatisfied with the current state.

I expect that the Rust project will end up benefiting from the extra interest though, and improving on the things above.

Re:Apple announces it will switch to its own processors for ... by fork-bomber on Wednesday June 24, 2020 @06:20AM (#23626250)
There has been very good progress on filling in the gaps to officially get Rust's AArch64 Linux toolchain triple to Tier-1 this year. We have CI for the Rust compiler test suites on native AArch64 silicon in a joint collaboration between Arm and the Rust lang core team and are converging on zero compiler test failures. Overall, we are pretty close to attaining Tier-1!
Re:Apple announces it will switch to its own processors for ... by steveklabnik on Wednesday June 24, 2020 @09:55AM (#23627892)
> a joint collaboration between Arm

Is this public knowledge yet?

Re:Apple announces it will switch to its own processors for ... by fork-bomber on Wednesday June 24, 2020 @02:53PM (#23632260)
We haven't been very vocal about it just yet but all the bits to enable CI etc and the new t/compiler-arm Zulip stream are happening openly pretty much.

I'll be pinging all the relevant folks soon-ish (we're pushing out fixes to the last remaining compiler test suite failures this week).

I mean to keep you on CC as I did the last time!

Re:Apple announces it will switch to its own processors for ... by steveklabnik on Wednesday June 24, 2020 @05:17PM (#23633982)
Cool, I was dancing around it in this thread and recently because I wasn't sure how public it was :) I appreciate it!
Re:Apple announces it will switch to its own processors for ... by mlindner on Tuesday June 23, 2020 @02:51AM (#23610636)
Anything that runs Firefox also supports Rust as Rust is a core part of Firefox.
Re:Apple announces it will switch to its own processors for ... by monocasa on Monday June 22, 2020 @11:37PM (#23609677)
I've been working on an OS in Rust that has an aarch64 port, and I've for sure seen some... questionable output. It's all been valid code for the input, but not nearly as optimized as I've come to expect out of LLVM based compilers. I'm sure there's some low hanging fruit that needs attention is all.