Производитель микросхем памяти Micron Technology (MU.O) заявил в среду, что выйдет из потребительского бизнеса, поскольку компания усиливает внимание на передовых чипах памяти, используемых в дата-центрах искусственного интеллекта, на фоне глобального дефицита этих ключевых компонентов.

Done with parallel compiles: /ix/build/VQEWVWXLpdRDv7B6T8uSq6/src/openjdk-boot/jdk/make/java/java
rm -f /ix/build/VQEWVWXLpdRDv7B6T8uSq6/src/openjdk.build-boot/lib/currency.data
/ix/build/VQEWVWXLpdRDv7B6T8uSq6/src/bootstrap/jdk1.6.0/bin/java -XX:-PrintVMOptions -XX:+UnlockDiagnosticVMOptions -XX:-LogVMOutput -Xmx512m -Xms512m -XX:PermSize=32m -XX:MaxPermSize=160m -jar /ix/build/VQEWVWXLpdRDv7B6T8uSq6/src/openjdk.build-boot/btjars/generatecurrencydata.jar -o /ix/build/VQEWVWXLpdRDv7B6T8uSq6/src/openjdk.build-boot/lib/currency.data.temp \
  < ../../../src/share/classes/java/util/CurrencyData.properties
Error: time is more than 10 years from present: 1420063200000
java.lang.RuntimeException: time is more than 10 years from present: 1420063200000
   at build.tools.generatecurrencydata.GenerateCurrencyData.makeSpecialCaseEntry(GenerateCurrencyData.java:287)
   at build.tools.generatecurrencydata.GenerateCurrencyData.buildMainAndSpecialCaseTables(GenerateCurrencyData.java:226)
   at build.tools.generatecurrencydata.GenerateCurrencyData.main(GenerateCurrencyData.java:157)
   at java.lang.reflect.VMMethod.invoke(Native Method)
   at java.lang.reflect.Method.invoke(Method.java:327)
   at jamvm.java.lang.JarLauncher.main(JarLauncher.java:50)
make[5]: *** [Makefile:346: /ix/build/VQEWVWXLpdRDv7B6T8uSq6/src/openjdk.build-boot/lib/currency.data] Error 1

pg:home# ../hotspot/outputdir/linux_amd64_compiler2/product/gamma
Using java runtime at: /ix/build/ZTejNJErcdJHO2zHaNUZ72/src/openjdk.build-boot/j2sdk-image/jre
OpenJDK 64-Bit Server VM warning: No monotonic clock was available - timed services may be adversely affected if the time-of-day clock changes
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00000000008c9f2d, pid=3319070, tid=140576357940024
#
# JRE version:  (7.0_171-b02) (build )
# Java VM: OpenJDK 64-Bit Server VM (24.171-b02 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea 2.6.13
# Distribution: Custom build (Fri Dec  5 16:08:17 UTC 2025)
# Problematic frame:
# C  [exe+0x6c9f2d]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid3319070.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
#   http://icedtea.classpath.org/bugzilla
#
Aborted

[lua] Failed to run module rulesets callback late_routing: /usr/local/nginx-fl/lua/modules/init.lua:314: attempt to index field 'execute' (a nil value)

if rule_result.action == "execute" then
  rule_result.execute.results = ruleset_results[tonumber(rule_result.execute.results_index)]
end

pg:home# ../hotspot/outputdir/linux_amd64_compiler2/product/gamma -cp ${PWD}/lib/tools.jar com.sun.tools.javac.Main
Using java runtime at: /ix/build/Uj5XWFaXHMN8wk3RuF4XP0/src/openjdk.build-boot/j2sdk-image/jre
Usage: javac <options> <source files>
where possible options include:
  -g                         Generate all debugging info
  -g:none                    Generate no debugging info
  -g:{lines,vars,source}     Generate only some debugging info
  -nowarn                    Generate no warnings

xzone malloc is partly derived from the mimalloc allocator. At the beginning of its development, the design and implementation of mimalloc was used as a starting point that provided solutions to many of the basic/fundamental problems an allocator needs to solve. Many of the concepts and terminology in xzone malloc are inherited from mimalloc:

* mimalloc also reserves virtual memory in segments that have an associated segment metadata array
* mimalloc's finest unit of virtual memory management is also slices
* mimalloc's pages are xzone malloc's chunks
* mimalloc's bins for size classes are the same as xzone malloc's
* mimalloc's heaps are like xzones, managing a set of pages/chunks for allocations of a particular size
* mimalloc tlds are somewhat like xzone malloc's segment groups, in that they maintain span queues of free spans across segments

From that foundation, xzone malloc diverged by adding and changing aspects of the design focusing on its specific security and performance goals.

At the time of this writing (09/25), most of xzone malloc's key security features are not present in mimalloc:

* xzones and segment groups are differentiated from mimalloc's heaps and tlds by their support for bucketed type isolation
* xzone malloc uses a segment table rather than mimalloc's segment bitmap to allow its metadata to be separated from the contents of the heap
* xzone malloc's allocation fronts and guard pages features introduce further obstacles to exploit reliability that there are no direct analogues for in mimalloc
mimalloc does not support ARM MTE