alibaba / dragonwell11

Alibaba Dragonwell11 JDK

Introduction

Over the years, Java has proliferated in Alibaba. Many applications are written in Java and many our Java developers have written more than one billion lines of Java code.

Alibaba Dragonwell, as a downstream version of OpenJDK, is the OpenJDK implementation at Alibaba optimized for online e-commerce, financial, logistics applications running on 100,000+ servers. Alibaba Dragonwell is the engine that runs these distributed Java applications in extreme scaling.

Alibaba Dragonwell is clearly a "friendly fork" under the same licensing terms as the upstream OpenJDK project. Alibaba is committed to collaborate closely with OpenJDK community and intends to bring as many customized features as possible from Alibaba Dragonwell to the upstream.

Using Alibaba Dragonwell

Alibaba Dragonwell JDK currently supports Linux/x86_64 platform only.

Installation

• You may download a pre-built Alibaba Dragonwell JDK from its GitHub page: https://github.com/dragonwell-project/dragonwell11/releases.
• Uncompress the package to the installation directory.

Enable Alibaba Dragonwell for Java applications

To enable Alibaba Dragonwell JDK for your application, simply set JAVA_HOME to point to the installation directory of Alibaba Dragonwell. If you installed Dragonwell JDK via YUM, follow the instructions prompted from post-install outputs, e.g.:

=======================================================================
# Assuming Alibaba Dragonwell 11 is installed to:
#    /opt/alibaba/java-11-alibaba-dragonwell
# You can set Alibaba Dragonwell as default JDK by exporting following environment variables:
$ export JAVA_HOME=/opt/alibaba/java-11-alibaba-dragonwell
$ export PATH=${JAVA_HOME}/bin:$PATH
=======================================================================

Acknowledgement

Special thanks to those who have made contributions to Alibaba's internal JDK builds.

Publications

Technologies included in Alibaba Dragonwell have been published in following papers

2021

• Yifei Zhang, Tianxiao Gu, Xiaolin Zheng, Lei Yu, Wei Kuai, Sanhong Li Towards a Serverless Java Runtime In ASE 2021 Industry Showcase, to appear

2020

• Mingyu Wu, Ziming Zhao, Yanfei Yang, Haoyu Li, Haibo Chen, Binyu Zang, Haibing Guan, Sanhong Li, Chuansheng Lu, Tongbao Zhang Platinum: A CPU-Efficient Concurrent Garbage Collector for Tail-Reduction of Interactive Services In USENIX ATC 2020, pp. 159–172

2019

• Shiyou Huang, Jianmei Guo, Sanhong Li, Xiang Li, Yumin Qi, Kingsum Chow, Jeff Huang SafeCheck: Safety Enhancement of Java Unsafe API In ICSE 2019, pp. 889–899

2018

• Fangxi Yin, Denghui Dong, Chuansheng Lu, Tongbao Zhang, Sanhong Li, Jianmei Guo, Kingsum Chow Cloud-Scale Java Profiling at Alibaba In ICPE Companion 2018, pp. 99–100

• Fangxi Yin, Denghui Dong, Sanhong Li, Jianmei Guo, Kingsum Chow Java Performance Troubleshooting and Optimization at Alibaba In ICSE-SEIP 2018, pp. 11–12

dragonwell11's Issues

[Misc] Update dragonwell version to 11.0.7.2

Description
This task is update the dragonwell version to 11.0.7.2

Steps to Reproduce

Expected behavior

JDK version

Execution environment

• OS and version:
• CPU model:
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[Misc] Port mini-heapdump to Dragonwell 11

Description
This issue will port following changes to Dragonwell 11
dragonwell-project/dragonwell8_hotspot@422ef9f
dragonwell-project/dragonwell8_hotspot@54fc109
dragonwell-project/dragonwell8_jdk@2bfb91d

Steps to Reproduce
N/A

Expected behavior
Following tests should pass

• test/jdk/tools/
• test/hotspot/jtreg/serviceability/sa/

JDK version
openjdk version "11.0.5.1-preview" 2019-12-24
OpenJDK Runtime Environment (Alibaba Dragonwell) (slowdebug build 11.0.5.1-preview+0)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell) (slowdebug build 11.0.5.1-preview+0, mixed mode)

Execution environment

• OS and version: linux
• CPU model: x64
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[Requirement] add Alpine linux/x86 platform support

Description
A clear and concise description of what the bug is.

Steps to Reproduce
Steps to reproduce the behavior:

1. Save below snippet '...'
2. Compile it with javac '....'
3. Execute with VM options '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

JDK version
The output of java -version command

Execution environment

• OS and version:
• CPU model:
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[GC] Add ZGC tests to pipelines

vmoption --- UseZGC

[Bug] Should remove those installation approaches unavailable in 11.0.5.1-preview

Description
The Aliyun YUM source is unavailable by 2019-12-31, should not display that information to users

Steps to Reproduce
checkout README.md

Expected behavior
contains no Aliyun YUM infomation

JDK version
openjdk version "11.0.5.1-preview" 2019-12-29
OpenJDK Runtime Environment (Alibaba Dragonwell) (build 11.0.5.1-preview+7)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell) (build 11.0.5.1-preview+7, mixed mode)

Execution environment

• OS and version: linux
• CPU model: x64
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container? No
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[Misc] Fix minimal build error

[Enhancement] Support building Dragonwell11 by gcc9.2

On aarch64 N1 platform or newer, gcc9.2 can greatly improve performance.
While there are warnings(as errors) in current code building with gcc9.2. Better to fix them

[Enhancement] Support fastdebug build for Dragonwell11

Description
Support fastdebug build

Steps to Reproduce
run the build shell

Expected behavior
fastdebug version can be successfully built

JDK version
11.0.5.1

Execution environment

• OS and version: Linux
• CPU model: x64
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[Misc] Use version file to mark Alibaba Dragonwell version

Description
Use a separate version file like version.txt

8.275.8.5.5.2

Based on jdk8u 275ga, 8.5.5 internal release number, 2 is an internal build number

版本号不对呀

11打印的版本号仍然是1.8.201的版本呀。

[Bug] Backport 8205921: Optimizing best-of-2 work stealing queue selection

Description
JDK-8205921: Optimizing best-of-2 work stealing queue selection
This enhancement will considerably improve gc performance.

Steps to Reproduce

Expected behavior

JDK version

Execution environment

Window的版本什么时候出？

Dragonwell 8的win版本已经有了，11的版本啥时候出一波？

[Feature request] Any plans to port Wisp2 to dragonwell11?

Hey guys!

Do you have any plans to port Wisp2 from dragonwell8 to 11?
We are very keen to use it, but this is stopping us from adopting it.

Best regards,

[Enhancement] VectorAPI preview

Description
Adding Vector API feature in a preview branch

Merge tag jdk-11.0.9-ga

Description
Merge tag jdk-11.0.9-ga

Steps to Reproduce
N/A

Expected behavior
N/A

JDK version
N/A

Execution environment

• OS and version:
• CPU model:
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

Is Dragonwell 11 TCK certified?

The Dragonwell 8 FAQ states that is TCK certified. The Dragonwell 11 FAQ reads very similar but has no mention of the TCK. I checked the OCTLA Signatories List and "Alibaba Group Holding Limited" is only a signatory for Java SE 8, not for Java SE 9+.

[GC] Minor optimization of ZBarrierSetAssembler, ZReferenceProcess, ZForwardingTableEntry, etc.

8214377: ZGC: Don't use memset to initialize array of ZForwardingTableEntry
8215487: ZGC: ZRuntimeWorkers incorrectly identify themselves as ZWorkers
8215985: ZGC: Simplify reference processing in light of JDK-8175797
8215547: ZGC: Fix incorrect match rule for loadBarrierWeakSlowRegNoVec
8217856: ZGC: Break out C2 matching rules into separate AD file
8216385: ZGC: Fix building without C2
8216372: ZGC: Put C2 load barrier stub routines in separate codeblobs
8213323: sa/TestJmapCoreMetaspace.java and sa/TestJmapCore.java fail with ZGC
8217258: ZGC: Minor cleanup of ZBarrierSetAssembler

@sandlerwang please review 8215547 by checking if VectorAPI are influenced while rxmms are changed
@mmyxym @linade @leveretconey please review the patches that mention your id

Thanks

[Bug] Failed to compile on windows platform

Description

Steps to Reproduce
Run build on windows platform( or use pipeline in http://ci.dragonwell-jdk.io//job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-windows-x64-dragonwell/)

Expected behavior
Pass Build on windows

JDK version
11.0.8.3 GA

Execution environment

• OS and version: Windows
• CPU model: x64
• Number of CPU cores: 4C
• Size of physical memory: 8G
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[JFR] add support for opto object allocations sampling

Add object profiling support in JFR, this feature can help Java developers find hot stacks of creating objects and further improve the performance of Java applications.
In the current version, we only add support for c2.

Caused by: java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11FontManagerat[Bug] A new bug

The problem was resolved after changing the JDK to Oracle

[Misc] Port -XX:ArrayAllocationWarningSize from Dragonwell8

Description
Port following patch from Dragonwell8
dragonwell-project/dragonwell8_hotspot@5677a71

Steps to Reproduce
Steps to reproduce the behavior:

1. not a bug

Expected behavior
All tests from hotspot/jtreg/runtime/memory should pass

JDK version

openjdk version "11.0.5.1-preview" 2019-12-23
OpenJDK Runtime Environment (Alibaba Dragonwell) (build 11.0.5.1-preview+0)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell) (build 11.0.5.1-preview+0, mixed mode)

Execution environment

• OS and version: linux
• CPU model: x64
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

非常期待Windows版本啊！！！

没有Windows版本，就没法在开发环境下使用，因此更不会直接使用Linux版本进行发布了。

所以说Windows版本是敲门砖，只有开发环境可以使用了，那才会在生产环境部署，运行。

之前看也有好几个帖子询问关于Windows版本的问题，近期有发布计划没有？

什么时候放出window版?

什么时候放出window版?

[Misc] Use version file to mark Alibaba Dragonwell version

Description
Use version file like

11.0.9.4.0

base on 11.0.9 ga
4 is Dragonwell release Number
0 is an internal buildNumber

Exception in thread "main" java.lang.AssertionError

When executing the maven packaging command, the following exception was thrown. At first, I thought it was a version problem, and then upgraded to 11.0.7. The result was still the same

maven : 3.6.3
dragonwell : 11.0.7
os : Linux x64

Exception in thread "main" java.lang.AssertionErro
	at jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:155)
	at jdk.compiler/com.sun.tools.javac.util.Assert.check(Assert.java:46)
	at jdk.compiler/com.sun.tools.javac.comp.Modules.enter(Modules.java:247)
	at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.readSourceFile(JavaCompiler.java:837)
	at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$ImplicitCompleter.complete(JavacProcessingEnvironment.java:1529)
	at jdk.compiler/com.sun.tools.javac.code.Symbol.complete(Symbol.java:642)
	at jdk.compiler/com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:1326)
	at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.complete(Type.java:1140)
	at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.getTypeArguments(Type.java:1066)
	at jdk.compiler/com.sun.tools.javac.code.Printer.visitClassType(Printer.java:237)
	at jdk.compiler/com.sun.tools.javac.code.Printer.visitClassType(Printer.java:52)
	at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.accept(Type.java:993)
	at jdk.compiler/com.sun.tools.javac.code.Printer.visit(Printer.java:136)
	at jdk.compiler/com.sun.tools.javac.util.AbstractDiagnosticFormatter.formatArgument(AbstractDiagnosticFormatter.java:199)
	at jdk.compiler/com.sun.tools.javac.util.AbstractDiagnosticFormatter.formatArguments(AbstractDiagnosticFormatter.java:167)
	at jdk.compiler/com.sun.tools.javac.util.BasicDiagnosticFormatter.formatMessage(BasicDiagnosticFormatter.java:111)
	at jdk.compiler/com.sun.tools.javac.util.BasicDiagnosticFormatter.formatMessage(BasicDiagnosticFormatter.java:67)
	at jdk.compiler/com.sun.tools.javac.util.AbstractDiagnosticFormatter.formatArgument(AbstractDiagnosticFormatter.java:185)
	at jdk.compiler/com.sun.tools.javac.util.AbstractDiagnosticFormatter.formatArguments(AbstractDiagnosticFormatter.java:167)
	at jdk.compiler/com.sun.tools.javac.util.BasicDiagnosticFormatter.formatMessage(BasicDiagnosticFormatter.java:111)
	at jdk.compiler/com.sun.tools.javac.util.BasicDiagnosticFormatter.formatMessage(BasicDiagnosticFormatter.java:67)
	at jdk.compiler/com.sun.tools.javac.util.JCDiagnostic.getMessage(JCDiagnostic.java:788)
	at jdk.compiler/com.sun.tools.javac.api.ClientCodeWrapper$DiagnosticSourceUnwrapper.getMessage(ClientCodeWrapper.java:799)
	at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:149)
	at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
	at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785)
	at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:47)

[Bug] mirror links not updated for recent Dragonwell11 releases

Description

The links on wiki are not updated, forgot?

see
https://github.com/alibaba/dragonwell11/wiki/Mirrors-for-download-(%E4%B8%8B%E8%BD%BD%E9%95%9C%E5%83%8F)

Steps to Reproduce
Steps to reproduce the behavior:
Please just checkout the above link;

Expected behavior
A clear and concise description of what you expected to happen.

JDK version
all builds after 11.0.7

Execution environment

• OS and version: Linux
• CPU model: amd64
• Number of CPU cores: 1
• Size of physical memory: 1g
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

is ZGC stable

is ZGC stable?
do you recommend using ZGC in production environment?

wish your response~

dragonwell11 应该不像 dragonwell8 一样 支持 wisp2 吧？？？

似乎 wisp2的参数无效

[Merge] Merge tag 'jdk-11.0.10-ga'

Description
Merge tag 'jdk-11.0.10-ga'

Steps to Reproduce
N/A

Expected behavior
A clear and concise description of what you expected to happen.

JDK version
The output of java -version command

Execution environment

• OS and version:
• CPU model:
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

【question】

dragonwall 11 是否支持warmup 功能

我使用11执行-XX:+CompilationWarmUpRecording -XX:CompilationWarmUpLogfile=/root/jwarmup.log -XX:CompilationWarmUpRecordTime=300 -XX:PrintCompilationWarmUpDetail

stdout：
Unrecognized VM option 'CompilationWarmUpRecording'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

[Bug] Dragonwell PR lacks various checking

Description
Currently Dragonwell PR lacks following checks:

• Comment format, we have defined it in .github/COMMIT_MESSAGE_TEMPLATE, but just enforce it by code review.
• Patch format, such as trailing spaces, etc.;
• Build, sanity test of the patch, we need this at PR level.

Steps to Reproduce
as stated above

Expected behavior
A PR can be merged only if it passes all the checks.

JDK version
11.0.5.1

Execution environment

• OS and version: Linux
• CPU model: x64
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[Misc] Port globals_ext.hpp changes from Dragonwell8 to hold dragonwell specific flags

Description
We'd like to keep Dragonwell specific VM flags in separate header files, typically globals_ext.hpp, to keep it easier for future maintenance. so following patch from Dragonwell-8 has to be ported:
dragonwell-project/dragonwell8_hotspot@1f4185d

Steps to Reproduce
Steps to reproduce the behavior:

1. not a error behavior

Expected behavior
Dragonwell specific VM flags in separate header files

JDK version

openjdk version "11.0.5.1-preview" 2019-12-23
OpenJDK Runtime Environment (Alibaba Dragonwell) (build 11.0.5.1-preview+0)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell) (build 11.0.5.1-preview+0, mixed mode)

Execution environment

• OS and version: linux
• CPU model: x64
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[Bug] medium short time pattern different style in TimePatterns FormatData_zh.java

Description
在文件FormatData_zh.java 中
TimePatterns 下面的 时间风格 不一致, medium 模式采用了24小时样式, 而其他的 full, long, short 都采用了12小时样式.
如下:
{ "TimePatterns",
new String[] {
"ahh'\u65f6'mm'\u5206'ss'\u79d2' z", // full time pattern
"ahh'\u65f6'mm'\u5206'ss'\u79d2'", // long time pattern
"H:mm:ss", // medium time pattern
"ah:mm", // short time pattern
}
},
通过查看其他 中文语言的的 **/ 香港 / 新加坡 发现他们的都是 用 ah / ahh 来表示的.
不知道你们怎么看待这个问题?

其实这个时间格式 官方的 书面的 更多是选择24小时制的, 口语更偏向12小时制的.
也希望能把这个默认的 格式统一切换到24小时制.(其他国家, 例如日本 这里默认就是24小时制的)
切换24小时制 不可取的话,至少把 medium 格式也能统一 为 ahh.

[Bug] Cleartext storage of ldap credentials

Hi this file is storing ldap credentials publicly https://github.com/alibaba/dragonwell11/blob/08bee80218261f41d976c9828fb94fa5fd4e3284/test/jdk/javax/naming/module/src/test/test/ConnectWithAuthzId.java

env.put(Context.PROVIDER_URL, ldapUri.toString());
        env.put(Context.SECURITY_AUTHENTICATION, "simple");
        env.put(Context.SECURITY_PRINCIPAL, "cn=admin,dc=ie,dc=oracle,dc=com");
        env.put(Context.SECURITY_CREDENTIALS, "changeit");
env.put(LdapContext.CONTROL_FACTORIES,

https://docs.oracle.com/javase/jndi/tutorial/ldap/security/ldap.html

username is 'admin' and password is 'changeit'

sensitive information disclosure

[GC] Code Refactoring

8219633: ZGC: Rename ZPageSizeMin to ZGranuleSize

[JFR] Some test failure caused by opto object allocations sampling

Description
Test failure:
TestActiveSettingEvent.java
TestDefaultConfigurations.java

Steps to Reproduce
use jtreg run these tests

Expected behavior
all passed

JDK version
11.0.5.1-preview

Execution environment

• OS and version: Linux
• CPU model: x64
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[Misc] Update Dragonwell11 version to 11.0.10.5

Description
Update Dragonwell11 version to 11.0.10.5

[Bug] transaction autocommit when jdk used in eclipse

JDK Version:Alibaba Dragonwell 11.0.8.3 GA
Eclipse Version: 2019-06 (4.12.0)
when i use jdbc to commit work like this:
connection.setAutoCommit(false);
...
statement.executeBatch();
System.in.read();//when run here, then i click Terminate Button to simulate tcp disconnection to verify how MySQL autorollback
connection.commit();//Something strange happened here,after i clicked the Terminate Button,the code shouldn't do connection.commit()，but it did;the transaction was commited;

i don't know it is jdk's problem or eclipse problem,but i write here.

[Bug] Backport 8204947: Port ShenandoahTaskTerminator to mainline and make it default

Description
JDK-8204947: Port ShenandoahTaskTerminator to mainline and make it default
to improve GC performance

Steps to Reproduce

Expected behavior

JDK version

Execution environment

Merge [GC] ZGC weak processing: redundant code removal

• 8210061: ZGC: Remove STW weak processor mode
• 8210065: ZGC: Remove mode for treating weaks as strong
• 8210714: ZGC: ZWeakRootsIterator should no longer call reset/finish_dead_counter()

[Request] Please add a windows build for dragonwell11

I am wishing and excited to test dragonwell 11 on windows. Please can U release a build . :-)

[Enhancement] make.sh support aarch64

Current make.sh does not support aarch64. It should be fixed.

[GC] ZGC: Increase max heap size to 16TB, etc.

• 8221212: ZGC: Command-line flags should be marked experimental
• 8221219: ZGC: Remove ZStallOnOutOfMemory option
• 8221540: ZGC: Reduce width of zForwardingEntry::from_index field
• 8221153: ZGC: Heap iteration and verification pollutes GC statistics
• 8221146: ZGC: Reports too much relocated
• 8221732: Introduce CollectedHeap::hash_oop()
• 8222180: ZGC: ZForwarding::verify() failing when checking for duplicates
• 8221984: ZGC: Clean up ZOop
• 8222462: Introduce CollectedHeap::unused()
• 8221786: ZGC: Increase max heap size to 16TB

[Bug] Add Dragonwell11 JDK build scripts for Alpine Linux x64 platform

Description
A clear and concise description of what the bug is.

Steps to Reproduce
Steps to reproduce the behavior:

1. Save below snippet '...'
2. Compile it with javac '....'
3. Execute with VM options '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

JDK version
The output of java -version command

Execution environment

• OS and version:
• CPU model:
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[Enhancement] IdealGraph bit check expression canonicalization

Back port of https://bugs.openjdk.java.net/browse/JDK-8247408.
This patch can improve SPECjbb2015 performance

[GC] ZGC backport: improve mark stacks, serviceability, etc.

Backport

• 8207756: ZGC: jstat should show CGC STW phases
• 8209125: ZGC: Clean up ZServiceabilityCounters
• 8209126: ZGC: ZMarkStackAllocator::is_initialized() never called
• 8209127: ZGC: Improve error message when failing to map memory for mark stacks
• 8209375: ZGC: Use dynamic base address for mark stack space
• 8209376: ZGC: Move ZMarkStackAllocator into a separate file
• 8209831: ZGC: Clean up ZRelocationSetSelectorGroup::semi_sort()
• 8209883: ZGC: Compile without C1 broken
• 8209894: ZGC: Cap number of GC workers based on heap size

registry.cn-hangzhou.aliyuncs.com/dragonwell/dragonwell11:11.0.7.2-GA_alpine_x86_64 这个镜像下载不下来

Description
在阿里的镜像服务里查询不到该镜像，也下载docker pull 不下来。

Steps to Reproduce
Steps to reproduce the behavior:

1. Save below snippet '...'
2. Compile it with javac '....'
3. Execute with VM options '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

JDK version
The output of java -version command

Execution environment

• OS and version:
• CPU model:
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[GC] Backport JDK-8217257: ZGC: Minor cleanup of ZBarrierSetC2

Description
Backport JDK-8217257: ZGC: Minor cleanup of ZBarrierSetC2

Merge ZGC root iteration, reference processing, etc.

[GC] 8210881: ZGC: Introduce ZRootsIteratorClosure
[GC] 8210884: ZGC: Remove insertion of filler objects
[GC] 8209163: SA: Show Object Histogram asserts with ZGC
[GC] 8210045: Allow using a subset of worker threads even when UseDynamicNumberOfGCThreads is not set
[GC] 8212181: ZGC: Fix incorrect root iteration in ZHeapIterator
[GC] 8212184: Incorrect oop ref strength used for referents in FinalReference
[GC] 8212921: ZGC: Move verification to after resurrection unblocked
[GC] 8214068: ZGC crashes with vmTestbase/nsk/jdi/ReferenceType/instances/instances004/TestDescription.java
[GC] 8212748: ZGC: Add reentrant locking functionality
[GC] 8214484: ZGC: Exclude SA tests ClhsdbJhisto and TestHeapDumpFor*

Failed to build dragonwell11 on windows

Dragonwell11 can not build on windows, this failure seems also happens in the upstream jdk tip as I reported several days ago, there is no fix on both sides :-(

Env:

* Environment:    cygwin version 3.1.7(0.340/5/3) (root at /cygdrive/f/cygwin64)
* Boot JDK:       java version "10.0.2" 2018-07-17  Java(TM) SE Runtime Environment 18.3 (build 10.0.2+13)  Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.2+13, mixed mode)   (at /cygdrive/f/Java/jdk-10.0.2/)
* Toolchain:      microsoft (Microsoft Visual Studio 2017)
* C Compiler:     Version 19.16.27045 (at /cygdrive/c/progra~2/vsudio/2017/community/vc/tools/msvc/14.16.27023/bin/hostx86/x64/cl)
* C++ Compiler:   Version 19.16.27045 (at /cygdrive/c/progra~2/vsudio/2017/community/vc/tools/msvc/14.16.27023/bin/hostx86/x64/cl)

Failure log:

$ make images
Building target 'images' in configuration 'windows-x86_64-normal-server-release'
Warning: No SCM configuration present and no .src-rev
Compiling 100 properties into resource bundles for java.desktop
Compiling 2996 files for java.base
./src/hotspot/share/compiler/methodMatcher.cpp(264): error C2220: warning treated as error - no 'object' file generated
./src/hotspot/share/compiler/methodMatcher.cpp(264): warning C4778: 'sscanf' : unterminated format string '%255[*\x01\x02\x03\x04\x05\x06\a\b\n\v\f\r\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f!\"#$%&'*+,-0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ\\^_`abcdefghijklmnopqrstuvwxyz{|}~\xe2\x82\xac\xe4\xba\x97\xe5\x84\x8e\xe5\x8e\x97%n'
./src/hotspot/share/compiler/methodMatcher.cpp(264): warning C4474: 'sscanf' : too many arguments passed for format string
./src/hotspot/share/compiler/methodMatcher.cpp(264): note: placeholders and their parameters expect 1 variadic arguments, but 3 were provided
./src/hotspot/share/compiler/methodMatcher.cpp(297): warning C4778: 'sscanf' : unterminated format string '%1022[[);/\x01\x02\x03\x04\x05\x06\a\b\n\v\f\r\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f!\"#$%&'*+,-0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ\\^_`abcdefghijklmnopqrstuvwxyz{|}~\xe2\x82\xac\xe4\xba\x97\xe5\x84\x8e\xe5\x8e%n'
./src/hotspot/share/compiler/methodMatcher.cpp(297): warning C4474: 'sscanf' : too many arguments passed for format string
./src/hotspot/share/compiler/methodMatcher.cpp(297): note: placeholders and their parameters expect 0 variadic arguments, but 2 were provided
make[3]: *** [lib/CompileJvm.gmk:153: /cygdrive/e/dragonwell11/build/windows-x86_64-normal-server-release/hotspot/variant-server/libjvm/objs/methodMatcher.obj] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [make/Main.gmk:272: hotspot-server-libs] Error 2
make[2]: *** Waiting for unfinished jobs....

ERROR: Build failed for target 'images' in configuration 'windows-x86_64-normal-server-release' (exit code 2)

=== Output from failing command(s) repeated here ===
* For target hotspot_variant-server_libjvm_objs_methodMatcher.obj:
methodMatcher.cpp
./src/hotspot/share/compiler/methodMatcher.cpp(264): error C2220: warning treated as error - no 'object' file generated
./src/hotspot/share/compiler/methodMatcher.cpp(264): warning C4778: 'sscanf' : unterminated format string '%255[*\x01\x02\x03\x04\x05\x06\a\b\n\v\f\r\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f!\"#$%&'*+,-0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ\\^_`abcdefghijklmnopqrstuvwxyz{|}~\xe2\x82\xac\xe4\xba\x97\xe5\x84\x8e\xe5\x8e\x97%n'
./src/hotspot/share/compiler/methodMatcher.cpp(264): warning C4474: 'sscanf' : too many arguments passed for format string
./src/hotspot/share/compiler/methodMatcher.cpp(264): note: placeholders and their parameters expect 1 variadic arguments, but 3 were provided
./src/hotspot/share/compiler/methodMatcher.cpp(297): warning C4778: 'sscanf' : unterminated format string '%1022[[);/\x01\x02\x03\x04\x05\x06\a\b\n\v\f\r\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f!\"#$%&'*+,-0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ\\^_`abcdefghijklmnopqrstuvwxyz{|}~\xe2\x82\xac\xe4\xba\x97\xe5\x84\x8e\xe5\x8e%n'
./src/hotspot/share/compiler/methodMatcher.cpp(297): warning C4474: 'sscanf' : too many arguments passed for format string
./src/hotspot/share/compiler/methodMatcher.cpp(297): note: placeholders and their parameters expect 0 variadic arguments, but 2 were provided

* All command lines available in /cygdrive/e/dragonwell11/build/windows-x86_64-normal-server-release/make-support/failure-logs.
=== End of repeated output ===

No indication of failed target found.
Hint: Try searching the build log for '] Error'.
Hint: See doc/building.html#troubleshooting for assistance.

make[1]: *** [/cygdrive/e/dragonwell11/make/Init.gmk:305: main] Error 2
make: *** [/cygdrive/e/dragonwell11/make/Init.gmk:186: images] Error 2