From tongbao.ztb at alibaba-inc.com Mon Dec 2 09:43:23 2019 From: tongbao.ztb at alibaba-inc.com (Tongbao Zhang) Date: Mon, 02 Dec 2019 17:43:23 +0800 Subject: =?UTF-8?B?5Zue5aSN77yaTXVsdGktc3Vydml2b3Igc3VwcG9ydCBmb3IgU1ZNIEdD?= In-Reply-To: References: Message-ID: Hello Graal developers, I have submit a PR here: https://github.com/oracle/graal/pull/1912 Look forward to your response. Thanks, Tongbao ------------------------------------------------------------------ ???????(??) ?????2019?11?22?(???) 21:24 ????graal-dev ????Multi-survivor support for SVM GC Dear Graal developers, Substrate VM is a great framework to generate executable native images for Java applications. Thank you for making it open-source. We (Alibaba) are trying to use Substrate VM and native-image to speed up the startup of our cloud-based Java applications. Meantime, we also found problems when running our applications using SVM. The full GC occurred more frequently than the HotSpot VM because there are no object age and survivor spaces in the current SVM GC implementation. We made some improvements to the SVM GC to address these problems, which can significantly decrease the full GC frequency. We would like to contribute a patch to the community, including the multi-survivor support of SVM builtin GC to reduce the frequency of full GC. We have tested this patch thoroughly in our production environment and are glad to contribute it to the Graal community. Look forward to your response. Thanks, Tongbao Zhang From thomas.wuerthinger at oracle.com Mon Dec 2 09:59:36 2019 From: thomas.wuerthinger at oracle.com (Thomas Wuerthinger) Date: Mon, 2 Dec 2019 10:59:36 +0100 Subject: Multi-survivor support for SVM GC In-Reply-To: References:

Message-ID: <36D3E8FF-222F-4D93-B19D-E113088D0D43@oracle.com> Hi Tongbao! Thanks for the PR! Can you add some higher level description to https://github.com/oracle/graal/pull/1912 ? Also, do you have any benchmark numbers that show which scenarios are performing differently with this patch? - thomas > On 2 Dec 2019, at 10:43, Tongbao Zhang wrote: > > Hello Graal developers, > > I have submit a PR here: > https://github.com/oracle/graal/pull/1912 > > Look forward to your response. > Thanks, > Tongbao > > > ------------------------------------------------------------------ > ???????(??) > ?????2019?11?22?(???) 21:24 > ????graal-dev > ????Multi-survivor support for SVM GC > > Dear Graal developers, > > Substrate VM is a great framework to generate executable native images for Java applications. Thank you for making it open-source. > We (Alibaba) are trying to use Substrate VM and native-image to speed up the startup of our cloud-based Java applications. > > Meantime, we also found problems when running our applications using SVM. > The full GC occurred more frequently than the HotSpot VM because there are no object age and survivor spaces in the current SVM GC implementation. > > We made some improvements to the SVM GC to address these problems, which can significantly decrease the full GC frequency. > We would like to contribute a patch to the community, including the multi-survivor support of SVM builtin GC to reduce the frequency of full GC. > We have tested this patch thoroughly in our production environment and are glad to contribute it to the Graal community. > > Look forward to your response. > > Thanks, > Tongbao Zhang From lists at fniephaus.com Mon Dec 2 10:27:13 2019 From: lists at fniephaus.com (Fabio Niephaus) Date: Mon, 2 Dec 2019 11:27:13 +0100 Subject: ECOOP'20 Berlin - Call for Papers Message-ID: ============================================================ The 34th Edition of ECOOP Call for Papers 13th-17th July 2020 Berlin, Germany https://2020.ecoop.org/ ============================================================ ECOOP is a conference about programming. Originally its primary focus was on object orientation, but now it looks at a much broader range of programming topics. Areas of interest include, at least, the design, implementation, optimization, analysis, and theory of programs, programming languages, and programming environments. It solicits both innovative and creative solutions to real problems as well as evaluations of existing solutions?evaluations that provide new insights. It also encourages the submission of reproduction studies. ECOOP 2020 solicits high-quality submissions describing original, unpublished results. The program committee will evaluate the technical contribution of each submission as well as its general relevance and accessibility to the ECOOP audience according to the following criteria: - Originality. Papers must present new ideas and place them appropriately within the context established by previous research in the field. - Significance. The results in the paper must have the potential to add significantly to the state of the art or practice. - Evidence. The paper must present evidence supporting its claims. Examples of evidence include implemented systems, experimental results, statistical analyses, case studies, formalizations, and proofs. - Clarity. The paper must present its contributions and results clearly. On submission, authors will be asked to identify their paper with one of the following categories: - Research Paper. This is the most traditional category and solicits high quality research papers that demonstrate advances in the field. (As an alternative to being published in the conference proceedings, authors may wish to submit research papers to be considered for publication in ACM TOPLAS or Science of Computer Programming.) - Tool Insights Paper. These submissions focus on the practical details of the design and implementation of PL tools?details that are often omitted from regular research papers, despite being fascinating and worthy of communication. A strong Tool Insights Paper should communicate engineering experience and insights that are likely to be useful to other members of the PL community, who may face similar problems in future. Examples of issues that Tool Insights Papers might focus on include, but are not limited to: performance, reliability, portability, inter-tool integration, infrastructure re-use, evaluation issues, theory/practice gaps, precision/efficiency, and soundness/efficiency trade-offs. - Reproduction Study. A Reproduction Study is an empirical evaluation. It reconstructs an already published experiment but in a different context (for example, using a different virtual machine or platform, or in a different class of applications) in order to validate or refute important results of earlier work. A good Reproduction Study includes thorough empirical evaluation as well as a detailed comparison with the previous results, providing reasons for possible disagreements. (A thoroughly-conducted Reproduction Study that perfectly replicates an existing experiment and reaches the same conclusions will be regarded as significant, so long as said experiment is significant enough to be worthy of reproduction.) - Experience Report. Such reports focus on noteworthy applications of known PL techniques, tools, and ideas in interesting domains and by other communities. Examples include, but are not limited to, applications of PL techniques in industry, open source, education, and other academic disciplines. We welcome reports on successful applications of PL ideas and reports that shed light on limitations and problems that may provide inspiration for future research. - Pearl. This category solicits articles that explain a known idea in a new and elegant way, to the benefit of the PL community. A Pearl may well be shorter than a regular research paper, but there is no hard requirement on this. - Brave New Idea. The Brave New Idea category solicits forward-looking articles on ideas in the field of PL that may take some time to substantiate, but for which early communication to the community is likely to be of benefit. For this category we welcome papers that are particularly conceptually novel or unconventional and that as a result may be harder to back up by traditional evaluation methods. A Brave New Idea paper may well be shorter than a regular research paper, but there is no requirement for it to be so. Paper Submission ================ Only papers that have not been published and are not under review for publication elsewhere may be submitted. Double submissions will be rejected without review. If major parts of an ECOOP submission have appeared elsewhere in any form, authors are required to notify the ECOOP program chair and explain the overlap and relationship. Authors are also required to inform the program chair about closely related work submitted to another conference while the ECOOP submission is under review. Papers must be no longer than 25 pages, excluding references. See below for information about appendices. Authors will not be penalized for papers that are shorter than the page limit. Submissions will be carried out electronically via the conference website [1]. ECOOP Proceedings are published by Dagstuhl LIPIcs. Papers must be written in English and follow the Dagstuhl LIPIcs LaTeX-style template [2]. Authors retain ownership of their content. Note: Submitted papers do not need to include the ACM classification or keywords. Also, please DO NOT put your name in either the \author or \Copyright macro, in order to maintain anonymity for double-blind reviewing (see below). Anonymity ========= ECOOP will use light double-blind reviewing: authors? identities are withheld until a reviewer submits his or her review (as usual, reviews are anonymous). To facilitate this, submitted papers must adhere to two rules: - Author names and institutions must be omitted. - References to authors? own other work should be in the third person (for example, not ?We build on our previous work?? but rather ?We build on the work of??). When in doubt, contact the Program Chair. Additional Material =================== Clearly marked additional appendices containing analyses, statistics, supporting proofs, etc. of possible value to reviewers but not published in the final publication, may be included beyond the page limit. The submission system provides an option to submit supplementary material; for example, a technical report including proofs, or web pages and repositories that cannot easily be anonymized. This supplementary material will be made available to reviewers after the initial reviews have been completed, when author names are revealed. Reviewers are under no obligation to examine such appendices and supplementary material. Therefore, the paper must be a stand-alone document - the appendices and supplementary material are a way of providing useful information that cannot fit in the page limit; they are not a means to extend the page limit. Authors of papers that have been submitted but not accepted by previous conferences may optionally submit a Note to Reviewers. The Note to Reviewers should provide the following information: - the identity of the previous venue(s) (for example, ESOP 2020, ?Programming? 2020, POPL 2020, OOPSLA 2019) - a list the major issues identified by the reviews at those venues - a description of the changes made to the paper in response to those reviews These notes will be made available to reviewers after their initial reviews have been completed and author names have been revealed. Response Period =============== Authors will be given a three-day period to read and respond to the reviews of their papers before the program committee meeting. Responses have no formal length limit, but concision is likely to be effective. Artifact Evaluation =================== To reward the creation of artifacts and support replication of experiments, authors of accepted research papers may submit artifacts (such as tools, data, models, or videos) to be evaluated by an Artifact Evaluation Committee. Artifacts that pass muster will be recognized officially. Important Dates =============== - Paper submission: 10 January 2020 (Fri) - Author response: 16?18 March 2020 (Mon-Wed) - Author notification: 8 April 2020 (Wed) Journal First ============= We have Journal First arrangements with ACM Transactions on Programming Languages and Systems and Elsevier Science of Computer Programming. Common to both routes --------------------- Only new research papers are eligible for the Journal First routes to ECOOP 2020. That is, it is not acceptable to submit an extension of a previous conference paper, even if the associated journal solicits extended papers via its standard submission route. Authors of all accepted Journal First papers will be invited to submit a short abstract for their paper to appear in the ECOOP 2020 conference proceedings. Journal First papers will be included along with research papers submitted directly to the conference when a Distinguished Paper is selected. Science of Computer Programming route ------------------------------------- See this dedicated web page [3] for full details of how to submit to the ECOOP 2020 Science of Computer Programming (SCP) special issue. Submission deadline: December 2, 2019 (Mon) ACM Transactions on Programming Languages and Systems route ----------------------------------------------------------- See this announcement [4] for details of the TOPLAS scheme whereby papers submitted to TOPLAS can be presented at selected conferences. Authors interested in this route should submit their paper to TOPLAS via its usual submission system and mark it as an ECOOP 2020 submission. The ECOOP Program Chair will then be informed of this submission and will have some input into the review process. Submission deadline: October 10, 2019 (Thu) More Information ================ For additional information, please contact the ECOOP Program Chair, Robert Hirschfeld [5]. [1] https://2020.ecoop.org/track/ecoop-2020-papers [2] https://www.dagstuhl.de/en/publications/lipics/instructions-for-authors/ [3] https://www.journals.elsevier.com/science-of-computer-programming/call-for-papers/object-oriented-programming [4] https://toplas.acm.org/announcements.cfm#submit-a-paper-for-pldi-2016 [5] https://www.hpi.uni-potsdam.de/hirschfeld/people/hirschfeld/ From tongbao.ztb at alibaba-inc.com Mon Dec 2 12:07:41 2019 From: tongbao.ztb at alibaba-inc.com (Tongbao Zhang) Date: Mon, 02 Dec 2019 20:07:41 +0800 Subject: =?UTF-8?B?5Zue5aSN77yaTXVsdGktc3Vydml2b3Igc3VwcG9ydCBmb3IgU1ZNIEdD?= In-Reply-To: <36D3E8FF-222F-4D93-B19D-E113088D0D43@oracle.com> References:

, <36D3E8FF-222F-4D93-B19D-E113088D0D43@oracle.com> Message-ID: <7181162d-e8cc-4e63-a268-58b348716f32.tongbao.ztb@alibaba-inc.com> Hi Thomas, I will update these in that PR page. Thanks for your advice! Tongbao ------------------------------------------------------------------ ????Thomas Wuerthinger ?????2019?12?2?(???) 18:00 ???????(??) ????graal-dev ????Re: Multi-survivor support for SVM GC Hi Tongbao! Thanks for the PR! Can you add some higher level description to https://github.com/oracle/graal/pull/1912? Also, do you have any benchmark numbers that show which scenarios are performing differently with this patch? - thomas On 2 Dec 2019, at 10:43, Tongbao Zhang wrote: Hello Graal developers, I have submit a PR here: https://github.com/oracle/graal/pull/1912 Look forward to your response. Thanks, Tongbao ------------------------------------------------------------------ ???????(??) ?????2019?11?22?(???) 21:24 ????graal-dev ????Multi-survivor support for SVM GC Dear Graal developers, Substrate VM is a great framework to generate executable native images for Java applications. Thank you for making it open-source. We (Alibaba) are trying to use Substrate VM and native-image to speed up the startup of our cloud-based Java applications. Meantime, we also found problems when running our applications using SVM. The full GC occurred more frequently than the HotSpot VM because there are no object age and survivor spaces in the current SVM GC implementation. We made some improvements to the SVM GC to address these problems, which can significantly decrease the full GC frequency. We would like to contribute a patch to the community, including the multi-survivor support of SVM builtin GC to reduce the frequency of full GC. We have tested this patch thoroughly in our production environment and are glad to contribute it to the Graal community. Look forward to your response. Thanks, Tongbao Zhang From usrinivasan at twitter.com Tue Dec 3 01:07:53 2019 From: usrinivasan at twitter.com (Uma Srinivasan) Date: Mon, 2 Dec 2019 17:07:53 -0800 Subject: 2nd Graal Workshop @ CGO 2020: Call for Submissions Message-ID: Hello All, The 2nd Graal Workshop in conjunction with CGO 2020 (www.cgo.org) is going to be held on Feb. 22nd in San Diego. At this point we are soliciting abstract submissions from the community. Details are available here: https://graalworkshop.github.io/2020/ Regards, Uma From lists at fniephaus.com Sun Dec 8 13:22:12 2019 From: lists at fniephaus.com (Fabio Niephaus) Date: Sun, 8 Dec 2019 14:22:12 +0100 Subject: =?UTF-8?Q?=E2=80=B9Programming=E2=80=BA_2020_=3A_Call_for_Participation?= Message-ID: ?Programming? 2020 : The Art, Science, and Engineering of Programming March 23-26, 2020, Porto, Portugal https://2020.programming-conference.org The International Conference on the Art, Science, and Engineering of Programming is a new conference focused on programming topics including the experience of programming. We have named it ?Programming? for short. The conference is co-located with several workshops, a poster and a demo session, a Coding Dojo, and the student research competition. Keynote ------- Guy L. Steele Jr. (Oracle Labs) Workshops --------- Convivial Computing Salon https://2020.programming-conference.org/home/salon-2020 ENIAC?20 https://2020.programming-conference.org/home/eniac-2020 ICW https://2020.programming-conference.org/home/icw-2020 MoreVMs?20 https://2020.programming-conference.org/home/MoreVMs-2020 NIP https://2020.programming-conference.org/home/nip-2020 PX/20 https://2020.programming-conference.org/home/px-2020 ProWeb?20 https://2020.programming-conference.org/home/proweb-2020 CoCoDo 2020 https://2020.programming-conference.org/home/cocodo-2020 Tutorials --------- https://2020.programming-conference.org/track/programming-2020-tutorials AntidoteDB : Just the Right Kind of Consistency! Bela Workshop Learning Haskell: a project-based approach Meta-Programming for the masses PharoIoT ******************************************************** ORGANIZATION ******************************************************** General Chair Ademar Aguiar, Universidade do Porto Program Chair Stefan Marr, University of Kent Organizing Committee https://2020.programming-conference.org/committee/programming-2020-organizing-committee Program Committee https://2020.programming-conference.org/committee/programming-2020-papers-program-committee ******************************************************** SUPPORTERS ******************************************************** ACM In-Cooperation Universidade do Porto City of Porto AOSA ******************************************************** For more information, visit https://2020.programming-conference.org From igor.veresov at oracle.com Wed Dec 11 07:11:26 2019 From: igor.veresov at oracle.com (Igor Veresov) Date: Tue, 10 Dec 2019 23:11:26 -0800 Subject: RFR(XL) 8235634: Update Graal Message-ID: <4C30F569-6D7E-48C3-984F-32E03CDD5633@oracle.com> Webrev: http://cr.openjdk.java.net/~iveresov/8235634/webrev.00/ JBS: https://bugs.openjdk.java.net/browse/JDK-8235634 The list of changes can be found in the JBS issue. Thanks, igor From vladimir.kozlov at oracle.com Wed Dec 11 23:30:31 2019 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Wed, 11 Dec 2019 15:30:31 -0800 Subject: RFR(XL) 8235634: Update Graal In-Reply-To: <4C30F569-6D7E-48C3-984F-32E03CDD5633@oracle.com> References: <4C30F569-6D7E-48C3-984F-32E03CDD5633@oracle.com> Message-ID: Looks good. Testing results are good too. Thanks, Vladimir On 12/10/19 11:11 PM, Igor Veresov wrote: > Webrev: http://cr.openjdk.java.net/~iveresov/8235634/webrev.00/ > JBS: https://bugs.openjdk.java.net/browse/JDK-8235634 > > The list of changes can be found in the JBS issue. > > Thanks, > igor > > > From igor.veresov at oracle.com Thu Dec 12 04:37:15 2019 From: igor.veresov at oracle.com (Igor Veresov) Date: Wed, 11 Dec 2019 20:37:15 -0800 Subject: RFR(XL) 8235634: Update Graal In-Reply-To: References: <4C30F569-6D7E-48C3-984F-32E03CDD5633@oracle.com> Message-ID: <004ABC75-BB6F-4630-99C0-442BE6853F50@oracle.com> Thanks, Vladimir! igor > On Dec 11, 2019, at 3:30 PM, Vladimir Kozlov wrote: > > Looks good. Testing results are good too. > > Thanks, > Vladimir > > On 12/10/19 11:11 PM, Igor Veresov wrote: >> Webrev: http://cr.openjdk.java.net/~iveresov/8235634/webrev.00/ >> JBS: https://bugs.openjdk.java.net/browse/JDK-8235634 >> The list of changes can be found in the JBS issue. >> Thanks, >> igor From doug.simon at oracle.com Mon Dec 16 20:25:51 2019 From: doug.simon at oracle.com (Doug Simon) Date: Mon, 16 Dec 2019 21:25:51 +0100 Subject: JVMCI 19.3-b06 release Message-ID: The 19.3-b06 release includes: ? GR-19906: Harmonize display of "Server VM" ? GR-19905: Fix LTS flag on JDK 11 builds ? GR-19933: -XX:-EnableJVMCI on GraalVM JDK11 fails instead of running on C2 ? GR-19880: remove UseJVMCIClassLoader code from labsjdk-11 ? GR-19570: VirtualObjectLayoutTest.testFormat needs to check field alignment ? GR-20027: Be more careful when getting nmethods from InstalledCode instances (JDK-8230884) ? GR-19767: HotSpot crash in Symbol::as_unicode when running native image generator (JDK-8235438) ? GR-19763: JVMCI c2v_getResolvedJavaType: VM crash (SIGSEGV) with SerialGC (#1863). The OpenJDK based Windows, Linux and macOS binaries are mirrored at: https://github.com/graalvm/openjdk8-jvmci-builder/releases/tag/jvmci-19.3-b06 https://github.com/graalvm/labs-openjdk-11/releases/tag/jvmci-19.3-b06 -Doug From dean.long at oracle.com Mon Dec 23 07:22:47 2019 From: dean.long at oracle.com (Dean Long) Date: Sun, 22 Dec 2019 23:22:47 -0800 Subject: [15] Review Request: 8235975 Update copyright year to match last edit in jdk repository for 2014/15/16/17/18 In-Reply-To: <1e7d0395-fc57-4d5b-9cfa-c33e0f6462d5@oracle.com> References: <1e7d0395-fc57-4d5b-9cfa-c33e0f6462d5@oracle.com> Message-ID: The changes to the src/jdk.internal.vm.compiler tree is going to complicate our automated sync with upstream Graal.? Our sync script sets the date based on changes in the Graal repo, so a file that was last modified in 2018 (in upstream Graal) but was added to JDK in 2019 would still have 2018 as the date. dl On 12/22/19 12:24 PM, Sergey Bylokhov wrote: > Hello. > Please review the fix for JDK 15. > > Bug: https://bugs.openjdk.java.net/browse/JDK-8235975 > Patch (2 Mb): > http://cr.openjdk.java.net/~serb/8235975/webrev.02/open.patch > Fix: http://cr.openjdk.java.net/~serb/8235975/webrev.02 > > I have updated the source code copyrights by the > "update_copyright_year.sh" > script for 2014/15/16/18/19 years, unfortunately, cannot run it for 2017 > because of: "JDK-8187443: Forest Consolidation: Move files to unified > layout" > which touched all files. > >