RFR: 8309266: C2: assert(final_con == (jlong)final_int) failed: final value should be integer
Daohan Qu
duke at openjdk.org
Tue Jun 13 03:01:58 UTC 2023
On Mon, 12 Jun 2023 19:26:06 GMT, Jesper Wilhelmsson <jwilhelm at openjdk.org> wrote:
>> @eme64 That's alright! I appreciate your telling me about some disciplines not written in the contributor guides. :P
>>
>> After some explorations, I realized that I didn't fully understand the root cause of this bug. Since I use my spare time to contribute, I think it would be better for some other experts to work on this so that we don't have to wait too long. I'm applying for an `Author` role and hope then I could continue contributing. Many thanks for your kindness again! :D
>
> @quadhier Please let me know if there is anything you think is missing from the OpenJDK Developers' Guide, I'd be happy to work on any improvements.
>
> Since you mention the guide, I assume that you have read https://openjdk.org/guide/index.html#contributing-to-an-openjdk-project and in particular https://openjdk.org/guide/index.html#socialize-your-change
Thanks, @JesperIRL. The guide is good and thoughtful. But it seems that nowadays the paradigm has slightly changed
— developers create issues in JBS, and someone picks up an issue and creates a PR in GitHub. Most of the communications happen in GitHub comments.
It would be better to emphasize that before working on an issue, you should make sure that it is assigned to you, or should mention in JBS or mailing list that you are working on it.
BTW, maybe for an unassigned issue, we could create a PR directly? Since we can communicate in the GitHub comments.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/14353#issuecomment-1588447159
More information about the hotspot-compiler-dev
mailing list