放弃提交补丁到上游,欢迎大家采纳。
"Giving up upstream-ing my patches & feel free to pick them up"

原始链接: https://mail.openjdk.org/pipermail/hotspot-dev/2026-January/118080.html

经过一年尝试向OpenJDK贡献补丁,开发者xtex(张炳武)因Oracle贡献者协议(OCA)审核停滞而放弃努力。尽管在数月内多次跟进邮件,OCA仍未获得批准,回复仅表示道歉并请求另一方进一步审核。 xtex居住在中国大陆,但声明与任何受限制的实体无关,他希望如果存在疑虑,能够明确拒绝,而不是无限期延迟。由于对流程感到沮丧,且没有时间继续“维护”这些PR,xtex发布这些补丁供他人采用。 这些补丁包括修复了损坏的`llvm-config`检查以及JDK 24零变体中的堆栈溢出问题,以及最初计划用于龙芯JDK分叉的多个补丁。xtex鼓励任何感兴趣的人以原创作品的形式重写这些补丁,以避免OCA要求。相关提交和拉取请求的链接已提供。

一位开发者(csmantle)宣布将停止向OpenJDK项目贡献补丁,原因是提交了多个拉取请求后,缺乏回应和进展。Hacker News上的讨论显示,这些补丁主要集中在编译器兼容性(特别是使用Clang编译),被一些人认为微不足道或“噪音”。 然而,其他人则为这些贡献辩护,认为即使是小的改动对新贡献者也有价值,并且可以防止在不同编译器上出现构建问题。一个关键问题是双精度浮点字面量中存在“d”后缀,这会导致使用Clang编译时出现错误,但GCC可以接受。 虽然一些人同情面临审查过载的维护者,但对于缺乏沟通感到沮丧——收到自动道歉,却没有实际审查。作者似乎已经接受了这种情况,并正在转向其他项目,并建议其他人也这样做。
相关文章

原文
Giving up upstream-ing my patches & feel free to pick them up xtex xtex at envs.net
Sat Jan 31 09:51:36 UTC 2026
Hi,

About one year ago, in Jan. 2025, I began my adventure of the OpenJDK 
codebase. Later I attempted to make some patches into the repository.
I checked the documentation and learned that I have to sign an Oracle 
Contributor Agreement before submitting patches to OpenJDK. At that time, I 
dreamed that it was just a pretty normal CLA, like the ones I signed for other 
projects and shall just take at most several days.

A few days later, I received an email asking me to update some information in 
the agreement. I did. After that, I have sent 5 emails to 
opensource_ww_grp at oracle.com asking if there was anything wrong (once a month 
from January to May). For each of my emails, I got a reply, saying that they 
"sincerely apologize" and "@Dalibor Topic Can you please review...", with no 
actual progress being made. Now it has been (more than) one year since I 
submitted my first OCA submission. And I have been tired of "/touch"-ing my PR 
once a month.

I wonder if there is a reason for not reviewing my OCA submission. I do live 
in Chinese Mainland but I have no contractual or subordinate or teacher-
student relationship with any entities that are restricted by the US import/
export control laws (according to OpenSanctions). If you think that I have 
such a relationship or should be rejected for any other reasons, please simply 
reject my OCA submission, instead of hanging it for months.

As I no longer have enough interest and spare time to work on OpenJDK, I 
decided to give up upstreaming those patches.
If anyone is interested in them, please feel free to pick up and submit these 
patches, most of which are small but I believe they are useful.
As OCA requires that "each contribution that you submit is and shall be an 
original work of authorship", you may rewrite my patches from scratch so it is 
an original work, and you don't need to sign my name or ping me.

I would like to give a list of the patches that I wanted to upstream but 
failed:

- Checks if "llvm-config" is broken:
https://github.com/AOSC-Tracking/jdk/commit/
6a8b12b1ad700d994a2803de593ca06e698ef1a9
- Extend default thread stack size for zero:
This addresses the stack overflow exception in javac when building JDK 24 with 
zero variants.
https://github.com/AOSC-Tracking/jdk/commit/
4534fcaafc149f649105dc9914c7cf4aaf8c802c
https://www.mail-archive.com/[email protected]/msg14818.html

Some patches that are not for the upstream OpenJDK but Loongson's fork of JDK 
and were also blocked by OCA:
https://github.com/loongson/jdk/pull/134
https://github.com/loongson/jdk/pull/126
https://github.com/loongson/jdk/pull/125
https://github.com/loongson/jdk/pull/135
https://github.com/loongson/jdk/pull/136
https://github.com/AOSC-Tracking/jdk/commit/
913dcb2b2759437876ae3a40a1b074eeb1bfe09f
https://github.com/AOSC-Tracking/jdk/commit/
caba8e6de73fd9ffa078d6c257d6be8500b9d16a

Best wishes,
Bye.
-- 
Bingwu Zhang (a.k.a. xtex) @ Sat, 31 Jan 2026 08:42:31 +0000





More information about the hotspot-dev mailing list
联系我们 contact @ memedata.com