gcc-15_15.1.0-8_source.changes uploaded successfully to localhost
along with the files:
gcc-15_15.1.0-8.dsc
gcc-15_15.1.0-8.debian.tar.xz
gcc-15_15.1.0-8_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 16 Jun 2025 19:21:02 +0200
Source: gcc-15
Architecture: source
Version: 15.1.0-8
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By
Hi,
On Mon, 16 Jun 2025 09:01:48 +0200, Matthias Klose wrote:
>isn't that something that should be done upstream for that architecture?
There are three code models on loongarch64 according to its doc[1]:
- normal, the default one providing 256MiB PC-relative memory space.
- medium, providing 256G
I found out that in the current debian gcc-14-offload-nvptx and
gcc-13-offload-nvptx, if I compile a code that requires
unified_shared_memory and uses openmp to offload to gpu, the code is never
run on the gpu. It does compile the offload code, but then it is never
executed on the gpu.
That's t
Processing control commands:
> tags -1 + moreinfo
Bug #1107859 [libffi-dev] libffi-dev: Can't link libffi_pic.a to large binaries
like chromium on loong64
Added tag(s) moreinfo.
--
1107859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107859
Debian Bug Tracking System
Contact ow...@bugs.d
Control: tags -1 + moreinfo
isn't that something that should be done upstream for that architecture?
On 16.06.25 04:54, Jianfeng Liu wrote:
Package: libffi-dev
Version: 3.4.8-2
Severity: normal
Tags: patch
X-Debbugs-Cc: debian-loonga...@lists.debian.org
User: debian-loonga...@lists.debian.org
U
6 matches
Mail list logo