RFR: 8304006: jlink should create the jimage file in the native endian for the target platform [v3]

[Jim Laskey]

On Sat, 11 Mar 2023 11:11:05 GMT, Jaikiran Pai <jpai at openjdk.org> wrote:

>> Can I please get a review for this change which proposes to fix the issue reported in https://bugs.openjdk.org/browse/JDK-8206890?
>> 
>> The `jlink` command allows a `--endian` option to specify the byte order in the generated image. Before this change, when such a image was being launched, the code would assume the byte order in the image to be the native order of the host where the image is being launched. That would result in failure to launch java, as noted in the linked issue.
>> 
>> The commit in this PR, changes relevant places to not assume native order and instead determine the byte order by reading the magic bytes in the image file's header content.
>> 
>> A new jtreg test has been added which reproduces the issue and verifies the fix.
>
> Jaikiran Pai has updated the pull request incrementally with one additional commit since the last revision:
> 
>   undo unintentional copyright year change

Changes requested by jlaskey (Reviewer).

src/jdk.jlink/share/classes/jdk/tools/jlink/internal/JlinkTask.java line 916:

> 914:             }
> 915:             String archName = targetPlatform.substring(index + 1);
> 916:             return switch (archName) {

Not that keen having this table buried in code. It's something that should be at the build level, maybe read from a resource?

-------------

PR: https://git.openjdk.org/jdk/pull/11943