Mastodon

SourcewareThe next GNU Tools Cauldron, taking place in Porto, Portugal, on September 26-28, 2025.<a href="https://inbox.sourceware.org/gcc/87o6ubhn4j.fsf@oracle.com/" rel="nofollow noopener" translate="no" target="_blank">https://inbox.sourceware.org/gcc/87o6ubhn4j.fsf@oracle.com/</a> <a href="https://gcc.gnu.org/wiki/cauldron2025" rel="nofollow noopener" translate="no" target="_blank">https://gcc.gnu.org/wiki/cauldron2025</a> <a href="https://gnu-tools-cauldron.org/" rel="nofollow noopener" translate="no" target="_blank">https://gnu-tools-cauldron.org/</a>Some <a href="https://fosstodon.org/tags/Sourceware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sourceware</a> Project Leadership Committee members and <a href="https://social.sfconservancy.org/users/conservancy" class="u-url mention" rel="nofollow noopener" target="_blank">@conservancy</a> staff should also be there.<a href="https://fosstodon.org/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a> <a href="https://fosstodon.org/tags/GDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDB</a> <a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a> <a href="https://fosstodon.org/tags/CGEN" class="mention hashtag" rel="nofollow noopener" target="_blank">#CGEN</a> <a href="https://fosstodon.org/tags/DejaGnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#DejaGnu</a> <a href="https://fosstodon.org/tags/newlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#newlib</a> <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://fosstodon.org/tags/poke" class="mention hashtag" rel="nofollow noopener" target="_blank">#poke</a> <a href="https://fosstodon.org/tags/libabigail" class="mention hashtag" rel="nofollow noopener" target="_blank">#libabigail</a> <a href="https://fosstodon.org/tags/elfutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#elfutils</a>

Christian HornWhen researching for one of my last articles, I noticed a speed difference between RHEL7 and RHEL10. I used these 2, but the observed speciality can also be seen on (all?) other distros.Got to the ground of it, might make a fun read for all involved with glibc and emulation : <a href="https://blog.fluxcoil.net/posts/2025/06/the-riddle-of-rhel7-being-faster-than-rhel10/" rel="nofollow noopener" translate="no" target="_blank">https://blog.fluxcoil.net/posts/2025/06/the-riddle-of-rhel7-being-faster-than-rhel10/</a> <a href="https://chaos.social/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a> <a href="https://chaos.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://chaos.social/tags/emulation" class="mention hashtag" rel="nofollow noopener" target="_blank">#emulation</a>EDIT: graphics added to the article

Kevin Karhan :verified:<a href="https://cuties.cloud/@ULTROS_PROFESSIONAL" class="u-url mention" rel="nofollow noopener" target="_blank">@ULTROS_PROFESSIONAL</a> <a href="https://studio8502.ca/@mos_8502" class="u-url mention" rel="nofollow noopener" target="_blank">@mos_8502</a> yeah. <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GlibC</a> randomly bricks shit at minor version updates.Their response: "JuSt ReCoMpIlE!"

Kevin Karhan :verified:<a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@mrmasterkeyboard</a> <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> My choice of <a href="https://social.treehouse.systems/@musl" class="u-url mention" rel="nofollow noopener" target="_blank">@musl</a> for <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> is because I want my stuff to be statically linked and not every minor update to have the risk to brick shit, because <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GlibC</a> is notorious for that since the <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> project are nonchalantly thinking "just recompile it" is a valid excuse.<ul><li>Espechally since (for better or worse) not everything is (A)GPL(v3)-licensed and prople may need to deal with <a href="https://infosec.space/tags/binaries" class="mention hashtag" rel="nofollow noopener" target="_blank">#binaries</a> and/or <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> because in many cases patents and licensing are not allowing the distribution of it.</li></ul>I mean, we all 'loved' to live in a world where this wasn't the case but if I were to like deal with a vocoder for <a href="https://en.wikipedia.org/wiki/Mixed-excitation_linear_prediction" rel="nofollow noopener" target="_blank">MELP</a>, <a href="https://en.wikipedia.org/wiki/Multi-Band_Excitation" rel="nofollow noopener" target="_blank">AMBE</a> or <a href="https://twelp.pro" rel="nofollow noopener" target="_blank">TWELP</a> I'm pretty shure I'd never ever be allowed to distribute it's source code, even for "clients exempted from the need to obtain licensing"...

Kevin Karhan :verified:<a href="https://fosstodon.org/@lmemsm" class="u-url mention" rel="nofollow noopener" target="_blank">@lmemsm</a> basically the Idea behind <a href="https://infosec.space/@OS1337" rel="nofollow noopener" target="_blank">it</a> is to be a brutally simple <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> + <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> / <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> distro that grew out of the necessity for me to actually think about <a href="https://infosec.space/tags/firmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#firmware</a> for some projects. <ul><li>And lets just say I did saw <a href="https://fosstodon.org/@w84death" class="u-url mention" rel="nofollow noopener" target="_blank">@w84death</a> 's <a href="https://infosec.space/tags/Floppynux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Floppynux</a> and <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> did present <a href="https://www.youtube.com/watch?v=SGmtP5Lg_t0" rel="nofollow noopener" target="_blank">a</a> <a href="https://www.youtube.com/watch?v=MkJkyMuBm3g" rel="nofollow noopener" target="_blank">lot</a> of convincing arguments <a href="https://www.youtube.com/watch?v=Sk9TatW9ino" rel="nofollow noopener" target="_blank">alongside a literal walktrough</a> to get started.</li></ul>Basically I want something that is so simple and auditable that it's practical to make it pass any <a href="https://infosec.space/tags/verification" class="mention hashtag" rel="nofollow noopener" target="_blank">#verification</a> demands for <a href="https://infosec.space/tags/SecureTerminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecureTerminal</a>|s in <a href="https://infosec.space/tags/CriticalInfrastructure" class="mention hashtag" rel="nofollow noopener" target="_blank">#CriticalInfrastructure</a> and <a href="https://infosec.space/tags/Communications" class="mention hashtag" rel="nofollow noopener" target="_blank">#Communications</a>. <ul><li>OFC one may point at my other projects and say: "Why don't you just put <a href="https://infosec.space/tags/RaspberryPiOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPiOS</a> on a <a href="https://infosec.space/tags/microSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#microSD</a>?" ignoring that the smallest image is >330MB in size and that seems kinda overkill for essentially my demands for a minimalist <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> with very few programs in userspace. </li></ul>Not to mention a <a href="https://infosec.space/tags/GNUfree" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUfree</a> - <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> distro is the way to go if I want that thing to not get bricked constantly by minor <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GlibC</a>-changes... <ul><li>End goal is something akin to <a href="https://infosec.space/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> in it's brutal simplicity, but way more extendable.</li></ul> I hope that answers your question...<ul><li>Sorry for the delay.</li></ul>

Michel Lind :fedora: :debian:One year to the day after my first <a href="https://hachyderm.io/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> commit is written, I am back at Arjun’s glibc clinic for round two! <a href="https://fosstodon.org/@devconf_cz" class="u-url mention" rel="nofollow noopener" target="_blank">@devconf_cz</a> <a href="https://hachyderm.io/tags/DevConf_CZ" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevConf_CZ</a> <a href="https://hachyderm.io/tags/FOSSConference" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSSConference</a> <a href="https://hachyderm.io/tags/FOSSConf" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSSConf</a> <a href="https://hachyderm.io/tags/DevConf2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevConf2025</a>

datenwolfAll I want is just a collection of <a href="https://chaos.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a>, <a href="https://chaos.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a>, <a href="https://chaos.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a>+<a href="https://chaos.social/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#clang</a>, <a href="https://chaos.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> and <a href="https://chaos.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> that are "free standing" / relocatable, which I can pack into a <a href="https://chaos.social/tags/squashfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#squashfs</a> image to carry around to my various development machines.You'd think that for something as fundamental as compiler infrastructure with over 60 years of knowledge, the whole bootstrapping and bringup process would have been super streamlined, or at least mostly pain free by now.Yeah, about that. IYKYK

IBBoardReading through the code, and I'm not even sure that some of the PHP functions make sense!PHP has a `crypt` function that takes a string and a salt. But the Wordpress code _and_ the in-page function are using the hashed password as the salt. Which makes no sense. How can you salt a password with the hashed password and get something that you can compare against?Wait. There _is_ something in the PHP docs. Not well signposted. But apparently "salt" _is_ extracted from hashed values. Which is SO obvious from the parameter naming 🙄Should say up-front "$salt is not actually the salt - it's a string containing the salt and other characters that's processed according to the chosen crypt algorithm"*digs further*Oh. It looks like that magic behaviour is ACTUALLY the fault of glibc2 😑 <a href="https://linux.die.net/man/3/crypt" rel="nofollow noopener" translate="no" target="_blank">https://linux.die.net/man/3/crypt</a>(Not clear yet how it handles `$P$` not being one of its known prefixes 😐)<a href="https://hachyderm.io/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://hachyderm.io/tags/WTF" class="mention hashtag" rel="nofollow noopener" target="_blank">#WTF</a> <a href="https://hachyderm.io/tags/Wordpress" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wordpress</a> <a href="https://hachyderm.io/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a>

Felix Palmen :freebsd: :c64:Solved! 🥳 This was a pretty "interesting" bug. Remember when I invented a way to implement <a href="https://mastodon.bsd.cafe/tags/async" class="mention hashtag" rel="nofollow noopener" target="_blank">#async</a> / <a href="https://mastodon.bsd.cafe/tags/await" class="mention hashtag" rel="nofollow noopener" target="_blank">#await</a> in <a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a>, for jobs running on a threadpool. Back then I said it only works when completion of the task resumes execution on the *same* pool thread.Trying to improve overall performance, I found the complex logic to identify the thread job to put on a pool thread a real deal-breaker. Just having one single MPMC queue with a single semaphore for all pool threads to wait on is a lot more efficient. But then, a job continued after an awaited task will resume on a "random" thread.It theoretically works by making sure to restore the CORRECT context (the original one of the pool thread) every time after executing a job, whether partially (up to the next await) or completely.Only it didn't, at least here on <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a>, and I finally understood the reason for this was that I was using <a href="https://mastodon.bsd.cafe/tags/TLS" class="mention hashtag" rel="nofollow noopener" target="_blank">#TLS</a> (thread-local storage) to find the context to restore.Well, most architectures store a pointer to the current thread metadata in a register. <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> user <a href="https://mastodon.bsd.cafe/tags/context" class="mention hashtag" rel="nofollow noopener" target="_blank">#context</a> <a href="https://mastodon.bsd.cafe/tags/switching" class="mention hashtag" rel="nofollow noopener" target="_blank">#switching</a> saves and restores registers. I found a source claiming that the <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> (<a href="https://mastodon.bsd.cafe/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a>) implementation explicitly does NOT include the register holding a thread pointer. Obviously, <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a>'s implementation DOES include it. POSIX doesn't have to say anything about that.In short, avoiding TLS accesses when running with a custom context solved the crash. 🤯

Vitexapt-listchanges: News ---------------------<a href="https://f.cz/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> (2.41-7) unstable; urgency=medium Starting with glibc 2.41, shared libraries requiring an executable stack cannot be dynamically loaded through the dlopen mechanism from a binary that does not require an executable stack. This change aims to improve <a href="https://f.cz/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>, as the previous behavior was used as a vector for RCE (<a href="https://f.cz/tags/CVE" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE</a>-2023-38408). Attempting to do so will result in the following error: cannot enable executable stack as shared object requires: Invalid argument While most libraries generated in the past 20 years do not require an executable stack, some third-party software still need this capability. Many vendors have already updated their binaries to address this. If you need to run a program that requires an executable stack through dynamic loaded shared libraries, you can use the glibc.rtld.execstack tunable: GLIBC_TUNABLES=glibc.rtld.execstack=2 ./program -- Aurelien Jarno <aurel32@debian.org> Sun, 13 Apr 2025 14:41:11 +0200<a href="https://f.cz/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> <a href="https://f.cz/tags/Trixie" class="mention hashtag" rel="nofollow noopener" target="_blank">#Trixie</a> <a href="https://f.cz/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>

Aho<a href="https://social.linux.pizza/@MichaelRoss" class="u-url mention" rel="nofollow noopener" target="_blank">@MichaelRoss</a> something I have been trying to look for is a <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/ls" class="mention hashtag" rel="nofollow noopener" target="_blank">#ls</a> that isn't depending on <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> or another <a href="https://mastodon.social/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> implementation, the reason is there was some malware that attached itself to glibc and prevented you to see the directories and files it used and also the process directory in /proc Had you a ls that wasn't built with glibc, then all the files and directories would be listed.

Freexian :debian:Debian LTS contributors released 46 Debian LTS Advisories about security updates for various packages in April 2025.These include critical security bug fixes for jetty9, zabbix and glibc and more. Also several LTS contributors prepared packages for the recent point release of current stable Debian 12, with many prepared in conjunction with related LTS updates of the same packages.Read more about this in our monthly report for April here: <a href="https://www.freexian.com/blog/debian-lts-report-2025-04/" rel="nofollow noopener" translate="no" target="_blank">https://www.freexian.com/blog/debian-lts-report-2025-04/</a>This work is funded by Freexian's Debian LTS offering.Your organization too can sponsor the Debian LTS (<a href="https://www.freexian.com/lts/debian/" rel="nofollow noopener" translate="no" target="_blank">https://www.freexian.com/lts/debian/</a>) and join the esteemed list of sponsors in the monthly report.<a href="https://hachyderm.io/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> <a href="https://hachyderm.io/tags/debianlts" class="mention hashtag" rel="nofollow noopener" target="_blank">#debianlts</a> <a href="https://hachyderm.io/tags/freexian" class="mention hashtag" rel="nofollow noopener" target="_blank">#freexian</a> <a href="https://hachyderm.io/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://hachyderm.io/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a>

jbz⚠️ Steam Will Stop Working on Outdated Linux Systems This August | Linuxiac ｢ According to a recent announcement, the Steam client will no longer run on any distribution with a GNU C Library (glibc) version older than 2.31 starting August 15, 2025.Users who stay on an outdated toolchain will find not only Steam but also any purchased games unable to launch until the underlying operating system is upgraded ｣<a href="https://linuxiac.com/steam-will-stop-working-on-outdated-linux-systems-this-august/" rel="nofollow noopener" translate="no" target="_blank">https://linuxiac.com/steam-will-stop-working-on-outdated-linux-systems-this-august/</a><a href="https://indieweb.social/tags/steam" class="mention hashtag" rel="nofollow noopener" target="_blank">#steam</a> <a href="https://indieweb.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://indieweb.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://indieweb.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

Tuckers Nuts Resist! 🇺🇦 <a href="https://mastodon.social/@cleverboi" class="u-url mention" rel="nofollow noopener" target="_blank">@cleverboi</a> Boi, I'm not knowledgeable about glibc, but I do use and like Pop!_Os, so I'm boosting your twt in an effort to secure you an answer. I don't know your use case, so I have no clue why you'd be having this software issue with Pop!_Os! Hope someone else can be of actual assistance. <a href="https://mstdn.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mstdn.social/tags/GLIBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GLIBC</a> <a href="https://mstdn.social/tags/Pop" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pop</a>!_Os <a href="https://mstdn.social/tags/PopOs" class="mention hashtag" rel="nofollow noopener" target="_blank">#PopOs</a>

Vitexglibc (2.41-7) unstable; urgency=medium Starting with glibc 2.41, shared libraries requiring an executable stack cannot be dynamically loaded through the <a href="https://f.cz/tags/dlopen" class="mention hashtag" rel="nofollow noopener" target="_blank">#dlopen</a> mechanism from a binary that does not require an executable stack. This change aims to improve security, as the previous behavior was used as a vector for RCE (<a href="https://f.cz/tags/CVE" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE</a>-2023-38408). Attempting to do so will result in the following error: cannot enable executable stack as shared object requires: Invalid argument While most libraries generated in the past 20 years do not require an executable stack, some third-party software still need this capability. Many vendors have already updated their binaries to address this. If you need to run a program that requires an executable stack through dynamic loaded shared libraries, you can use the glibc.rtld.execstack tunable: Glibc6_TUNABLES=glibc.rtld.execstack=2 ./program -- Aurelien Jarno <aurel32@debian.org> Sun, 13 Apr 2025 14:41:11 +0200<a href="https://f.cz/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> <a href="https://f.cz/tags/Changelog" class="mention hashtag" rel="nofollow noopener" target="_blank">#Changelog</a> <a href="https://f.cz/tags/GLibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GLibC</a> <a href="https://f.cz/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://f.cz/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>

An "Alaknár" ZaOn August 15th, 2025, Steam will officially stop supporting Linux distributions with a version of glibc older than 2.31 <a href="https://friendica.world/display/84b6ef2b-3168-0736-1c9c-81e579514582" rel="nofollow noopener" translate="no" target="_blank">https://friendica.world/display/84b6ef2b-3168-0736-1c9c-81e579514582</a>

SourcewareSourceware Survey 2025 ResultsIn the end we got 103 (!) responses with a nice mix of developers, users and maintainers from various hosted projects.<a href="https://sourceware.org/survey-2025" rel="nofollow noopener" translate="no" target="_blank">https://sourceware.org/survey-2025</a><a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a> <a href="https://fosstodon.org/tags/cygwin" class="mention hashtag" rel="nofollow noopener" target="_blank">#cygwin</a> <a href="https://fosstodon.org/tags/dwarfstd" class="mention hashtag" rel="nofollow noopener" target="_blank">#dwarfstd</a> <a href="https://fosstodon.org/tags/elfutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#elfutils</a> <a href="https://fosstodon.org/tags/gcc" class="mention hashtag" rel="nofollow noopener" target="_blank">#gcc</a> <a href="https://fosstodon.org/tags/gdb" class="mention hashtag" rel="nofollow noopener" target="_blank">#gdb</a> <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://fosstodon.org/tags/libabigail" class="mention hashtag" rel="nofollow noopener" target="_blank">#libabigail</a> <a href="https://fosstodon.org/tags/newlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#newlib</a> <a href="https://fosstodon.org/tags/systemTap" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemTap</a> <a href="https://fosstodon.org/tags/valgrind" class="mention hashtag" rel="nofollow noopener" target="_blank">#valgrind</a> <a href="https://fosstodon.org/tags/bzip2" class="mention hashtag" rel="nofollow noopener" target="_blank">#bzip2</a> <a href="https://fosstodon.org/tags/libffi" class="mention hashtag" rel="nofollow noopener" target="_blank">#libffi</a> <a href="https://fosstodon.org/tags/dwz" class="mention hashtag" rel="nofollow noopener" target="_blank">#dwz</a> <a href="https://fosstodon.org/tags/debugedit" class="mention hashtag" rel="nofollow noopener" target="_blank">#debugedit</a> <a href="https://fosstodon.org/tags/gnupoke" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnupoke</a> <a href="https://fosstodon.org/tags/bunsen" class="mention hashtag" rel="nofollow noopener" target="_blank">#bunsen</a> <a href="https://fosstodon.org/tags/lvm2" class="mention hashtag" rel="nofollow noopener" target="_blank">#lvm2</a> <a href="https://fosstodon.org/tags/annobin" class="mention hashtag" rel="nofollow noopener" target="_blank">#annobin</a> <a href="https://fosstodon.org/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnu</a>-gabi <a href="https://fosstodon.org/tags/cgen" class="mention hashtag" rel="nofollow noopener" target="_blank">#cgen</a> <a href="https://fosstodon.org/tags/kawa" class="mention hashtag" rel="nofollow noopener" target="_blank">#kawa</a> <a href="https://fosstodon.org/tags/insight" class="mention hashtag" rel="nofollow noopener" target="_blank">#insight</a> <a href="https://fosstodon.org/tags/pacme" class="mention hashtag" rel="nofollow noopener" target="_blank">#pacme</a>

you╭👺+300╭🐈x5╭⁂+3╭(Ⓐ+a<a href="https://mastodon.social/tags/tek" class="mention hashtag" rel="nofollow noopener" target="_blank">#tek</a> 0.2.0 out now: <a href="https://codeberg.org/unspeaker/tek/releases/tag/0.2.0" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/unspeaker/tek/releases/tag/0.2.0</a>it's buggy as hell, and about half the features i've showcased previously are disabled for now. but, more importantly, i've managed to build it as a single binary that you should be able to run on any <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> with <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> and <a href="https://mastodon.social/tags/jack" class="mention hashtag" rel="nofollow noopener" target="_blank">#jack</a>... let me know what happens!<a href="https://mastodon.social/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> <a href="https://mastodon.social/tags/tui" class="mention hashtag" rel="nofollow noopener" target="_blank">#tui</a> <a href="https://mastodon.social/tags/daw" class="mention hashtag" rel="nofollow noopener" target="_blank">#daw</a>

Felix Palmen :freebsd: :c64:Today, I implemented the <a href="https://mastodon.bsd.cafe/tags/async" class="mention hashtag" rel="nofollow noopener" target="_blank">#async</a> / <a href="https://mastodon.bsd.cafe/tags/await" class="mention hashtag" rel="nofollow noopener" target="_blank">#await</a> pattern (as known from <a href="https://mastodon.bsd.cafe/tags/csharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#csharp</a> and meanwhile quite some other languages) ...... in good old <a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a>! 😎 Well, at least sort of.* It requires some standard library support, namely <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> user context switching with <a href="https://mastodon.bsd.cafe/tags/getcontext" class="mention hashtag" rel="nofollow noopener" target="_blank">#getcontext</a> and friends, which was deprecated in POSIX-1.2008. But it's still available on many systems, including <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a>, <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#NetBSD</a>, <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> (with <a href="https://mastodon.bsd.cafe/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a>). It's NOT available e.g. on <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBSD</a>, or Linux with some alternative libc.* I can't do anything about the basic language syntax, so some boilerplate comes with using it.* It has some overhead (room for extra stacks, even extra syscalls as getcontext unfortunately also always saves/restores the signal mask)But then ... async/await in C! 🥳 Here are the docs: <a href="https://zirias.github.io/poser/api/latest/class_p_s_c___async_task.html" rel="nofollow noopener" translate="no" target="_blank">https://zirias.github.io/poser/api/latest/class_p_s_c___async_task.html</a><a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a>

Recent searches

Search options

Administered by:

Server stats:

#glibc