The article explains how Intel’s newly announced x86S architecture simplifies the decades‑old x86 design by dropping 16‑ and 32‑bit modes while still supporting legacy 32‑bit applications, reducing processor complexity and improving performance amid growing ARM competition.
The article explains the upcoming 2038 Y2K38 Unix time overflow, why Debian is proactively converting its entire system to 64‑bit time stamps, the technical challenges involved, and how legacy 32‑bit hardware and software will be affected.
This article traces Intel's processor lineage from the 1971 4004 to modern x86_64 CPUs, explains why the 32‑bit operating system is called x86 despite varying bit widths, and clarifies the naming conventions used by AMD and Microsoft for 64‑bit platforms.
This article recounts the origin of the Unix epoch, explains why a single integer counting seconds from 1 January 1970 was adopted, outlines its advantages, and discusses the 32‑bit Y2K38 limitation and the shift to 64‑bit timestamps.
This article reviews Linux virtual memory layouts for 32‑bit and 64‑bit systems, explains the kernel and user address spaces, details how threads consume stack memory, and outlines both virtual‑memory and kernel‑parameter limits that affect the maximum number of threads a process can create.
This article reviews Linux virtual memory layouts for 32‑bit and 64‑bit systems, explains the different memory segments, shows how the default 8 MiB thread stack impacts virtual address consumption, and calculates practical thread limits based on virtual memory and kernel parameters.
The article recounts how Ken Thompson and Dennis Ritchie invented the Unix epoch as a single integer counting seconds since 1970, explains its advantages, exposes the 32‑bit overflow issue known as the Y2K38 problem, and outlines the transition to 64‑bit timestamps in modern systems.
This article recounts how Ken Thompson and Dennis Ritchie devised the Unix Epoch Time as a simple integer timestamp, explains its advantages, the 32‑bit limitation leading to the Y2K38 issue, and describes the transition to 64‑bit timestamps in modern systems.
This article provides a comprehensive overview of the ARMv8 architecture, detailing its 32‑bit and 64‑bit execution states, backward compatibility, key enhancements such as larger register pools and address spaces, and the specific characteristics of ARMv8‑A processors like Cortex‑A53, A57, and A73.
This article provides a comprehensive overview of the ARMv8 architecture, describing its 32‑bit (AArch32) and 64‑bit (AArch64) execution states, the benefits of larger registers and address spaces, and detailed specifications of Cortex‑A53, Cortex‑A57, and Cortex‑A73 processors.
A comprehensive Phoronix benchmark on a Raspberry Pi 400 reveals that the new 64‑bit Raspberry Pi OS consistently outperforms its 32‑bit counterpart, delivering performance gains ranging from modest single‑digit improvements to massive jumps of over 1300% depending on the workload.
This guide explains why Android apps must adopt 64‑bit architectures, outlines market mandates, describes the ABI landscape, shows how to detect missing 64‑bit native libraries with Gradle scripts or the EasyPrivacy plugin, and provides step‑by‑step instructions for updating build configurations, testing, and publishing compliant APKs or App Bundles.
This article explains the relationship and differences among 32‑bit and 64‑bit hardware, operating systems, and applications, covering CPU families, Linux and Windows OS variants, compatibility layers, and how to identify architecture using simple commands.
iQIYI migrated its Android app to 64‑bit by configuring ABI selection, delivering native libraries via universal or split APKs, plugin packages, and a cloud‑based SO distribution platform, adding a front‑end SDK and back‑end publishing service, and applying size‑reduction and hot‑fix optimizations, resulting in faster startup, better performance, and a unified library management workflow.
This guide explains why Google’s 64‑bit requirement forces a React Native upgrade, outlines the benefits of moving to version 0.59.10, and provides step‑by‑step instructions for updating iOS, Android, Babel configuration, native modules, and handling deprecated components and API changes.
The article explains the Unix epoch, how 32‑bit time counters overflow on 19 January 2038 causing the infamous 2038 bug, and why 64‑bit systems extend the range far beyond any realistic horizon, effectively eliminating the problem.
After a recent Bash upgrade on certain servers, SSH logins intermittently failed due to bash’s inability to allocate memory, prompting an investigation that revealed differences in 32‑bit and 64‑bit process memory layouts, exec‑shield behavior, and kernel mmap handling on CentOS 6.5.
