<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div class="moz-cite-prefix">On 25/10/2025 11:53, wenshao wrote:<br>
</div>
<blockquote type="cite" cite="mid:b27a2c9d-d268-4489-8b57-920090635dca.shaojin.wensj@alibaba-inc.com">
<div class="__aliyun_email_body_block">
<div style="font-family: Tahoma, Arial, STHeitiSC-Light, SimSun">
<div style="clear: both;"><span>Initially, the option to
disable CompactStrings was provided for performance
reasons. </span></div>
<div style="clear: both;"><span><br>
</span></div>
<div style="clear: both;"><span>However, with some
optimizations for UTF8 scenarios and Latin1, disabling
CompactStrings no longer has any performance benefits. I
propose removing the related code to make it simpler and
easier to maintain.</span></div>
<br>
</div>
</div>
</blockquote>
<br>
Thanks for bringing up this topic. I don't think it can be removed
without notice, any removal would at least need to start with
deprecating the CompactStrings VM option.<br>
<br>
It would be useful to get list of the cases that dependent on
-XX:-CompactString/equivalent. It was initially a <span style="color: rgb(23, 43, 77); font-family: "DejaVu Sans", sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">contingency
in the event of a performance or functional issue but I think we
are past all that. Things to check are the </span>32-bit ARM
port, is that this relevant? Other ports? IBM ports appear to care
about -CompactString, maybe only with their own VM?<br>
<br>
-Alan<br>
<br>
<br>
</body>
</html>