<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=GBK">
</head>
<body>
<br>
<p>On Thu, 24 Oct 2024 10:12:03 +0300 Ilias Tsitsimpis <iliastsi@debian.org>
wrote:</iliastsi@debian.org></p>
<p>Add replaceJump for a larger jump range.<br>
</p>
<p>On the Loong64 platform, there may be situations that are out of
the<br>
R_LARCH_B26 jump range. The previous commit added an additional<br>
--ghc-options parameter, but the issue persists. The reason for
this is<br>
the lack of code for jump substitution, so we should add this part
of<br>
the code to make sure that the --ghc-options parameter works.<br>
<br>
Please refer to the attachment for specific changes.<br>
<iliastsi@debian.org></iliastsi@debian.org></p>
<iliastsi@debian.org>> Hi Dandan,<br>
> <br>
> On Thu, Oct 24, 2024 at 11:16AM, zhangdandan wrote:<br>
> > Please give us some suggestions.<br>
> > Let's discuss and solve the problem together under this
bug.<br>
> > Your opinions are welcome.<br>
> <br>
> Unfortunately I am not an expert on this and I don't really
know why it<br>
> fails. It looks like GHC is broken/incomplete on LoongArch64,
so I would<br>
> suggest you report this upstream[1]. I will happily backport
any fix but<br>
> we have to first discuss it with them.<br>
> <br>
> [1] <a class="moz-txt-link-freetext" href="https://gitlab.haskell.org/ghc/ghc/-/issues">https://gitlab.haskell.org/ghc/ghc/-/issues</a><br>
> <br>
> As a workaround, maybe we can try to build an unregisterised
compiler on<br>
> LoongArch64 and use that instead, until this bug is fixed.
Can you try<br>
> and see if an unregisterised GHC works and build pandoc
successfully?<br>
> <br>
> Best,<br>
> <br>
> -- <br>
> Ilias<br>
> <br>
> <br>
</iliastsi@debian.org><br>
</body>
</html>