Read 34 answers by scientists to the question asked by Christian Thomas Wolf on Mar 6, 2020

Op 2 november schreef LWN.net over de release van Tor Browser 16.0. Het is de eerste stabiele versie van de browser die is gebaseerd op Firefox ESR 153. De Linux-versie ondersteunt nu 64bit-Arm.

VQ3 - An Ensoniq-inspired Mega Synth : Windows 32/64bit VST Soft Synth

ExLight Build 260322 uses kernel 6.19.8-amd64-exton built from Debian kernel sources with Debian patches.

Amazon · R$600,97

All 25 messages in linux-pci: [PATCH v2 0/2] Fix for storage corruption w/ AMD IOMMU on 64-bit addressing

I can't build this because it applies only to special 32bit systems and I only have full 64bit ones, but as far as these special systems go it does what it advertises. I read the discussion on the repo and as the author say, this applies only to glibc not just because the code is properly guarded, but because the affected systems can exist only by using glibc. This code only applies when glibc and every program linking to it use macros to access 64bit-capable functions despite being on a 32bit-capable system. This is something that exists only on glibc, I'm not aware of any other library (either musl, the one used by clang, or anything else) where this kind of "transitional" system exists. Those macros should only affect file and time operations, so there shouldn't be any follow-up to this commit as it should take care of everything. I say should because I'm basing this on reading glibc documentation, not real testing. To go into a bit more detail, the code tries to always use the 64bit-capable interface no matter the kind of system it is compiled for. The lsfName function makes sure to fetch the (now deprecated and always listed as a transition solution) functions with a "64" suffix, e.g. lseek64 instead of lseek. These functions were added to avoid breaking ABI back when 64bit was first introduced. However these functions really only exist for file operations. For the time-related ones, the glibc code uses a terrifying feature to change the function name to an "internal" 64bit-capable implementation. This means that on a 32bit system compiled to use 64bit functions, these time functions cannot be extracted unless the "new" name is used. For example time() after compiling the program becomes __time64(). The commit in question uses these "assembly names" when this "feature" is detected. In closing, even though I can't compile or run this commit, by cross-referencing documentation and my own experience I can at least say that for the majority of Pale Moon and other UXP-based applications users this is harmless. * * *

Amazon · R$602,82

Versie 1.12.3 van XnView MP is uitgekomen. Met dit programma kunnen afbeeldingen worden bekeken en bewerkt. Het is gratis voor persoonlijk gebruik; voor gebruik in een commerciële omgeving wordt wel een vergoeding gevraagd. MP staat voor Multi Platform, wat betekent dat er versies zijn voor Windows, Linux en macOS, met elk aparte downloads voor 32bit- en 64bit-omgevingen. XnView MP gebruikt dezelfde broncode voor Windows, Linux en macOS; functionaliteit en uiterlijk van de afzonderlijke versies zijn dan ook nagenoeg gelijk. Zo is er onder andere ondersteuning voor unicode, afbeeldingen met full bit depth, een eenvoudigere manier voor vertalingen en een betere database. In deze uitgave zijn de volgende veranderingen en verbeteringen aangebracht: Changes in XnView MP 1.12.3