From: listout <brahmajit.xyz@gmail.com>
To: gentoo-soc <gentoo-soc@lists.gentoo.org>
Cc: juippis <juippis@gentoo.org>, sam <sam@gentoo.org>,
arsen <arsen@gentoo.org>
Subject: [gentoo-soc] Week 8 report on porting Gentoo packages to modern C
Date: Sun, 23 Jul 2023 20:36:44 +0530 [thread overview]
Message-ID: <st6ix6xyzeal4pbguxx7ghozqgssy6meujmcthg33y7ne5vzkv@cl2dnm3jgfzy> (raw)
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
Hello all,
I'm here with my week 8 report on Modern C porting of Gentoo's packages.
Current:
Testing environments are set. I now have three environments to test my
PRs on.
- GCC 13 with glibc
- Clang-16 with llvm profile
- Clang-16 with musl-llvm profile
Much of it goes to juippis who gave me the instructions for creating
custom lxc images using gentoo stage-3 tar balls. This has helped me
immensely, I can now have testing environment ready in only couple of
minutes and keep untouched clean environments at ready.
Coming to my work, it's has remained the same, I've picked up various
random bugs from the tracker list and worked on them. But I've come to
the realization that my work isn't just limited to c99 or c11 porting.
It's is mix between c99 porting, using Clang-16 as the default compiler
and perhaps using lld as the system linker as well. Which of course I'm
very happy about.
Another thing that Sam brought up is that it's always the best to inform
him whenever I'm or I'm not sending patches upstream, because it's in
my initial proposal to send patches upstream and sometimes it's very
important because often times the developers of the packages know better
about the codebase and can offer more in sights about what would be the
best practice.
Next:
Coming next week, I plan to work more on reducing the bug from the
tracker, mainly picking up bugs from the tracker and send patching them.
Also, work with Sam and Joonas on my already submitted patches as they
have started to review my PRs. Not to mention I've to take care about
sending patches upstream whenever possible, as Sam mentioned.
Till then, see ya!
--
Regards,
listout
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2023-07-23 15:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=st6ix6xyzeal4pbguxx7ghozqgssy6meujmcthg33y7ne5vzkv@cl2dnm3jgfzy \
--to=brahmajit.xyz@gmail.com \
--cc=arsen@gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
--cc=juippis@gentoo.org \
--cc=sam@gentoo.org \
/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