Posts
4417
Following
315
Followers
470
Linux kernel hacker and maintainer etc.

OpenPGP: 3AB05486C7752FE1
Edited 10 months ago

Since there seems to be renewed interest in , I thought I'd have a look at the my CDE utilities from back then, which led me to my old Web page “Linux on a VAIO Z600LEK” http://dynalabs.de/mxp.old/vaio/index.html, because there's a screenshot of my work environment from back then. ⇢

1
2
1

@litchipi So my guess is that this lagging a bit behind, i.e. it might be that even tho GCC is already at 14.2 (at least in my Fedora system), this shows 14.0:

~/work/github/gccrs master*
$ $(find . -name gccrs) --version
gccrs (GCC) 14.0.1 20240309 (experimental)
Copyright (C) 2024 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
1
0
1
Edited 10 months ago
So after reading around the Internet I got the picture that already GCC 14.1 could be able to compile Rust-Linux. Is this correct? Amazing progress if it is! I did not simply know this.

I'll give it a shot since 14.1 came out already at Spring if I recall correctly.

Update: I have now gccrs build ongoing, after that I'll just point it out to cargo with build.rustc-wrapper and see how it compiles user space code first. Very interesting and exciting ;-)

#linux #kernel #rust #gcc
1
1
2
Edited 10 months ago
While making a track for Random Records [1] compilation I've noticed one and dumb and simple workflow improvement: for drum sounds hosted by a sampler in their own tracks it is best to keep key-tracking off.

Then the MIDI note values are free for Note Grid and for plugins like Effectrix 2. Saves tons of time because then no separate MIDI track is needed for triggering the effect.

[1] https://randomrecords.bandcamp.com/ #bitwig
0
0
0
Ie time to deliver the promise.
0
0
2
I mean if you money to pay for ext2 driver that we actually even don't need, you certainly have money to sponsor GCC.
1
0
0
It can be interpreted as an action where these companies try to purposely cause a toolchain lock-in. Not sure if that is even aligned with CoC. Please stop doing that.
1
0
0
#Microsoft and #Google should really put few million to GCC-Rust because they are the main corporate entities pushing the Rust code to the mainline.

Blame them instead of maintainers.

#linux #kernel #rust
1
1
2
Edited 10 months ago
Here's something I don't understand: ext2 driver in Rust. Frankly, I just don't get why Microsoft spends money on stuff like that.

Ok, so here's something I WOULD get (assuming that it compiles with GCC because it is a hard constraint): re-write user space interaction points of ext4 driver in Rust and make it call the existing internals.

Then I'd have a patch at hand that is written in Rust and that makes a modest improvement for the sake of better security, i.e. something I can *measure*.

I really try to avoid thinking of liking or disliking patch. If I can measure an improvement that overrides the possible drawbacks, then I see no other choice than carry the patch forward.
1
0
0
@jani Because I'm idealist let's put my 5-7 year timeline guess to 2-5% ;-) As GCC-Rust starts to catch up that might give a boost that is hard to predict beforehand, and also because Firefox is quite distant comparison point.
1
0
0
@jani I look mainly at the data. Firefox at 20% (2017-2024) now. Based on that my rough guess would be that within 5-7 years timeline we have 20% * 0.1 (complexity factor out of top of my head) = 2% of code that is in some defconfig. That is probably also about the time needed to GCC-Rust to catch up, which is literally a hard constraint because a defconfig's need to compile only with a GCC toolchain.

I don't think making Linux clang only would ever receive a positive response. Why I see defconfig level adoption happening in a longer timeline is that in input validation and all kinds of syscall/uapi layer stuff Rust adoption would have undebatable benefits.

I believe I have fairly weighted argument. I've used professionally Rust in user space code since 2022 (and actual low-level stuff like memory manager for Intel SGX enclaves), which I believe gives some basis also for my guess.

Like AI, blockchains, pick-your-hype-tech it is IMHO both uneducated to say that they are a hoax, and also that they solve every possible problem.
1
0
0
OK, now we can safely cross over "quantum computers will break all the crypto" apocalypse scenario. I'd predict that "AI will take all our jobs" will be next on the list (to be crossed over).
0
0
1
NIST's post-quantum key exchange algorithm is called "CRYSTALS-Kyber" 🤣 I guess NIST also has had a "brat summer". #NIST #cryptography #quantum
1
0
1
@FediTips Love the visual style of this post :-) Awesome collections of icons (of icons).
1
0
2
@hgfernan I'm not going to agree on anything since you are talking about stuff that can be plain observed. There is no topic to debate here.
1
0
1
@hgfernan Openhub from Synopsys is super useful for doing this type of comparisons.
1
0
0
@hgfernan So for example:

https://openhub.net/p/firefox/analyses/latest/languages_summary

Native ("non-XUL") code covers 49.1% so Rust's share is slightly better but I think I got it roughly correct ;-)
1
0
1
If I get a toxic response I imagine myself as being in a customer service. They get worse shit EVERY single day. It's good to actually think your reactive mindset BEFOREHAND you are in a situation where someone gets into your nerves.
0
0
1
Show older