Giter VIP home page Giter VIP logo

alibaba / dragonwell8 Goto Github PK

View Code? Open in Web Editor NEW
4.1K 145.0 488.0 1017.5 MB

Alibaba Dragonwell8 JDK

Home Page: http://dragonwell-jdk.io

License: GNU General Public License v2.0

Makefile 0.25% HTML 0.72% Shell 1.09% M4 0.09% C 6.63% sed 0.01% Perl 0.01% Java 76.23% Batchfile 0.02% Objective-C 0.39% C++ 11.85% JavaScript 1.22% DTrace 0.04% Assembly 0.04% XSLT 0.20% Lex 0.01% Roff 1.16% Python 0.04% Ruby 0.01% Haskell 0.01%
dragonwell8 java openjdk jdk lts java8

dragonwell8's Introduction

Dragonwell Logo

Alibaba Dragonwell8 User Guide

Alibaba Dragonwell8 Extended Edition Release Notes

Alibaba Dragonwell8 Standard Edition Release Notes

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 in-house 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.

The current release supports Linux/x86_64 platform only.

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

Option 1, Download and install pre-built Alibaba Dragonwell
Option 2, Install via YUM

Alibaba Dragonwell is officially supported and maintained in Alibaba Cloud Linux 2 (Aliyun Linux 2) YUM repository, and this repo should be also compatible with Aliyun Linux 17.1, Red Hat Enterprise Linux 7 and CentOS 7.

  • For users running Alibaba Cloud Linux 2 OS, you should be able to install Alibaba Dragonwell by simply running: sudo yum install -y java-1.8.0-alibaba-dragonwell;
  • For users running with aforementioned compatible distros, place a new repository file under /etc/yum.repos.d (e.g.: /etc/repos.d/alinux-plus.repo) with contents as follows, then you should be able to install Alibaba Dragonwell by executing: sudo yum install -y java-1.8.0-alibaba-dragonwell:
# plus packages provided by Aliyun Linux dev team
[plus]
name=AliYun-2.1903 - Plus - mirrors.aliyun.com
baseurl=http://mirrors.aliyun.com/alinux/2.1903/plus/$basearch/
gpgcheck=1
gpgkey=http://mirrors.aliyun.com/alinux/RPM-GPG-KEY-ALIYUN

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.:

=======================================================================
Alibaba Dragonwell is installed to:
    /opt/alibaba/java-1.8.0-alibaba-dragonwell-8.0.0.212.b04-1.al7
You can set Alibaba Dragonwell as default JDK by exporting the
following ENV VARs:
$ export JAVA_HOME=/opt/alibaba/java-1.8.0-alibaba-dragonwell-8.0.0.212.b04-1.al7
$ 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

dragonwell8's People

Contributors

adinn avatar alekseiefimov avatar chrishegarty avatar coffeys avatar coleenp avatar d-d-h avatar dfuch avatar erikj79 avatar gctony avatar gnu-andrew avatar hns avatar jddarcy avatar jerboaa avatar jimlaskey avatar jonathan-gibbons avatar kevinjwalls avatar martinuy avatar mcimadamore avatar michael-mc-mahon avatar mrserb avatar naotoj avatar prrace avatar rwestrel avatar seanjmullan avatar stefank avatar sundararajana avatar szegedi avatar wangweij avatar xueleifan avatar zhengyu123 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dragonwell8's Issues

[Misc] upgrade java -version output to match 222u-b10

Description

dragonwell8 is ready synchronized with openjdk upstream 222u-b10.
java -version should match it.

Steps to Reproduce

Run "java -version"
The output still show that the build is still from 212-b04
Expected behavior
java -version should have the following output

openjdk version "1.8.0_222"
OpenJDK Runtime Environment (Alibaba Dragonwell 8.0.0-b00) (build 1.8.0_222-b10)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell 8.0.0-b00) (build 25.222-b10, mixed mode)

JDK version
latest

Execution environment
any

[GC] Port G1ElasticHeap to dragonwell

Description
New feature G1ElasticHeap to support heap shrink/expansion in runtime.

Steps to Reproduce
Use -XX:+G1ElasticHeap to enable the feature. Detailed instruction will be provided.

Expected behavior
The memory usage of Java process can reduce in runtime.

JDK version
The feature will be provided in Dragonwell 8.1.1-ga(to be determined)

Execution environment

  • Only used in Linux

[JWarmUp] support windows build

Description
Support build Dragonwell on windows platform.
Fix compilation problems in jwarmup module.

Expected behavior
Dragonwell can be built on windows x64

JDK version
Dragonwell 8.2.0

Execution environment

  • OS and version: Windows
  • CPU model: x86-64

get_source_dragonwell.sh: 90: get_source_dragonwell.sh: [[: not found

$ sh get_source_dragonwell.sh 
Check directories
get_source_dragonwell.sh: 90: get_source_dragonwell.sh: [[: not found
get_source_dragonwell.sh: 90: get_source_dragonwell.sh: [[: not found
get_source_dragonwell.sh: 90: get_source_dragonwell.sh: [[: not found
get_source_dragonwell.sh: 90: get_source_dragonwell.sh: [[: not found
get_source_dragonwell.sh: 90: get_source_dragonwell.sh: [[: not found
get_source_dragonwell.sh: 90: get_source_dragonwell.sh: [[: not found
get_source_dragonwell.sh: 90: get_source_dragonwell.sh: [[: not found

[Bug] Alibaba Dragonwell version is not correct.

Description
With java -version, dragonwell version is not correct.

Steps to Reproduce

  1. execute sh make.sh to build dragonwell8
  2. Execute 'java -version' with the built jdk
  3. You will got the following output
openjdk version "1.8.0_202"
OpenJDK Runtime Environment (Dragonwell 8.0-preview) (build 1.8.0_202-b37)
OpenJDK 64-Bit Server VM (Dragonwell 8.0-preview) (build 25.202-b37, mixed mode)

Expected behavior
The java -version should reflect the distro build and upstream build. So the expected output should be

openjdk version "1.8.0_202"
OpenJDK Runtime Environment (Dragonwell 8.0.0-b00) (build 1.8.0_202-b01)
OpenJDK 64-Bit Server VM (Dragonwell 8.0.0-b00) (build 25.202-b01, mixed mode)

JDK version
Any

Execution environment
Any

[Bug] crash:AddNode::Ideal(PhaseGVN*, bool)

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

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fba9132e4ff, pid=1023671, tid=0x00007fb85dd64700
#
# JRE version: OpenJDK Runtime Environment (8.0_202-b30) (build 1.8.0_202-b30)
# Java VM: OpenJDK 64-Bit Server VM (25.202-b30 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x2bf4ff]  AddNode::Ideal(PhaseGVN*, bool)+0x1af
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#

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

$ ./j2sdk-image/bin/java -version ; ./j2sdk-image/bin/java -Xinternalversion
openjdk version "1.8.0_202"
OpenJDK Runtime Environment (Dragonwell 8.0-preview) (build 1.8.0_202-b30)
OpenJDK 64-Bit Server VM (Dragonwell 8.0-preview) (build 25.202-b30, mixed mode)
OpenJDK 64-Bit Server VM (25.202-b30) for linux-amd64 JRE (1.8.0_202-b30), built on Mar 20 2019 18:29:49 by "admin" with gcc 4.4.7

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:
$ cat /etc/issue ; uname -a ; lscpu ; nproc ; free -h
Ubuntu 16.04 LTS \n \l

Linux mathine-ysd 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                144
On-line CPU(s) list:   0-143
Thread(s) per core:    2
Core(s) per socket:    18
Socket(s):             4
NUMA node(s):          4
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 63
Model name:            Intel(R) Xeon(R) CPU E7-8890 v3 @ 2.50GHz
Stepping:              4
CPU MHz:               2499.902
CPU max MHz:           3300.0000
CPU min MHz:           1200.0000
BogoMIPS:              4990.09
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              46080K
NUMA node0 CPU(s):     0-17,72-89
NUMA node1 CPU(s):     18-35,90-107
NUMA node2 CPU(s):     36-53,108-125
NUMA node3 CPU(s):     54-71,126-143
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm xsaveopt cqm_llc cqm_occup_llc dtherm arat pln pts
144
              total        used        free      shared  buff/cache   available
Mem:           503G        8.3G        288G        1.0G        207G        492G
Swap:           19G        369M         18G

[RFC] add document how to compile dragonwell8 from source code

Add document how to compile dragonwell8 from source code

for example, at debian/ubuntu

sudo apt-get install libx11-dev libxext-dev libxrender-dev libxtst-dev libxt-dev libcups2-dev libfreetype6-dev libasound2-dev
chmod +x configure
./configure --prefix=/usr/local --with-freetype-include=/usr/include/freetype2 --with-freetype-lib=/usr/lib/x86_64-linux-gnu

make 
sudo make install

[Bug] crash:PhaseIdealLoop::build_loop_late_post

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

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f4476005d20, pid=1021976, tid=0x00007f4242cec700
#
# JRE version: OpenJDK Runtime Environment (8.0_202-b30) (build 1.8.0_202-b30)
# Java VM: OpenJDK 64-Bit Server VM (25.202-b30 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x83cd20]  PhaseIdealLoop::build_loop_late_post(Node*)+0x130
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

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

$ ./j2sdk-image/bin/java -version ; ./j2sdk-image/bin/java -Xinternalversion
openjdk version "1.8.0_202"
OpenJDK Runtime Environment (Dragonwell 8.0-preview) (build 1.8.0_202-b30)
OpenJDK 64-Bit Server VM (Dragonwell 8.0-preview) (build 25.202-b30, mixed mode)
OpenJDK 64-Bit Server VM (25.202-b30) for linux-amd64 JRE (1.8.0_202-b30), built on Mar 20 2019 18:29:49 by "admin" with gcc 4.4.7

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:
$ cat /etc/issue ; uname -a ; lscpu ; nproc ; free -h
Ubuntu 16.04 LTS \n \l

Linux mathine-ysd 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                144
On-line CPU(s) list:   0-143
Thread(s) per core:    2
Core(s) per socket:    18
Socket(s):             4
NUMA node(s):          4
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 63
Model name:            Intel(R) Xeon(R) CPU E7-8890 v3 @ 2.50GHz
Stepping:              4
CPU MHz:               2499.902
CPU max MHz:           3300.0000
CPU min MHz:           1200.0000
BogoMIPS:              4990.09
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              46080K
NUMA node0 CPU(s):     0-17,72-89
NUMA node1 CPU(s):     18-35,90-107
NUMA node2 CPU(s):     36-53,108-125
NUMA node3 CPU(s):     54-71,126-143
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm xsaveopt cqm_llc cqm_occup_llc dtherm arat pln pts
144
              total        used        free      shared  buff/cache   available
Mem:           503G        8.3G        288G        1.0G        207G        492G
Swap:           19G        369M         18G

OpenJDK 8 broken font rendering e.g. for Google font "Great Vibes"

Platform:
Fedora release 30 (Thirty), Debian GNU/Linux 9.9 (stretch), Ubuntu 18.04, Arch Linux
openjdk version "1.8.0_212"
OpenJDK Runtime Environment (Alibaba Dragonwell 8.0.0-b03) (build 1.8.0_212-b04)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell 8.0.0-b03) (build 25.212-b04, mixed mode)

Architecture:
amd64

Please see the following images for Google font "Great Vibes":

OpenJDK 8 broken font redering:

openjdk-8-font-incorrect

openjdk-8-font-incorrect-marked

OracleJDK 8, OpenJDK 10, 11, 13 correct font rendering:

openjdk-13-font-correct

Example code:

Wrong rendering not visible:

javax.swing.JButton button = new javax.swing.JButton("Open");
java.awt.Font font = new java.awt.Font("Great Vibes", Font.PLAIN, 64);
button.setFont(font);

OpenJDK-8-font-size-128-wrong-rendering-not-visible png

Wrong rendering visible:

javax.swing.JButton button = new javax.swing.JButton("Open");
java.awt.Font font = new java.awt.Font("Great Vibes", Font.PLAIN, 128);
button.setFont(font);

OpenJDK-8-font-size-128-wrong-rendering-visible

As it turned out, it is related to the font version we are using.:

[Bug] compile failed with ubuntu 18.04 + kernel 4.15.0

Creating Makefile ...
make[6]: Warning: File '../shared_dirs.lst' has modification time 4.7 s in the future
Creating flags.make ...
Creating flags_vm.make ...
Creating vm.make ...
Creating adlc.make ...
Creating jvmti.make ...
Creating trace.make ...
Creating sa.make ...
make[6]: warning:  Clock skew detected.  Your build may be incomplete.
make[5]: warning:  Clock skew detected.  Your build may be incomplete.
make[5]: Warning: File 'flags.make' has modification time 5 s in the future
make[6]: Warning: File 'flags.make' has modification time 4.9 s in the future
Compiling /vagrant/hotspot/src/share/vm/adlc/adlparse.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/archDesc.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/arena.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/dfa.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/dict2.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/filebuff.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/forms.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/formsopt.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/formssel.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/main.cpp
Compiling /vagrant/hotspot/src/share/vm/opto/opcodes.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/output_c.cpp
Compiling /vagrant/hotspot/src/share/vm/adlc/output_h.cpp
Making adlc
make[6]: warning:  Clock skew detected.  Your build may be incomplete.
warning: [options] bootstrap class path not set in conjunction with -source 1.6
1 warning
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/jvmtifiles/jvmtiEnv.hpp
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/jvmtifiles/jvmtiEnter.cpp
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/jvmtifiles/jvmtiEnterTrace.cpp
warning: [options] bootstrap class path not set in conjunction with -source 1.6
1 warning
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/jvmtifiles/jvmtiEnvRecommended.cpp
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/jvmtifiles/bytecodeInterpreterWithChecks.cpp
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/jvmtifiles/jvmti.h
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/tracefiles/traceEventClasses.hpp
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/tracefiles/traceEventIds.hpp
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/tracefiles/traceTypes.hpp
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/tracefiles/traceEventControl.hpp
Generating /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/tracefiles/tracePeriodic.hpp
INFO: ENABLE_FULL_DEBUG_SYMBOLS=1
INFO: ALT_OBJCOPY=/usr/bin/objcopy
INFO: /usr/bin/objcopy cmd found so will create .debuginfo files.
INFO: STRIP_POLICY=min_strip
INFO: ZIP_DEBUGINFO_FILES=1
INFO: ENABLE_FULL_DEBUG_SYMBOLS=1
INFO: ALT_OBJCOPY=/usr/bin/objcopy
INFO: /usr/bin/objcopy cmd found so will create .debuginfo files.
INFO: STRIP_POLICY=min_strip
INFO: ZIP_DEBUGINFO_FILES=1
Making /vagrant/build/linux-x86_64-normal-server-release/hotspot/linux_amd64_compiler2/product/../generated/sa-jdi.jar
warning: [options] bootstrap class path not set in conjunction with -source 1.6
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
Warning: generation and use of skeletons and static stubs for JRMP
is deprecated. Skeletons are unnecessary, and static stubs have
been superseded by dynamically generated stubs. Users are
encouraged to migrate away from using rmic to generate skeletons and static
stubs. See the documentation for java.rmi.server.UnicastRemoteObject.

INFO: ENABLE_FULL_DEBUG_SYMBOLS=1
INFO: ALT_OBJCOPY=/usr/bin/objcopy
INFO: /usr/bin/objcopy cmd found so will create .debuginfo files.
INFO: STRIP_POLICY=min_strip
INFO: ZIP_DEBUGINFO_FILES=1
Generating precompiled header precompiled.hpp.gch
In file included from /vagrant/hotspot/src/share/vm/utilities/histogram.hpp:32:0,
                 from /vagrant/hotspot/src/share/vm/runtime/mutex.hpp:30,
                 from /vagrant/hotspot/src/share/vm/classfile/classLoaderData.hpp:32,
                 from /vagrant/hotspot/src/share/vm/oops/typeArrayKlass.hpp:28,
                 from /vagrant/hotspot/src/share/vm/oops/typeArrayOop.hpp:29,
                 from /vagrant/hotspot/src/share/vm/oops/constantPool.hpp:32,
                 from /vagrant/hotspot/src/share/vm/oops/method.hpp:33,
                 from /vagrant/hotspot/src/share/vm/runtime/frame.hpp:28,
                 from /vagrant/hotspot/src/share/vm/code/codeBlob.hpp:30,
                 from /vagrant/hotspot/src/share/vm/code/codeCache.hpp:28,
                 from /vagrant/hotspot/src/cpu/x86/vm/assembler_x86.inline.hpp:30,
                 from /vagrant/hotspot/src/share/vm/asm/assembler.inline.hpp:31,
                 from /vagrant/hotspot/src/share/vm/precompiled/precompiled.hpp:30:
/vagrant/hotspot/src/os/linux/vm/os_linux.inline.hpp: In static member function ‘static dirent* os::readdir(DIR*, dirent*)’:
/vagrant/hotspot/src/os/linux/vm/os_linux.inline.hpp:127:18: error: ‘int readdir_r(DIR*, dirent*, dirent**)’ is deprecated [-Werror=deprecated-declarations]
   if((status = ::readdir_r(dirp, dbuf, &p)) != 0) {
                  ^~~~~~~~~
In file included from /vagrant/hotspot/src/os/linux/vm/jvm_linux.h:44:0,
                 from /vagrant/hotspot/src/share/vm/prims/jvm.h:30,
                 from /vagrant/hotspot/src/share/vm/utilities/debug.hpp:29,
                 from /vagrant/hotspot/src/share/vm/runtime/globals.hpp:28,
                 from /vagrant/hotspot/src/share/vm/memory/allocation.hpp:28,
                 from /vagrant/hotspot/src/share/vm/memory/iterator.hpp:28,
                 from /vagrant/hotspot/src/share/vm/memory/genOopClosures.hpp:28,
                 from /vagrant/hotspot/src/share/vm/oops/klass.hpp:28,
                 from /vagrant/hotspot/src/share/vm/runtime/handles.hpp:28,
                 from /vagrant/hotspot/src/share/vm/memory/universe.hpp:28,
                 from /vagrant/hotspot/src/share/vm/code/oopRecorder.hpp:28,
                 from /vagrant/hotspot/src/share/vm/asm/codeBuffer.hpp:28,
                 from /vagrant/hotspot/src/share/vm/asm/assembler.hpp:28,
                 from /vagrant/hotspot/src/share/vm/precompiled/precompiled.hpp:29:
/usr/include/dirent.h:183:12: note: declared here
 extern int readdir_r (DIR *__restrict __dirp,
            ^~~~~~~~~
In file included from /vagrant/hotspot/src/share/vm/utilities/histogram.hpp:32:0,
                 from /vagrant/hotspot/src/share/vm/runtime/mutex.hpp:30,
                 from /vagrant/hotspot/src/share/vm/classfile/classLoaderData.hpp:32,
                 from /vagrant/hotspot/src/share/vm/oops/typeArrayKlass.hpp:28,
                 from /vagrant/hotspot/src/share/vm/oops/typeArrayOop.hpp:29,
                 from /vagrant/hotspot/src/share/vm/oops/constantPool.hpp:32,
                 from /vagrant/hotspot/src/share/vm/oops/method.hpp:33,
                 from /vagrant/hotspot/src/share/vm/runtime/frame.hpp:28,
                 from /vagrant/hotspot/src/share/vm/code/codeBlob.hpp:30,
                 from /vagrant/hotspot/src/share/vm/code/codeCache.hpp:28,
                 from /vagrant/hotspot/src/cpu/x86/vm/assembler_x86.inline.hpp:30,
                 from /vagrant/hotspot/src/share/vm/asm/assembler.inline.hpp:31,
                 from /vagrant/hotspot/src/share/vm/precompiled/precompiled.hpp:30:
/vagrant/hotspot/src/os/linux/vm/os_linux.inline.hpp:127:42: error: ‘int readdir_r(DIR*, dirent*, dirent**)’ is deprecated [-Werror=deprecated-declarations]
   if((status = ::readdir_r(dirp, dbuf, &p)) != 0) {
                                          ^
In file included from /vagrant/hotspot/src/os/linux/vm/jvm_linux.h:44:0,
                 from /vagrant/hotspot/src/share/vm/prims/jvm.h:30,
                 from /vagrant/hotspot/src/share/vm/utilities/debug.hpp:29,
                 from /vagrant/hotspot/src/share/vm/runtime/globals.hpp:28,
                 from /vagrant/hotspot/src/share/vm/memory/allocation.hpp:28,
                 from /vagrant/hotspot/src/share/vm/memory/iterator.hpp:28,
                 from /vagrant/hotspot/src/share/vm/memory/genOopClosures.hpp:28,
                 from /vagrant/hotspot/src/share/vm/oops/klass.hpp:28,
                 from /vagrant/hotspot/src/share/vm/runtime/handles.hpp:28,
                 from /vagrant/hotspot/src/share/vm/memory/universe.hpp:28,
                 from /vagrant/hotspot/src/share/vm/code/oopRecorder.hpp:28,
                 from /vagrant/hotspot/src/share/vm/asm/codeBuffer.hpp:28,
                 from /vagrant/hotspot/src/share/vm/asm/assembler.hpp:28,
                 from /vagrant/hotspot/src/share/vm/precompiled/precompiled.hpp:29:
/usr/include/dirent.h:183:12: note: declared here
 extern int readdir_r (DIR *__restrict __dirp,
            ^~~~~~~~~
cc1plus: all warnings being treated as errors
/vagrant/hotspot/make/linux/makefiles/vm.make:309: recipe for target 'precompiled.hpp.gch' failed
make[6]: *** [precompiled.hpp.gch] Error 1
make[5]: *** [the_vm] Error 2
/vagrant/hotspot/make/linux/makefiles/top.make:119: recipe for target 'the_vm' failed
/vagrant/hotspot/make/linux/Makefile:297: recipe for target 'product' failed
make[4]: *** [product] Error 2
Makefile:230: recipe for target 'generic_build2' failed
make[3]: *** [generic_build2] Error 2
Makefile:177: recipe for target 'product' failed
make[2]: *** [product] Error 2
HotspotWrapper.gmk:44: recipe for target '/vagrant/build/linux-x86_64-normal-server-release/hotspot/_hotspot.timestamp' failed
make[1]: *** [/vagrant/build/linux-x86_64-normal-server-release/hotspot/_hotspot.timestamp] Error 2
/vagrant//make/Main.gmk:109: recipe for target 'hotspot-only' failed
make: *** [hotspot-only] Error 2
root@ubuntu-bionic:/vagrant# 
root@ubuntu-bionic:/vagrant# uname -a
Linux ubuntu-bionic 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Do we have a workaround to link successfully with only 1GB RAM

This error happened because there's only 1GB RAM on my virtual machine. Other than expanding the memory, do we have a workaround to link successfully with only 1GB RAM?
Thanks!

Linking vm...
collect2: fatal error: ld terminated with signal 9 [Killed]
compilation terminated.
/usr/bin/ld: warning: unrecognized --build-id style ignored.
/usr/bin/objcopy: error: the input file 'libjvm.so' is empty
/root/opensource/dragonwell8/hotspot/make/linux/makefiles/vm.make:340: recipe for target 'libjvm.so' failed
make[6]: *** [libjvm.so] Error 1
make[5]: *** [the_vm] Error 2
make[4]: *** [product] Error 2
make[3]: *** [generic_build2] Error 2
make[2]: *** [product] Error 2
make[1]: *** [/root/opensource/dragonwell8/build/linux-x86_64-normal-server-release/hotspot/_hotspot.timestamp] Error 2
/root/opensource/dragonwell8/hotspot/make/linux/makefiles/top.make:119: recipe for target 'the_vm' failed
/root/opensource/dragonwell8/hotspot/make/linux/Makefile:284: recipe for target 'product' failed
Makefile:230: recipe for target 'generic_build2' failed
Makefile:177: recipe for target 'product' failed
HotspotWrapper.gmk:44: recipe for target '/root/opensource/dragonwell8/build/linux-x86_64-normal-server-release/hotspot/_hotspot.timestamp' failed
/root/opensource/dragonwell8//make/Main.gmk:109: recipe for target 'hotspot-only' failed
make: *** [hotspot-only] Error 2

Add install instructions for Alibaba Cloud Linux 2

Description
Alibaba Cloud Linux 2 already integrated Dragonwell JDK. readme.md should add install instructions for Alibaba Cloud Linux 2.

Steps to Reproduce
Review readme.md.

Expected behavior
Readme.md should contain install instructions for Alibaba Cloud Linux 2

JDK version
Any

Execution environment
Any

[Warning] of online processor count

Description
The testing device is kunlun-9032 with 1024 processors, when I run java program it will report the warning:
OpenJDK 64-Bit Server VM warning: sched_getaffinity failed (Invalid argument)- using online processor count (1024) which may exceed available processors

Expected behavior
the warning may also can reproduce on other jdk versions, but it may not fixed on redhat version, it should be fixed.
seen: https://bugs.openjdk.java.net/browse/JDK-8157478

JDK version
openjdk version "1.8.0_212"
OpenJDK Runtime Environment (Alibaba Dragonwell 8.0.0-b48) (build 1.8.0_212-b04)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell 8.0.0-b48) (build 25.212-b04, mixed mode)

Execution environment

  • OS and version: redhat 7.2
  • Number of CPU cores: 1024
  • Inside Linux container? No

[Bug] Mini-heapdump might be the default mode when FGC happens

Description
Mini-heapdump is the default mode when FGC happens

Steps to Reproduce
Steps to reproduce the behavior:

  1. Specify -XX:+HeapDumpBeforeFullGC
  2. Run the app until FGC

Expected behavior
Full heap dump generated

JDK version
openjdk version "1.8.0_212"
OpenJDK Runtime Environment (Alibaba Dragonwell 8.0.0-b49) (build 1.8.0_212-b04)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell 8.0.0-b49) (build 25.212-b04, mixed mode)

Execution environment

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

[Misc] Update Dragonwell version to 8.1.1

Description
With java -version, dragonwell version is not correct.

Steps to Reproduce

execute sh make.sh to build dragonwell8
Execute 'java -version' with the built jdk
You will got the following output
openjdk version "1.8.0_222"
OpenJDK Runtime Environment (Alibaba Dragonwell 8.0.0-b66) (build 1.8.0_222-b10)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell 8.0.0-b66) (build 25.222-b10, mixed mode)
Expected behavior
The java -version should reflect the distro build and upstream build. So the expected output should be

openjdk version "1.8.0_222"
OpenJDK Runtime Environment (Alibaba Dragonwell 8.1.1-b68) (build 1.8.0_222-b10)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell 8.1.1-b68) (build 25.222-b10, mixed mode)
JDK version
Any

Execution environment
Any

Add ECMAScript6 support in Nashorn

The javascript engine, aka. nashorn in Java8 is ES5 based, ES6 support was added in Java9.
Hope dragonwell can add support of ES6 language features.

Doesn't support windows?

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:

[Bug] Missing commit_message_template for github workflow

Description
Alibaba Dragonwell used to pick up patches directly from Alibaba's internal build whose test/review process is not visible to external users. To better fit into the shoes of github.com while keeping a good shape of code quality, we need a template for git commit messages.

Steps to Reproduce
Steps to reproduce the behavior:

  • Clone Alibaba Dragonwell8 repository [email protected]:alibaba/dragonwell8.git
  • Found no template for git commit -a -t <template>

Expected behavior
git commit -a -t .github/commit_message_template
should give developers a guide on how to write a commit message for Alibaba Dragonwell.

JDK version
Affects preview versions only:
openjdk version "1.8.0_202"
OpenJDK Runtime Environment (Dragonwell 8.0-preview) (build 1.8.0_202-b30)
OpenJDK 64-Bit Server VM (Dragonwell 8.0-preview) (build 25.202-b30, mixed mode)

Execution environment

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

[Bug] crash:Node_Backward_Iterator::next()

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

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f92e7fc545a, pid=1023799, tid=0x00007f90b4d9c700
#
# JRE version: OpenJDK Runtime Environment (8.0_202-b30) (build 1.8.0_202-b30)
# Java VM: OpenJDK 64-Bit Server VM (25.202-b30 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x5da45a]  Node_Backward_Iterator::next()+0x10a
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#

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:

Dragonwell upgrades to jdk8u212-b04

Dragonwell should follow jdk8u upstream and upgrade to jdk8u212-b04. The current dragonewll state is at jdk8u202-b01 that is out of date.

[C1][Windows] Windows x64 build crashed in C1 compiler thread

# JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build 1.8.0_222-b10)
# Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode windows-amd64 compressed oops)
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:

[Bug] crash:SuperWord::get_pre_loop_end(CountedLoopNode*)

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

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fbaf195dedb, pid=1021938, tid=0x00007fb8bdd64700
#
# JRE version: OpenJDK Runtime Environment (8.0_202-b30) (build 1.8.0_202-b30)
# Java VM: OpenJDK 64-Bit Server VM (25.202-b30 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0xa53edb]  SuperWord::get_pre_loop_end(CountedLoopNode*)+0x6b
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

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:

What's the difference between "Dragonwell" and "Alibaba JDK" ?

Congratulations for finally releasing Dragonwell!!!

I saw the presentation "Extreme Scaling with Alibaba JDK" (recording).

It mentions a bunch of features like Multi-tenant, GCIH, Wisp, JWarmup, ZProfiler. Are they, or will they all eventually be part of Dragonwell?

As far as I understood, not all of the mentioned "Alibaba JDK" features are Java SE 8 compatible. What are your future plans for such features? Will you integrate them into Dragonwell nevertheless (thus making Dragonwell incompatible to Java SE 8), will you maintain an extra version/branch with such features or do you not plan to bring such features into Dragonwell at all?

Please don't get me wrong. I like all the mentioned "Alibaba JDK" features and I'd love to see them in Dragonwell (or any other open source, OpenJDK version).

Thanks,
Volker

java -version should match 212u-b04

Description
dragonwell8 is ready synchronized with openjdk upstream 212u-b04. java -version should match it.

Steps to Reproduce

  1. Run "java -version"
  2. The output still show that the build is still from 202-b01

Expected behavior
java -version should have the following output

openjdk version "1.8.0_212"
OpenJDK Runtime Environment (Alibaba Dragonwell 8.0.0-b00) (build 1.8.0_212-b04)
OpenJDK 64-Bit Server VM (Alibaba Dragonwell 8.0.0-b00) (build 25.212-b04, mixed mode)

JDK version
latest

Execution environment
any

[Bug] Build doesn't include Dragonwell information with configure/make.

Description
Build doesn't include Dragonwell information with configure/make.

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:

[JWarmUp] port JWarmUp to mac os

Description
Port JWarmUp to mac os.

Expected behavior
Dragonwell can be built on mac os.

Execution environment

  • OS and version: mac os
  • CPU model: x86-64

[Bug] VM crash at concurrent marking

Description

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f27f207ba44, pid=10448, tid=0x00007f27d52fe700
#
# JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build 1.8.0_222-b10)
# Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x4a1a44]  CMBitMapClosure::do_bit(unsigned long)+0xd4
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread (0x00007f27dc02b800):  ConcurrentGCThread [stack: 0x00007f27d51fe000,0x00007f27d52ff000] [id=10460]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0000000000000010

Registers:
RAX=0x00007f27f2bff860, RBX=0x00007f27dc032fe0, RCX=0x0000000000000003, RDX=0x0000000000000001
RSP=0x00007f27d52fdcb0, RBP=0x00007f27d52fdcd0, RSI=0x000000001341b078, RDI=0x0000000000000008
R8 =0x00007f27d5400000, R9 =0x00000000004d0800, R10=0x0000000002680000, R11=0x0000000000000202
R12=0x00007f27d52fdd30, R13=0x000000079a0d83c0, R14=0x00007f27f2c1e824, R15=0x00007f27dc032fe0
RIP=0x00007f27f207ba44, EFLAGS=0x0000000000010202, CSGSFS=0x0000000000000033, ERR=0x0000000000000004
  TRAPNO=0x000000000000000e

Top of Stack: (sp=0x00007f27d52fdcb0)
0x00007f27d52fdcb0:   0000000013420000 000000079a100000
0x00007f27d52fdcc0:   00007f27dc028e50 000000001341b078
0x00007f27d52fdcd0:   00007f27d52fddd0 00007f27f2077af0
0x00007f27d52fdce0:   00007f27dc02c850 00000001dc02c828
0x00007f27d52fdcf0:   4024000000000000 3fe0000000000000
0x00007f27d52fdd00:   00007f27dc0330f0 0100000000000000
0x00007f27d52fdd10:   00007f27dc028e68 00007f27d52fdd30
0x00007f27d52fdd20:   00007f27d52fdd90 00007f27f24c05cc
0x00007f27d52fdd30:   00007f27f2bd1390 00007f27dc028e50
0x00007f27d52fdd40:   00007f27dc028d70 00007f27dc032fe0
0x00007f27d52fdd50:   00007f27f2bd0d70 0000000000009c00
0x00007f27d52fdd60:   00007f27dcc17450 00007f27f2bdae20
0x00007f27d52fdd70:   0000000000000000 00007f27d52fdd50
0x00007f27d52fdd80:   00007f27dc028d70 0000000000870d00
0x00007f27d52fdd90:   00007f27dc032fe0 0000000000000008
0x00007f27d52fdda0:   0000000000000000 00007f27dc032fe0
0x00007f27d52fddb0:   00007f27d53fed00 00007f27dc02bc30
0x00007f27d52fddc0:   00007f27f2c2d7e0 00007f27f2bedbb0
0x00007f27d52fddd0:   00007f27d52fde60 00007f27f207d261
0x00007f27d52fdde0:   00007f27f2bd0dd0 00000000000003d8
0x00007f27d52fddf0:   00007f27dc02c058 00007f27dc02bc80
0x00007f27d52fde00:   0000000000000000 400a116a8b8f14db
0x00007f27d52fde10:   00000000dc02b140 00007f27dc02bc70
0x00007f27d52fde20:   40108a9e6eeb7026 40115f93ff25e56d
0x00007f27d52fde30:   00007f27d52fde60 00007f27dc02b140
0x00007f27d52fde40:   00007f27dc02b800 000000000000000e
0x00007f27d52fde50:   00007f27d53fed00 000000000000000e
0x00007f27d52fde60:   00007f27d52fdea0 00007f27f26862da
0x00007f27d52fde70:   00007f27d52fdea0 00007f27dc02cc80
0x00007f27d52fde80:   00007f27dc02cb90 00007f27dc02b800
0x00007f27d52fde90:   00007f27f3a4f040 0000000000000003
0x00007f27d52fdea0:   00007f27d52fdee0 00007f27f24bfb42 

Instructions: (pc=0x00007f27f207ba44)
0x00007f27f207ba24:   5b 41 5c 41 5d 41 5e 83 f0 01 5d c3 48 8d 05 29
0x00007f27f207ba34:   3e b8 00 41 8b 7d 08 8b 48 08 48 d3 e7 48 03 38
0x00007f27f207ba44:   8b 4f 08 83 f9 00 0f 8f 6e ff ff ff 0f 85 8a 00
0x00007f27f207ba54:   00 00 66 2e 0f 1f 84 00 00 00 00 00 48 8b 07 4c 

Register to memory mapping:

RAX=0x00007f27f2bff860: <offset 0x1025860> in /home/tomcat/j2sdk-image/jre/lib/amd64/server/libjvm.so at 0x00007f27f1bda000
RBX=0x00007f27dc032fe0 is an unknown value
RCX=0x0000000000000003 is an unknown value
RDX=0x0000000000000001 is an unknown value
RSP=0x00007f27d52fdcb0 is an unknown value
RBP=0x00007f27d52fdcd0 is an unknown value
RSI=0x000000001341b078 is an unknown value
RDI=0x0000000000000008 is an unknown value
R8 =0x00007f27d5400000 is an unknown value
R9 =0x00000000004d0800 is an unknown value
R10=0x0000000002680000 is an unknown value
R11=0x0000000000000202 is an unknown value
R12=0x00007f27d52fdd30 is an unknown value
R13=0x000000079a0d83c0 is an unknown value
R14=0x00007f27f2c1e824: <offset 0x1044824> in /home/tomcat/j2sdk-image/jre/lib/amd64/server/libjvm.so at 0x00007f27f1bda000
R15=0x00007f27dc032fe0 is an unknown value


Stack: [0x00007f27d51fe000,0x00007f27d52ff000],  sp=0x00007f27d52fdcb0,  free space=1023k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [libjvm.so+0x4a1a44]  CMBitMapClosure::do_bit(unsigned long)+0xd4
V  [libjvm.so+0x49daf0]  CMTask::do_marking_step(double, bool, bool)+0x8a0
V  [libjvm.so+0x4a3261]  CMConcurrentMarkingTask::work(unsigned int)+0xd1
V  [libjvm.so+0xaac2da]  GangWorker::loop()+0xca
V  [libjvm.so+0x8e5b42]  java_start(Thread*)+0xf2


---------------  P R O C E S S  ---------------

Steps to Reproduce
Steps to reproduce the behavior:
try following vm options:
-Xms3g -Xmx3g -XX:MaxPermSize=128M -XX:+UseG1GC -XX:+G1ElasticHeap -XX:+ElasticHeapPeriodicUncommit -XX:-UseSplitVerifier -XX:MaxDirectMemorySize=64m

Expected behavior
work well

JDK version
8.1.1GA

Execution environment

  • OS and version: CentOS release 6.9 (Final)
  • CPU model: Intel(R) Xeon(R) Platinum 8163 CPU @ 2.50GHz
  • Number of CPU cores: 4
  • Size of physical memory:
  • Inside Linux container? No
    • Linux container name (docker, pouch, etc):
    • Linux container version:

Two suggestions for building scripts

  1. The following error occurred when executing the get_source_dragonwell.sh -s github command
Cloning into 'dragonwell8-corba'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I know this because I didn't set GitHub SSH public key.
It is suggested that line 66 of get_source_dragonwell.sh be changed from GITURL= "[email protected]:alibaba" to GITURL= "https://github.com/alibaba".
This problem can be solved simply and effectively.

  1. It is suggested to add executable permissions to the configure script.

how to install dragonwell using brew

expected feature:
brew tap dragonwell/dragonwell
brew install dragonwell

ls /Library/Java/JavaVirtualMachines/dragonwell-jdk
...

java -version
...

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.