Version: 12.2.0-18
malat@barriere ~ % apt-cache policy gcc-12
gcc-12:
Installed: 12.2.0-18
Candidate: 12.2.0-18
Version table:
*** 12.2.0-18 100
1 https://deb.debian.org/debian experimental/main i386 Packages
100 /var/lib/dpkg/status
12.2.0-14 500
500 https://
I’m sorry if this is the wrong place to post this, but I’m still trying to
figure everything out.
Am I correct in concluding that this bug doesn’t affect packages compiled for
Bookworm on AMD64? What about packages on AMD64 (like libpcre2-32-0) with
32-bit runtimes/versions/ABIs or packages (li
Version: 12.2.0-8
malat@barriere ~ % apt-cache policy gcc-12
gcc-12:
Installed: 12.2.0-18
Candidate: 12.2.0-18
Version table:
*** 12.2.0-18 100
1 https://deb.debian.org/debian experimental/main i386 Packages
100 /var/lib/dpkg/status
12.2.0-14 500
500 https://d
diff -Narup a/debian/patches/gcc-distro-specs.diff
b/debian/patches/gcc-distro-specs.diff
--- a/debian/patches/gcc-distro-specs.diff 2022-10-31 21:50:28.0
+0800
+++ b/debian/patches/gcc-distro-specs.diff 2023-04-07 09:57:08.034297864
+0800
@@ -1,20 +1,19 @@
# DP: Add empty dis
Dear,
The patch git-updates.diff including bug fixes from release/gcc-12 branch have
not been enabled in rules.patch, for gcc-12-12.2.0-14 and -17 (sid and exp).
( see
https://salsa.debian.org/toolchain-team/gcc/-/blob/gcc-12-debian/debian/rules.patch
line 15~17 )
To enable git-updates.diff,
Control: reopen -1
> the upstream fix went into 12.2.0-2.
Would be so kind as to demonstrate how ?
Here is what I see on my side:
% ssh barriere.debian.org
% sessionid=$(schroot -b -c sid_i386-dchroot)
% dd-schroot-cmd -c $sessionid apt-get update
% dd-schroot-cmd -c $sessionid apt-get upgrade
Version: 12.2.0-2
the upstream fix went into 12.2.0-2. If the problem persists, then there's
probably another issue. Please file a separate issue, after testing both gcc-12
and gcc-13 from experimental.
Control: severity -1 grave
By default packages on Debian are build with -O2 since I see that it
affects release arches:
* armel
* i386
* mips64el
* mipsel
Would it be possible to include fix:
https://gcc.gnu.org/g:9f532fec01d6651cc3cc136073f044a7953d8560
Thanks,
Control: found 1016903 12.2.0-9
See i386:
*
https://buildd.debian.org/status/fetch.php?pkg=highway&arch=i386&ver=1.0.3%7Egit20221102.4899d11-2&stamp=1667806545&raw=0
Control: found 1016903 12.2.0-7
For example ppc64:
*
https://buildd.debian.org/status/fetch.php?pkg=highway&arch=ppc64&ver=1.0.3%7Egit20221102.4899d11-1&stamp=1667470496&raw=0
Control: reopen -1
> -- Forwarded message --
> From: Matthias Klose
> To: 1016903-d...@bugs.debian.org, 1016...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 3 Nov 2022 09:28:54 +0100
> Subject: Fixed in 12.2.0-2 and later.
> Version: 12.2.0-2
>
> Fixed in 12.2.0-2 and later.
Nope. A
Version: 12.2.0-2
Fixed in 12.2.0-2 and later.
Control: affects -1 src:jpeg-xl
Just a wild guess:
*
https://buildd.debian.org/status/fetch.php?pkg=jpeg-xl&arch=armhf&ver=0.7.0-2&stamp=1664702466&raw=0
Package: g++-12
Version: 12.1.0-7
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
Affects: src:highway
I am getting some odd behavior for unit test of highway. I believe
there is some wrong-code generation using g++ + -O2 (tree-vectorize is
default now).
14 matches
Mail list logo