Today work was centered around a few things. The main ones are outlined below.
I reviewed the MCP with new feedback I had received.
I started looking into setting up a GitHub pages for the repo I’ll hold the GSoC work product on.
I finished the siginfo_t on Linux patch and opened a PR.
The first thing I did was reviewing the MCP by simplifying the text and ensuring the purpose was stated in a more straightforward manner. Then I also tweaked some smaller stuff and sent back a response on the Zulip thread.
Then I went on to looking through the GSoC guidelines for the final evaluation to get a rough overview of the expected text body. I messaged my mentor with an outline of my plan, and looked into creating a GitHub Pages site for the report.
In between doing this, I also answered back to the FreeBSD PR, where my mentor mentioned it would be best to extend ctest. Another contributor has already been tagged with this task, so I’ll take it up if they’re not implementing it.
I also got the Linux uClibc PR merged.
Then I continued working through the siginfo_t on Linux patchset. I’ve finished up the uClibc targets and the musl definition, and have also opened a PR with the changes. The only notable changes are to M68K and RISCV-32 targets.
The last thing I did was to look into another issue in the 1.0 milestone. This time I looked into another old issue that seemed to already be solved in present-day libc. It’s concerned with a backward-incompatible change in FreeBSD.
The Windows function pointer issue thread remains silent.
None at present.
The MCP seems to be on the road to getting merged, as there didn’t seem to be any roablocks in my mentor’s answer. The pending PRs continue on halt, except for the Linux uClibc PR, which is now merged. The siginfo_t PR, though, fills that hole as it’s now pending. Either way, the Linux uClibc PR was split and the other half has remained silent for a while. I pinned the target maintainers back when I opened it, but that’s not received any comments yet. I plan to look into another old issue concerning the use unions, which seems more juicy.