head 1.4; access; symbols pkgsrc-2026Q1:1.4.0.78 pkgsrc-2026Q1-base:1.4 pkgsrc-2025Q4:1.4.0.76 pkgsrc-2025Q4-base:1.4 pkgsrc-2025Q3:1.4.0.74 pkgsrc-2025Q3-base:1.4 pkgsrc-2025Q2:1.4.0.72 pkgsrc-2025Q2-base:1.4 pkgsrc-2025Q1:1.4.0.70 pkgsrc-2025Q1-base:1.4 pkgsrc-2024Q4:1.4.0.68 pkgsrc-2024Q4-base:1.4 pkgsrc-2024Q3:1.4.0.66 pkgsrc-2024Q3-base:1.4 pkgsrc-2024Q2:1.4.0.64 pkgsrc-2024Q2-base:1.4 pkgsrc-2024Q1:1.4.0.62 pkgsrc-2024Q1-base:1.4 pkgsrc-2023Q4:1.4.0.60 pkgsrc-2023Q4-base:1.4 pkgsrc-2023Q3:1.4.0.58 pkgsrc-2023Q3-base:1.4 pkgsrc-2023Q2:1.4.0.56 pkgsrc-2023Q2-base:1.4 pkgsrc-2023Q1:1.4.0.54 pkgsrc-2023Q1-base:1.4 pkgsrc-2022Q4:1.4.0.52 pkgsrc-2022Q4-base:1.4 pkgsrc-2022Q3:1.4.0.50 pkgsrc-2022Q3-base:1.4 pkgsrc-2022Q2:1.4.0.48 pkgsrc-2022Q2-base:1.4 pkgsrc-2022Q1:1.4.0.46 pkgsrc-2022Q1-base:1.4 pkgsrc-2021Q4:1.4.0.44 pkgsrc-2021Q4-base:1.4 pkgsrc-2021Q3:1.4.0.42 pkgsrc-2021Q3-base:1.4 pkgsrc-2021Q2:1.4.0.40 pkgsrc-2021Q2-base:1.4 pkgsrc-2021Q1:1.4.0.38 pkgsrc-2021Q1-base:1.4 pkgsrc-2020Q4:1.4.0.36 pkgsrc-2020Q4-base:1.4 pkgsrc-2020Q3:1.4.0.34 pkgsrc-2020Q3-base:1.4 pkgsrc-2020Q2:1.4.0.30 pkgsrc-2020Q2-base:1.4 pkgsrc-2020Q1:1.4.0.10 pkgsrc-2020Q1-base:1.4 pkgsrc-2019Q4:1.4.0.32 pkgsrc-2019Q4-base:1.4 pkgsrc-2019Q3:1.4.0.28 pkgsrc-2019Q3-base:1.4 pkgsrc-2019Q2:1.4.0.26 pkgsrc-2019Q2-base:1.4 pkgsrc-2019Q1:1.4.0.24 pkgsrc-2019Q1-base:1.4 pkgsrc-2018Q4:1.4.0.22 pkgsrc-2018Q4-base:1.4 pkgsrc-2018Q3:1.4.0.20 pkgsrc-2018Q3-base:1.4 pkgsrc-2018Q2:1.4.0.18 pkgsrc-2018Q2-base:1.4 pkgsrc-2018Q1:1.4.0.16 pkgsrc-2018Q1-base:1.4 pkgsrc-2017Q4:1.4.0.14 pkgsrc-2017Q4-base:1.4 pkgsrc-2017Q3:1.4.0.12 pkgsrc-2017Q3-base:1.4 pkgsrc-2017Q2:1.4.0.8 pkgsrc-2017Q2-base:1.4 pkgsrc-2017Q1:1.4.0.6 pkgsrc-2017Q1-base:1.4 pkgsrc-2016Q4:1.4.0.4 pkgsrc-2016Q4-base:1.4 pkgsrc-2016Q3:1.4.0.2 pkgsrc-2016Q3-base:1.4 pkgsrc-2016Q2:1.3.0.8 pkgsrc-2016Q2-base:1.3 pkgsrc-2016Q1:1.3.0.6 pkgsrc-2016Q1-base:1.3 pkgsrc-2015Q4:1.3.0.4 pkgsrc-2015Q4-base:1.3 pkgsrc-2015Q3:1.3.0.2 pkgsrc-2015Q3-base:1.3 pkgsrc-2015Q2:1.2.0.4 pkgsrc-2015Q2-base:1.2 pkgsrc-2015Q1:1.2.0.2 pkgsrc-2015Q1-base:1.2; locks; strict; comment @// @; 1.4 date 2016.08.15.19.09.38; author ryoon; state Exp; branches; next 1.3; commitid 4Ay4SVgP0rsg1riz; 1.3 date 2015.07.03.20.40.59; author fhajny; state Exp; branches; next 1.2; commitid hLfEJ7NShOl8FSry; 1.2 date 2015.03.02.03.53.26; author tnn; state Exp; branches; next 1.1; commitid EXGSR4O4Qqkx2Zby; 1.1 date 2015.03.01.21.43.50; author tnn; state Exp; branches; next ; commitid qyYlKBfk4BJXZWby; desc @@ 1.4 log @Update to 1.8.102 Changelog: IANA Data 2016d JDK 8u102 contains IANA time zone data version 2016d. For more information, refer to Timezone Data Versions in the JRE Software. See JDK-8151876 Enhancements core-libs/java.lang.invoke Internal package sun.invoke.anon has been removed The internal package sun.invoke.anon has been removed. The functionality it used to provide, namely anonymous class loading with possible constant pool patches, is available via the Unsafe.defineAnonymousClass() method. See JDK-8081512 hotspot/runtime New property jdk.lang.processReaperUseDefaultStackSize When a large TLS (Thread local storage) size is set for Threads, the JVM results in a stack overflow exception. The reason for this behavior is that the reaper thread was created with a low stack size of 32768k. When a large TLS size is set, it steals space from the threads stack, which eventually results in a stack overflow. This is a known glibc bug. To overcome this issue, we have introduced a workaround (jdk.lang.processReaperUseDefaultStackSize) in which the user can set the reaper threads stack size to a default instead of to 32768. This gives the reaper thread a bigger stack size, so for a large TLS size, such as 32k, the process will not fail. Users can set this flag in one of two ways: 1. -Djdk.lang.processReaperUseDefaultStackSize=true 2. System.setProperty("jdk.lang.processReaperUseDefaultStackSize", "true") The problem has been observed only when JVM is started from JNI code in which TLS is declared using "__thread" See JDK-8130425 hotspot/compiler Implemented performance improvements for BigInteger.montgomeryMultiply We have implemented improvements that will improve performance of several security algorithms, especially when using ciphers with key lengths of 2048-bit or greater. To turn on these improvements, use the options -XX:+UseMontgomeryMultiplyIntrinsic and -XX:+UseMontgomerySquareIntrinsic. This improvement is only for Linux and Solaris on x86_64 architecture. See JDK-8130150 Changes security-libs/javax.crypto MSCAPI KeyStore can handle same-named certificates Java SE KeyStore does not allow certificates that have the same aliases (http://docs.oracle.com/javase/8/docs/api/java/security/KeyStore.html). However, on Windows, multiple certificates stored in one keystore are allowed to have non-unique friendly names.The fix for JDK-6483657 makes it possible to operate on such non-uniquely named certificates through the Java API by artificially making the visible aliases unique. Please note, this fix does not enable creating same-named certificates with the Java API. It only allows you to deal with same-named certificates that were added to the keystore by 3rd party tools. It is still recommended that your design not use multiple certificates with the same name. In particular, the following sentence will not be removed from the Java documentation: "In order to avoid problems, it is recommended not to use aliases in a KeyStore that only differ in case." (http://docs.oracle.com/javase/8/docs/api/java/security/KeyStore.html) See JDK-6483657 security-libs/javax.net.ssl Modify requirements on Authority Key Identifier extension field during X509 certificate chain building The requirement to have the Authority Key Identifier (AKID) and Subject Key Identifier (SKID) fields matching when building X509 certificate chains has been modified for some cases. See JDK-8072463 hotspot/gc Providing more granular levels for GC verification This enhancement provides a way to specify more granular levels for the GC verification enabled using the VerifyBeforeGC, VerifyAfterGC, and VerifyDuringGC diagnostic options. It introduces a new diagnostic option VerifySubSet with which one can specify the subset of the memory system that should be verified. With this new option, one or more sub-systems can be specified in a comma separated string. Valid memory sub-systems are: threads, heap, symbol_table, string_table, codecache, dictionary, classloader_data_graph, metaspace, jni_handles, c-heap, and codecache_oops. During the GC verification, only the sub-systems specified using VerifySubSet get verified: D:\\tests>java -XX:+UnlockDiagnosticVMOptions -XX:+VerifyBeforeGC -XX:VerifySubSet="threads,c-heap" -Xlog:gc+verify=debug Test [0.095s][debug ][gc,verify] Threads [0.099s][debug ][gc,verify] C-heap [0.105s][info ][gc,verify] Verifying Before GC (0.095s, 0.105s) 10.751ms [0.120s][debug ][gc,verify] Threads [0.124s][debug ][gc,verify] C-heap [0.130s][info ][gc,verify] Verifying Before GC (0.120s, 0.130s) 9.951ms [0.148s][debug ][gc,verify] Threads [0.152s][debug ][gc,verify] C-heap If any invalid memory sub-systems are specified with VerifySubSet, the Java process exits with the following error message: D:\\tests>java -XX:+UnlockDiagnosticVMOptions -XX:+VerifyBeforeGC -XX:VerifySubSet="threads,c-heap,hello" -Xlog:gc+verify=debug oom Error occurred during initialization of VM VerifySubSet: 'hello' memory sub-system is unknown, please correct it See JDK-8072725 hotspot/compiler Removed PICL warning message In 8u40 and 7u80, a new feature was introduced to use the PICL library on Solaris to get some system information. If this library was not found, we printed an error message: Java HotSpot(TM) Server VM warning: PICL (libpicl.so.1) is missing. Performance will not be optimal. This warning was misleading. Not finding the PICL library is a very minor issue, and the warnings mostly lead to confusion. In this release, the warning was removed. See JDK-8144957 core-libs/javax.naming Improved exception handling for bad LDAP referral replies The JDK was throwing a NullPointerException when a non-compliant REFERRAL status result was sent but no referral values were included. With this change, a NamingException with message value of "Illegal encoding: referral is empty" will be thrown in such circumstances. See JDK-8149450 and JDK-8154304 Bug Fixes The following are some of the notable bug fixes included in this release: security-libs/javax.net.ssl Fix to resolve "Unable to process PreMasterSecret, may be too big" issue Recent JDK updates introduced an issue for applications that depend on having a delayed provider selection mechanism. The issue was introduced in JDK 8u71, JDK 7u95 and JDK 6u111. The main error seen corresponded to an exception like the following : handling exception: javax.net.ssl.SSLProtocolException: Unable to process PreMasterSecret, may be too big See JDK-8149017 This release also contains fixes for security vulnerabilities described in the Oracle Java SE Critical Patch Update Advisory. For a more complete list of the bug fixes included in this release, see the JDK 8u102 Bug Fixes page. @ text @$NetBSD$ --- hotspot/src/share/vm/utilities/globalDefinitions_gcc.hpp.orig 2016-08-11 05:37:42.000000000 +0000 +++ hotspot/src/share/vm/utilities/globalDefinitions_gcc.hpp @@@@ -30,12 +30,16 @@@@ // This file holds compiler-dependent includes, // globally used constants & types, class (forward) // declarations and a few frequently used utility functions. -#if defined(LINUX) || defined(_ALLBSD_SOURCE) +#if defined(LINUX) || defined(_ALLBSD_SOURCE) || defined(SOLARIS) #ifndef __STDC_LIMIT_MACROS #define __STDC_LIMIT_MACROS #endif // __STDC_LIMIT_MACROS #endif +#ifdef SOLARIS +#include +#endif // SOLARIS + #include #include #include @ 1.3 log @Add support for building with GCC on SunOS, largely based on openjdk7 patches by jesse et al. Fixes build on SunOS. @ text @d1 1 a1 1 $NetBSD: patch-hotspot_src_share_vm_utilities_globalDefinitions__gcc.hpp,v 1.2 2015/03/02 03:53:26 tnn Exp $ d3 1 a3 1 --- hotspot/src/share/vm/utilities/globalDefinitions_gcc.hpp.orig 2015-02-02 15:32:37.000000000 +0000 d5 2 a6 1 @@@@ -31,6 +31,10 @@@@ d9 6 a22 9 @@@@ -76,7 +76,7 @@@@ # include # endif -#if defined(LINUX) || defined(_ALLBSD_SOURCE) +#if defined(LINUX) || defined(_ALLBSD_SOURCE) || defined(SOLARIS) #ifndef __STDC_LIMIT_MACROS #define __STDC_LIMIT_MACROS #endif // __STDC_LIMIT_MACROS @ 1.2 log @- put -D__STDC_LIMIT_MACROS on command line instead of patching it everywhere - don't use ALT_JDK_IMPORT_PATH on SunOS, just build like on other platforms - regen all bootstraps to facilitate removal of the +UseSerialGC hacks - bootstrap binaries on FTP are now PGP signed - remove a handful of obsolete patches @ text @d1 1 a1 1 $NetBSD$ d5 11 @ 1.1 log @Rototil include order so stdint doesn't get included without the necessary feature test macros. Should fix "UINTPTR_MAX not declared" error. @ text @d5 1 a5 18 @@@@ -31,6 +31,16 @@@@ // globally used constants & types, class (forward) // declarations and a few frequently used utility functions. +#ifndef __STDC_CONSTANT_MACROS +#define __STDC_CONSTANT_MACROS +#endif +#ifndef __STDC_FORMAT_MACROS +#define __STDC_FORMAT_MACROS +#endif +#ifndef __STDC_LIMIT_MACROS +#define __STDC_LIMIT_MACROS +#endif + #include #include #include @@@@ -76,10 +86,7 @@@@ a9 3 -#ifndef __STDC_LIMIT_MACROS -#define __STDC_LIMIT_MACROS -#endif // __STDC_LIMIT_MACROS d11 3 a13 3 #include #include #ifndef __OpenBSD__ @