Conversation
jarkko

Jarkko Sakkinen

Edited 1 month ago
I did necessary plumbing and shoehorning to compile Buildroot with wild-linker. Took a few days but for Puu OS it halved the build time :-)

For 6-7 GIB image with GNOME, K3S, LLM-D and whatnot I went from 7-8 h build to time to 3,5 h using Zen 2 architecture laptop CPU (i.e. very slow CPU these days standards).

I packaged also wild for Buildroot, which is bootstrapped along with GCC and LLVM in the beginning of the build process.

Took four days to get this right but now I get 3,5 hours of interest for the time investment for every single build :-) I should release this work some day but better to get every tiny detail right at first.

#buildroot #rustlang #wild
2
0
1
jarkko

Jarkko Sakkinen

Reply to @jarkko
I'll push today some of the work ported on top of https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd-test.git/ today including wild integration for Buildroot. I mean obviously I want to speed up my kernel testing cycle too.
0
0
0
karppinen@mastodon.online

Marko Karppinen

Reply to @jarkko

@jarkko should remember to look at these like 10x more often than I do. My Rust build+test run was pushing 30 minutes and dealing with some known Mac pathologies took that down to 90 seconds. Should have done this months ago

1
0
0
jarkko

Jarkko Sakkinen

Reply to @karppinen@mastodon.online
@karppinen Using Wild is trivial for Rust project build. This is a completely different situation as it is used as the master linker for operating system build.

For Rust build you just edit `~/.cargo/config.toml` as the Github page instructs.
1
0
0
karppinen@mastodon.online

Marko Karppinen

Reply to @jarkko

@jarkko for sure, I didn't mean the specifics, just remembering to actually look at improving build times every once in a while no matter the environment

1
0
1
jarkko

Jarkko Sakkinen

Reply to @karppinen@mastodon.online
Edited 1 month ago
@karppinen Here the interesting use case was can it link EDK2 or glibc :-)
0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: