Bug#1107706: except: Don't use the cached value of the gcc_except_table section for comdat functions

2025-06-12 Thread fanpeng
Package: gcc-14 Version: 14.2.0-19 Severity: normal X-Debbugs-Cc: fanp...@loongson.cn Dear Maintainer, As https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119507 mentioned: We think this patch should be backported. -- System Information: Debian Release: 13.0 APT prefers unstable APT policy: (50

Bug#1101273: ghc: Pass the mcmodel=medium parameter to CC via GHC

2025-03-25 Thread fanpeng
On Tue, 25 Mar 2025 10:20:12 + (UTC) Gianfranco Costamagna wrote: Yes, We can drop the extra option to some packages. Commit 534391ca67cb508966b850f7a0fc3c6e26b50651 is fine. In fact,

Bug#1101273: ghc: Pass the mcmodel=medium parameter to CC via GHC

2025-03-24 Thread fanpeng
Package: ghc Version: 9.6.6-4+b1 Severity: normal X-Debbugs-Cc: fanp...@loongson.cn Dear Maintainer, To ensure that GHC-driver builds default to mcmodel=medium, GHC needs to pass this default parameter to CC without having to add it to the compiled project. The former commit does not ensure that

Bug#1085966: fixed in ghc 9.6.6-3

2024-11-05 Thread fanpeng
On Wed, 6 Nov 2024 14:48:52 +0800 fanpeng wrote: debian/patches/7e2d3eb507da184cf3337d36715fd82a81643d91.patch This patch is for GHC-9.6, 9.8 and later versions that already contain this change. And it's only part of the fix for build errors, the -optc-mcmodel=medium option is still n

Bug#1085966: fixed in ghc 9.6.6-3

2024-11-05 Thread fanpeng
Haskell Group > Changed-By: Gianfranco Costamagna > Closes: 1085966 > Changes: > ghc (9.6.6-3) unstable; urgency=medium > . > [ fanpeng ] > * debian/patches/7e2d3eb507da184cf3337d36715fd82a81643d91.patch: > - upstream fix for loong64 build failures (Closes: #1085966

Bug#1085966: ghc: ftbfs: help: Use extra --ghc-options does not reduce binary size (based on ghc 9.6.6-2)

2024-11-04 Thread fanpeng
On Thu, 24 Oct 2024 10:12:03 +0300 Ilias Tsitsimpis wrote: Add replaceJump for a larger jump range. On the Loong64 platform, there may be situations that are out of the R_LARCH_B26 jump range. The previous commit added an additional --ghc-options parameter, but the issue persists. The reason fo

Bug#1085966: ghc: ftbfs: help: Use extra --ghc-options does not reduce binary size (based on ghc 9.6.6-2)

2024-10-23 Thread fanpeng
On Thu, 24 Oct 2024 11:16:04 +0800 zhangdandan wrote: I'm aware of the problem. For LoongArch64, support in ghc-9.6-* is not complete. Maybe we should finish it. To put it simply, we should add some code like this: 41c41 < rewrites = [rewriteSymType, rewriteAVX, rewriteCall] --- > rewrit

Bug#1071151: ghc: Use extra --ghc-options in d/rules on loong64

2024-07-29 Thread fanpeng
Sorry it took so long to reply. Because I need to rebuild many libghc-* packages. With ghc-9.6.5-1~exp1, the error of R_LARCH_B26 overflowing also happened. So can we change the options for loong64? On Sat, 1 Jun 2024 15:01:13 +0800 zhangdandan wrote: > diff --git a/debian/rules b/debian/rul

Bug#1071151: ghc: Use extra --ghc-options in d/rules on loong64

2024-06-01 Thread fanpeng
On Fri, 17 May 2024 14:01:37 +0300 Ilias Tsitsimpis wrote: Yes, that's unregisterised. I'll try ghc 9.6.7-1~exp1 lately. > Hi! > > On Wed, May 15, 2024 at 09:23AM, Peng Fan wrote: > > The reason for the above error is that "relocation R_LARCH_B26 overflow > > .." occurs during static linkin