Re: RFR: 8247957: remove doclint support for HTML 4 [v3]

2020-12-17 Thread Yoshiki Sato
On Thu, 17 Dec 2020 04:58:21 GMT, Jonathan Gibbons  wrote:

>> Yoshiki Sato has refreshed the contents of this pull request, and previous 
>> commits have been removed. The incremental views will show differences 
>> compared to the previous content of the PR. The pull request contains one 
>> new commit since the last revision:
>> 
>>   8257204 and 8256313
>>   8257204: Remove usage of -Xhtmlversion option from javac
>>   8256313: JavaCompilation.gmk needs to be updated not to use 
>> --doclint-format html5 option
>
> Mostly OK; some minor suggestions

Some related changes to 8258460 in closed repo is here.
https://orahub.oci.oraclecorp.com/yoshiki_sato/jdk/-/merge_requests/new?merge_request%5Bsource_branch%5D=JDK-8247957_2

-

PR: https://git.openjdk.java.net/jdk/pull/893


Re: RFR: 8247957: remove doclint support for HTML 4 [v5]

2020-12-17 Thread Yoshiki Sato
> HTML4 is no longer supported in javadoc.
> 
> doclint needs to drop HTML4 support as well.
> The changes consist of:
> * Removing jdk.javadoc.internal.doclint.HtmlVersion and its references.
> * Sorting out supported tags and attributes in HTML5 (including fix incorrect 
> permission of valign in TH, TR, TD, THEAD and TBODY)
> * Modifying test code and expected outputs to be checked in HTML5

Yoshiki Sato has updated the pull request incrementally with one additional 
commit since the last revision:

  5th: 8258460: Remove --doclint-format option from javac

-

Changes:
  - all: https://git.openjdk.java.net/jdk/pull/893/files
  - new: https://git.openjdk.java.net/jdk/pull/893/files/f9ae0c5f..261f207a

Webrevs:
 - full: https://webrevs.openjdk.java.net/?repo=jdk=893=04
 - incr: https://webrevs.openjdk.java.net/?repo=jdk=893=03-04

  Stats: 10 lines in 3 files changed: 0 ins; 10 del; 0 mod
  Patch: https://git.openjdk.java.net/jdk/pull/893.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/893/head:pull/893

PR: https://git.openjdk.java.net/jdk/pull/893


Re: RFR: 8247957: remove doclint support for HTML 4 [v4]

2020-12-17 Thread Yoshiki Sato
> HTML4 is no longer supported in javadoc.
> 
> doclint needs to drop HTML4 support as well.
> The changes consist of:
> * Removing jdk.javadoc.internal.doclint.HtmlVersion and its references.
> * Sorting out supported tags and attributes in HTML5 (including fix incorrect 
> permission of valign in TH, TR, TD, THEAD and TBODY)
> * Modifying test code and expected outputs to be checked in HTML5

Yoshiki Sato has updated the pull request incrementally with one additional 
commit since the last revision:

  5th: 8257204 and 8256313
  8257204: Remove usage of -Xhtmlversion option from javac
  8256313: JavaCompilation.gmk needs to be updated not to use --doclint-format 
html5 option

-

Changes:
  - all: https://git.openjdk.java.net/jdk/pull/893/files
  - new: https://git.openjdk.java.net/jdk/pull/893/files/30db3882..f9ae0c5f

Webrevs:
 - full: https://webrevs.openjdk.java.net/?repo=jdk=893=03
 - incr: https://webrevs.openjdk.java.net/?repo=jdk=893=02-03

  Stats: 50 lines in 5 files changed: 0 ins; 0 del; 50 mod
  Patch: https://git.openjdk.java.net/jdk/pull/893.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/893/head:pull/893

PR: https://git.openjdk.java.net/jdk/pull/893


Integrated: Merge jdk16

2020-12-17 Thread Jesper Wilhelmsson
On Thu, 17 Dec 2020 20:38:45 GMT, Jesper Wilhelmsson  
wrote:

> Forwardport JDK 16 -> JDK 17

This pull request has now been integrated.

Changeset: f15528eb
Author:Jesper Wilhelmsson 
URL:   https://git.openjdk.java.net/jdk/commit/f15528eb
Stats: 773 lines in 63 files changed: 449 ins; 124 del; 200 mod

Merge

-

PR: https://git.openjdk.java.net/jdk/pull/1827


Integrated: Merge jdk16

2020-12-17 Thread Jesper Wilhelmsson
Forwardport JDK 16 -> JDK 17

-

Commit messages:
 - Merge
 - 8247994: Localize javadoc search
 - 8258515: javac should issue an error if an annotation is nested in a local 
class or interface
 - 8258225: compiler/c2/cr6340864/TestIntVect.java runs faster in interpreter
 - 8258293: tools/jpackage/share/RuntimePackageTest.java#id0 with 
RuntimePackageTest.testUsrInstallDir2
 - 8257621: JFR StringPool misses cached items across consecutive recordings
 - 8257999: Parallel GC crash in gc/parallel/TestDynShrinkHeap.java: new region 
is not in covered_region
 - 8257636: Update usage of "type" terminology in java.lang.Class and 
java.lang.reflect
 - 8258505: [TESTBUG] TestDivZeroWithSplitIf.java fails due to missing 
UnlockDiagnosticVMOptions
 - 8254023: A module declaration is not allowed to be a target of an annotation 
that lacks an @Target meta-annotation

The webrevs contain the adjustments done while merging with regards to each 
parent branch:
 - master: https://webrevs.openjdk.java.net/?repo=jdk=1827=00.0
 - jdk16: https://webrevs.openjdk.java.net/?repo=jdk=1827=00.1

Changes: https://git.openjdk.java.net/jdk/pull/1827/files
  Stats: 773 lines in 63 files changed: 449 ins; 124 del; 200 mod
  Patch: https://git.openjdk.java.net/jdk/pull/1827.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/1827/head:pull/1827

PR: https://git.openjdk.java.net/jdk/pull/1827


[jdk16] Integrated: JDK-8247994: Localize javadoc search

2020-12-17 Thread Jonathan Gibbons
On Sun, 13 Dec 2020 00:19:59 GMT, Jonathan Gibbons  wrote:

> This is for JDK16, as a precursor to fixing JDK-8258002.
> 
> While it is good to be using localized strings in the generated output, the 
> significance for JDK-8258002 is that the strings are now obtained from a 
> resource file, and not hardcoded in JavaScript file itself.
> 
> The source file `search.js` is renamed to `search.js.template`, and (unlike 
> other template files) is copied as-is into the generated image. The values in 
> the template are resolved when javadoc is executed, depending on the locale 
> in use at the time. Because of the change in the file's extension, two 
> makefiles are updated to accommodate the new extension: one is for the 
> "interim" javadoc used to generate the API docs; the other is for the primary 
> javadoc in the main JDK image.

This pull request has now been integrated.

Changeset: 30ca0a5d
Author:Jonathan Gibbons 
URL:   https://git.openjdk.java.net/jdk16/commit/30ca0a5d
Stats: 120 lines in 9 files changed: 87 ins; 6 del; 27 mod

8247994: Localize javadoc search

Reviewed-by: hannesw, ihse

-

PR: https://git.openjdk.java.net/jdk16/pull/16


Re: [jdk16] RFR: JDK-8247994: Localize javadoc search [v4]

2020-12-17 Thread Hannes Wallnöfer
On Thu, 17 Dec 2020 17:10:10 GMT, Jonathan Gibbons  wrote:

>> This is for JDK16, as a precursor to fixing JDK-8258002.
>> 
>> While it is good to be using localized strings in the generated output, the 
>> significance for JDK-8258002 is that the strings are now obtained from a 
>> resource file, and not hardcoded in JavaScript file itself.
>> 
>> The source file `search.js` is renamed to `search.js.template`, and (unlike 
>> other template files) is copied as-is into the generated image. The values 
>> in the template are resolved when javadoc is executed, depending on the 
>> locale in use at the time. Because of the change in the file's extension, 
>> two makefiles are updated to accommodate the new extension: one is for the 
>> "interim" javadoc used to generate the API docs; the other is for the 
>> primary javadoc in the main JDK image.
>
> Jonathan Gibbons has updated the pull request incrementally with one 
> additional commit since the last revision:
> 
>   Address review comment

Marked as reviewed by hannesw (Reviewer).

-

PR: https://git.openjdk.java.net/jdk16/pull/16


Re: [jdk16] RFR: JDK-8247994: Localize javadoc search [v4]

2020-12-17 Thread Jonathan Gibbons
> This is for JDK16, as a precursor to fixing JDK-8258002.
> 
> While it is good to be using localized strings in the generated output, the 
> significance for JDK-8258002 is that the strings are now obtained from a 
> resource file, and not hardcoded in JavaScript file itself.
> 
> The source file `search.js` is renamed to `search.js.template`, and (unlike 
> other template files) is copied as-is into the generated image. The values in 
> the template are resolved when javadoc is executed, depending on the locale 
> in use at the time. Because of the change in the file's extension, two 
> makefiles are updated to accommodate the new extension: one is for the 
> "interim" javadoc used to generate the API docs; the other is for the primary 
> javadoc in the main JDK image.

Jonathan Gibbons has updated the pull request incrementally with one additional 
commit since the last revision:

  Address review comment

-

Changes:
  - all: https://git.openjdk.java.net/jdk16/pull/16/files
  - new: https://git.openjdk.java.net/jdk16/pull/16/files/1a406f35..de6802c0

Webrevs:
 - full: https://webrevs.openjdk.java.net/?repo=jdk16=16=03
 - incr: https://webrevs.openjdk.java.net/?repo=jdk16=16=02-03

  Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
  Patch: https://git.openjdk.java.net/jdk16/pull/16.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk16 pull/16/head:pull/16

PR: https://git.openjdk.java.net/jdk16/pull/16


Re: [jdk16] RFR: JDK-8247994: Localize javadoc search [v3]

2020-12-17 Thread Hannes Wallnöfer
On Thu, 17 Dec 2020 16:39:17 GMT, Jonathan Gibbons  wrote:

>> This is for JDK16, as a precursor to fixing JDK-8258002.
>> 
>> While it is good to be using localized strings in the generated output, the 
>> significance for JDK-8258002 is that the strings are now obtained from a 
>> resource file, and not hardcoded in JavaScript file itself.
>> 
>> The source file `search.js` is renamed to `search.js.template`, and (unlike 
>> other template files) is copied as-is into the generated image. The values 
>> in the template are resolved when javadoc is executed, depending on the 
>> locale in use at the time. Because of the change in the file's extension, 
>> two makefiles are updated to accommodate the new extension: one is for the 
>> "interim" javadoc used to generate the API docs; the other is for the 
>> primary javadoc in the main JDK image.
>
> Jonathan Gibbons has updated the pull request incrementally with one 
> additional commit since the last revision:
> 
>   Address review comment

src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/formats/html/resources/search.js.template
 line 40:

> 38: var MIN_RESULTS = 3;
> 39: var MAX_RESULTS = 500;
> 40: var UNNAMED = ">";

Oops, an additional closing angle bracket slipped there.

-

PR: https://git.openjdk.java.net/jdk16/pull/16


Re: [jdk16] RFR: JDK-8247994: Localize javadoc search [v3]

2020-12-17 Thread Jonathan Gibbons
> This is for JDK16, as a precursor to fixing JDK-8258002.
> 
> While it is good to be using localized strings in the generated output, the 
> significance for JDK-8258002 is that the strings are now obtained from a 
> resource file, and not hardcoded in JavaScript file itself.
> 
> The source file `search.js` is renamed to `search.js.template`, and (unlike 
> other template files) is copied as-is into the generated image. The values in 
> the template are resolved when javadoc is executed, depending on the locale 
> in use at the time. Because of the change in the file's extension, two 
> makefiles are updated to accommodate the new extension: one is for the 
> "interim" javadoc used to generate the API docs; the other is for the primary 
> javadoc in the main JDK image.

Jonathan Gibbons has updated the pull request incrementally with one additional 
commit since the last revision:

  Address review comment

-

Changes:
  - all: https://git.openjdk.java.net/jdk16/pull/16/files
  - new: https://git.openjdk.java.net/jdk16/pull/16/files/ec85..1a406f35

Webrevs:
 - full: https://webrevs.openjdk.java.net/?repo=jdk16=16=02
 - incr: https://webrevs.openjdk.java.net/?repo=jdk16=16=01-02

  Stats: 3 lines in 2 files changed: 0 ins; 1 del; 2 mod
  Patch: https://git.openjdk.java.net/jdk16/pull/16.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk16 pull/16/head:pull/16

PR: https://git.openjdk.java.net/jdk16/pull/16


Cross-compilation of OpenJDK Zero with clang

2020-12-17 Thread Andy Nisbet
Hi,
I am in the process of porting OpenJDK to a new architecture, at the
current moment in time we only have clang/LLVM cross compilation tools, and
GCC/binutils is still a year or so away. Could anyone offer any pointers to
documentation/hints, and/or outline what is necessary to get cross
compilation with clang working?  I have a sysroot and a bootable diskimage
for the virtual emulated platform.

Thanks,
Andy