For some reason I spent two hours annotating a tiny chunk of the libstdc++ std::vector implementation that somebody asked about on reddit
https://www.reddit.com/r/cpp_questions/comments/1rgstr1/comment/o7v0sli/
| Blog | https://kristerw.github.io |
| GitHub | https://github.com/kristerw |
For some reason I spent two hours annotating a tiny chunk of the libstdc++ std::vector implementation that somebody asked about on reddit
https://www.reddit.com/r/cpp_questions/comments/1rgstr1/comment/o7v0sli/
AI agent "contributes" PR to matplotlib.
PR gets rejected.
AI agent *writes and publishes blog to shame the maintainer*.
What a time to be alive.
RE: https://mathstodon.xyz/@markusde/116020715195099414
Oh boy, I've been *asked* to rant about constructivity and Lean's type theory, so here I come. Beware, long thread incoming (I tried to keep it reasonable, I have definitely failed).
Let's try something different today.
Reply with your favorite still opened gcc bug report (https://gcc.gnu.org/bugzilla/) . I am going to put together a poll next week on which bug report i should fix and that poll will be based on the responses here.
Disclaimer, X86_64 and aarch64 target specific bugs are OK, other backends depending on the bug report might be fine but I will reply to your toot if it will be included in the poll. If I get a lot of responses, I might have a few polls to narrow down which one I implement.
This is for 2 reasons, one to show gcc developers still care about the bug reports (especially with over 18k of them filed) and 2 to give an opportunity to users to see more of the process. Also sometimes I like giving back to the users of gcc.
In my work on [smtgcc](https://github.com/kristerw/smtgcc) to formalize the semantics of GIMPLE, I have found several cases where optimization passes perform invalid transformations, as well as cases where the GIMPLE semantics do not allow optimization passes to express what they need (see [PR120980](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120980) for an example). In this talk, I will present the current status of the formalization and discuss the issues I have found during the process.
I have implemented support for BPF assembly in the smtgcc GCC translation validator:
https://github.com/kristerw/smtgcc
It has already found multiple bugs in the GCC BPF backend. I have reported three so far:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122139
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122140
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122141
The GNU tools Cauldron 2025 schedule is now live:
https://conf.gnu-tools-cauldron.org/opo25/schedule/
Hope to see many of you there.