Processed: Re: Bug#1032165: gcc-12-cross-ports: not binNMU safe
Processing control commands: > clone -1 -2 Bug #1032165 [src:gcc-12-cross-ports] gcc-12-cross-ports: not binNMU safe Bug 1032165 cloned as bug 1032167 > reassign -2 gcc-11-cross-mipsen 5+c3 Bug #1032167 [src:gcc-12-cross-ports] gcc-12-cross-ports: not binNMU safe Bug reassigned from package 'src:gcc-12-cross-ports' to 'gcc-11-cross-mipsen'. No longer marked as found in versions gcc-12-cross-ports/12. Ignoring request to alter fixed versions of bug #1032167 to the same values previously set Bug #1032167 [gcc-11-cross-mipsen] gcc-12-cross-ports: not binNMU safe There is no source info for the package 'gcc-11-cross-mipsen' at version '5+c3' with architecture '' Unable to make a source version for version '5+c3' Marked as found in versions 5+c3. > retitle -2 gcc-11-cross-mipsen: not binNMU-safe Bug #1032167 [gcc-11-cross-mipsen] gcc-12-cross-ports: not binNMU safe Changed Bug title to 'gcc-11-cross-mipsen: not binNMU-safe' from 'gcc-12-cross-ports: not binNMU safe'. -- 1032165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032165 1032167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#1032165: gcc-12-cross-ports: not binNMU safe
Control: clone -1 -2 Control: reassign -2 gcc-11-cross-mipsen 5+c3 Control: retitle -2 gcc-11-cross-mipsen: not binNMU-safe On 2023-02-28 22:13:59 +0100, Sebastian Ramacher wrote: > Source: gcc-12-cross-ports > Version: 12 > Severity: serious > > The method to compute the version of the binary packages is not > binNMU-safe. This can be seen from the latest round of binNMUs to > rebuild for outdated Built-Using fields. See > https://buildd.debian.org/status/fetch.php?pkg=gcc-12-cross-ports=amd64=12%2Bb1=1677602107=0 > > As it can be seen from the log, the version computed for the binary > packages is the same as the one of the build of the initial upload of > version 12. The binNMU version -- b1 in this case -- is missing. gcc-11-cross-mipsen is affected by the same issue. Cloning and reassigning. Cheers -- Sebastian Ramacher
Bug#1032165: gcc-12-cross-ports: not binNMU safe
Source: gcc-12-cross-ports Version: 12 Severity: serious The method to compute the version of the binary packages is not binNMU-safe. This can be seen from the latest round of binNMUs to rebuild for outdated Built-Using fields. See https://buildd.debian.org/status/fetch.php?pkg=gcc-12-cross-ports=amd64=12%2Bb1=1677602107=0 As it can be seen from the log, the version computed for the binary packages is the same as the one of the build of the initial upload of version 12. The binNMU version -- b1 in this case -- is missing. Cheers -- Sebastian Ramacher
Bug#1032161: gcc-12 FTCBFS: -gm2 not found
Source: gcc-12 Version: 12.2.0-14 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs Hi Matthias, gcc-12 fails to cross build since gm2 was introduced as a frontend due to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92336 and we cannot make a dent on it, but recently it started failing way earlier. It now fails finding -gm2 (the cross compiler). This is due to Build-Depends relying on a particular gcc version (which is good) but failing to supply the version suffix to the build. As with many other frontends, we need to pass GM2_FOR_TARGET to the build. I'm attaching a patch for this particular issue and that moves us back to the previous one. Helmut diff --minimal -Nru gcc-12-12.2.0/debian/changelog gcc-12-12.2.0/debian/changelog --- gcc-12-12.2.0/debian/changelog 2023-01-08 10:12:42.0 +0100 +++ gcc-12-12.2.0/debian/changelog 2023-02-27 13:33:34.0 +0100 @@ -1,3 +1,10 @@ +gcc-12 (12.2.0-14.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Improve cross building: Pass GM2_FOR_TARGET. (Closes: #-1) + + -- Helmut Grohne Mon, 27 Feb 2023 13:33:34 +0100 + gcc-12 (12.2.0-14) unstable; urgency=medium * Update to git 20230108 from the gcc-12 branch. diff --minimal -Nru gcc-12-12.2.0/debian/rules2 gcc-12-12.2.0/debian/rules2 --- gcc-12-12.2.0/debian/rules2 2022-10-31 14:42:14.0 +0100 +++ gcc-12-12.2.0/debian/rules2 2023-02-27 13:33:34.0 +0100 @@ -125,7 +125,8 @@ GFORTRAN_FOR_TARGET=$(DEB_TARGET_GNU_TYPE)-gfortran-$(BASE_VERSION) \ GOC_FOR_TARGET=$(DEB_TARGET_GNU_TYPE)-gccgo-$(BASE_VERSION) \ GNAT_FOR_TARGET=$(DEB_TARGET_GNU_TYPE)-gnat-$(BASE_VERSION) \ - GDC_FOR_TARGET=$(DEB_TARGET_GNU_TYPE)-gdc-$(BASE_VERSION) + GDC_FOR_TARGET=$(DEB_TARGET_GNU_TYPE)-gdc-$(BASE_VERSION) \ + GM2_FOR_TARGET=$(DEB_TARGET_GNU_TYPE)-gm2-$(BASE_VERSION) endif ifeq ($(DEB_BUILD_GNU_TYPE),$(DEB_TARGET_GNU_TYPE))
Bug#1023666: gcc-10 should not be shipped in bookworm
Package: gcc-10 Version: 10.4.0-7 Followup-For: Bug #1023666 Bug #1004184 implies that gcc-11 cannot build correct mips64 code for a key Debian package (source: matplotlib) without buildflag adjustments. However, gcc-10 does emit correct code for the same package and architecture. Should that be considered a blocker for this bug?
Bug#1032130: gcc-12: incorrect -Wanalyzer-shift-count-overflow warning
Package: gcc-12
Version: 12.2.0-14
Severity: normal
Tags: upstream
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98447
On the following program
void f (unsigned long *p, int r, int i)
{
int b = 64, n = r % 64;
while (i >= 0 && b >= 0)
{
if (b <= n)
p[i--] = 1UL << b;
b -= n;
}
}
gcc-12 emits the following incorrect warning:
$ gcc-12 -fanalyzer -c warn-shiftcount.c
warn-shiftcount.c: In function ‘f’:
warn-shiftcount.c:8:22: warning: shift by count (‘64’) >= precision of type
(‘6’) [-Wanalyzer-shift-count-overflow]
8 | p[i--] = 1UL << b;
| ^~~~
‘f’: events 1-5
|
|5 | while (i >= 0 && b >= 0)
| | ~~~^
| | |
| | (1) following ‘true’ branch...
|6 | {
|7 | if (b <= n)
| | ~
| | |
| | (2) ...to here
| | (3) following ‘true’ branch (when ‘b <= n’)...
|8 | p[i--] = 1UL << b;
| | ~~~
| || |
| || (5) shift by count ‘64’ here
| |(4) ...to here
|
Here, due to the "n = r % 64", one has n <= 63, so that "1UL << b"
can be executed only when b <= 63, and the shift is necessarily valid
(no overflow).
Note: gcc-11 is affected too, but not gcc-10.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gcc-12 depends on:
ii binutils 2.40-2
ii cpp-12 12.2.0-14
ii gcc-12-base12.2.0-14
ii libc6 2.36-8
ii libcc1-0 12.2.0-14
ii libgcc-12-dev 12.2.0-14
ii libgcc-s1 12.2.0-14
ii libgmp10 2:6.2.1+dfsg1-1.1
ii libisl23 0.25-1
ii libmpc31.3.1-1
ii libmpfr6 4.2.0-1
ii libstdc++6 12.2.0-14
ii libzstd1 1.5.4+dfsg2-3
ii zlib1g 1:1.2.13.dfsg-1
Versions of packages gcc-12 recommends:
ii libc6-dev 2.36-8
Versions of packages gcc-12 suggests:
ii gcc-12-doc 12.2.0-1
ii gcc-12-locales 12.2.0-14
ii gcc-12-multilib 12.2.0-14
-- no debconf information
--
Vincent Lefèvre - Web:
Bug#1032126: elfutils: bad d/copyright syntax
Source: elfutils Version: 0.188-2.1 Control: tags -1 patch The debian/copyright's Files: debian/po/pt.po paragraph misses the License field. It inherits the project license, so please add License: GPL-3+ as in the attached patch.--- debian/copyright.orig 2023-02-28 13:12:15.462780279 +0100 +++ debian/copyright 2023-02-28 13:12:29.314919074 +0100 @@ -188,6 +188,7 @@ Files: debian/po/pt.po Copyright: (C) 2021, Américo Monteiro +License: GPL-3+ License: GPL-3+ This file is free software; you can redistribute it and/or modify
Processed: elfutils: bad d/copyright syntax
Processing control commands: > tags -1 patch Bug #1032126 [src:elfutils] elfutils: bad d/copyright syntax Added tag(s) patch. -- 1032126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: vect: Don't allow vect_emulated_vector_p type in vectorizable_call [PR106322]
Processing control commands: > severity -1 grave Bug #1016903 [g++-12] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) Severity set to 'grave' from 'normal' -- 1016903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016903: vect: Don't allow vect_emulated_vector_p type in vectorizable_call [PR106322]
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,
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 1032118 1:20221021-1 Bug #1032118 [src:gcc-snapshot] riscv64: error: too few arguments to function 'long unsigned int __riscv_vsetvlmax_e8mf8(void)' Marked as found in versions gcc-snapshot/1:20221021-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 1032118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 1032118 src:highway Bug #1032118 [src:gcc-snapshot] riscv64: error: too few arguments to function 'long unsigned int __riscv_vsetvlmax_e8mf8(void)' Added indication that 1032118 affects src:highway > End of message, stopping processing here. Please contact me if you need assistance. -- 1032118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
