Bug#974806: autofdo: Please upgrade to llvm-toolchain-11

2020-11-14 Thread sylvestre
Package: autofdo
Severity: normal

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the
archive, please upgrade to -11.

Thanks,
Sylvestre



Bug#974073: gcc-10: arm64 internal compiler error: canonical types differ for identical types

2020-11-14 Thread Wookey
Package: gcc-10
Followup-For: Bug #974073

I tried to build SparseMatrix-2.ii using the sample command on an Ampere emag 
(64GB RAM). It built successfully in an unstable chroot, taking about 5 
minutes, consuming about 3.5GB resident memory to do so, confirming what you 
found.

However building polymake under sbuild still fails, just as in #974058.
So does building polymake in the above (unclean) chroot, or compiling
SparseMatrix.cc alone. Max RAM usage in the polymake build got to
about 20G using 16 cores, but fell back to about 4.7G and only 4 cores
when the sparseMatrix compile dies. 

Building the one file alone:
g++ -c -o 
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o 
-MMD -MT 
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o 
-MF 
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o.d
 -fPIC -pipe -g -O2 -fdebug-prefix-map=/home/wookey/debian/polymake-4.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++14 -ftemplate-depth-200 -fno-strict-aliasing 
-fopenmp -Wshadow -Wlogical-op -Wconversion -Wzero-as-null-pointer-constant 
-Wno-parentheses -Wno-error=unused-function -Wno-stringop-overflow 
-Wno-array-bounds -DPOLYMAKE_WITH_FLINT  -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 
-DPOLYMAKE_APPNAME=common 
-I/home/wookey/debian/polymake-4.1/include/app-wrappers 
-I/home/wookey/debian/polymake-4.1/include/apps 
-I/home/wookey/debian/polymake-4.1/include/external/permlib 
-I/home/wookey/debian/polymake-4.1/include/external/TOSimplex 
-I/home/wookey/debian/polymake-4.1/include/core-wrappers 
-I/home/wookey/debian/polymake-4.1/include/core 
/home/wookey/debian/polymake-4.1/apps/common/cpperl/generated/SparseMatrix-2.cc 
&& : 'COMPILER_USED=10.2.0'

fails quickly with the same 
/home/wookey/debian/polymake-4.1/include/core/polymake/GenericVector.h:304:11: 
internal compiler error: canonical types differ for identical types error.
This only gets to about 500MB RAM usage before dying.

So, no this doesn't seem to be an OOM-killer issue. Not sure what _is_ going on 
with all that hardcore C++ typing. I'll ask internally if anyone has a clue.

--
Wookey



Bug#974802: autofdo: Please upgrade to llvm-toolchain-11

2020-11-14 Thread Sylvestre Ledru
Package: autofdo
Severity: normal

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the 
archive, please upgrade to -11.

Thanks,
Sylvestre



Processed (with 1 error): your mail

2020-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 974788 by 974784 974783 974782  974781 974780 974779 974778 974777
Bug #974788 [ftp.debian.org] RM: llvm-toolchain-10 -- ROM; Try to limit the 
number of llvm versions
974788 was not blocked by any bugs.
974788 was not blocking any bugs.
Added blocking bug(s) of 974788: 974777, 974783, 974781, 974778, 974784, 
974780, 974779, and 974782
> 974776 974787
Unknown command or malformed arguments to command.
> Thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
974788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#974781: gcc-10: Please upgrade to llvm-toolchain-11

2020-11-14 Thread Sylvestre Ledru
Package: gcc-10
Version: 10.2.0-16
Severity: normal

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the 
archive, please upgrade to -11.

Thanks,
Sylvestre

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (500, 'stable-updates'), 
(500, 'stable'), (500, 'oldstable'), (300, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcc-10 depends on:
ii  binutils   2.35.1-2
ii  cpp-10 10.2.0-16
ii  gcc-10-base10.2.0-16
ii  libc6  2.31-4
ii  libcc1-0   10.2.0-16
ii  libgcc-10-dev  10.2.0-16
ii  libgcc-s1  10.2.0-16
ii  libgmp10   2:6.2.0+dfsg-6
ii  libisl22   0.22.1-1
ii  libmpc31.2.0-1
ii  libmpfr6   4.1.0-3
ii  libstdc++6 10.2.0-16
ii  libzstd1   1.4.5+dfsg-4
ii  zlib1g 1:1.2.11.dfsg-2

Versions of packages gcc-10 recommends:
ii  libc6-dev  2.31-4

Versions of packages gcc-10 suggests:
pn  gcc-10-doc   
pn  gcc-10-locales   
pn  gcc-10-multilib  

-- no debconf information



Bug#974073: Help with an arm64 specific gcc internal error with polymake

2020-11-14 Thread Dominic Hargreaves
On Wed, Nov 11, 2020 at 10:12:19PM +, Dominic Hargreaves wrote:
> During the perl 5.32 transition we observed a build failure on arm64 which
> is reproducible on the porterbox and at lease three different buidds::
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974073
> 
> However Matthias Klose (and I) tried to isolate the problem using the
> expanded source and that doesn't fail:
> 
> g++ -c -std=c++14 -g -O2 -fPIC -fstack-protector-strong -ftemplate-depth=200 
> -fno-strict-aliasing -fopenmp -Wshadow -Wlogical-op -Wconversion 
> -Wzero-as-null-pointer-constant -Wno-parentheses -Wno-error=unused-function 
> -Wno-stringop-overflow -Wno-array-bounds SparseMatrix-2.ii
> 
> (source file attached).
> 
> Can anyone help try and pin this down?

Matthias theorized that this could be the OOM killer, which is why
it doesn't happen when built sequentially.

Does anyone have access to a higher RAM machine than the buildds
and amdahl (11GiB) that could help test this theory (and maybe do a
porter upload to unblock the issue for the perl transition?

Cheers
Dominic



Bug#963947: marked as done (gcc-10-cross-mipsen: FTBFS: empty variable name)

2020-11-14 Thread Debian Bug Tracking System
Your message dated Sat, 14 Nov 2020 21:25:47 +0800
with message-id <7c4908ed-58bc-4fcc-9fe2-6fa8e161d...@gmail.com>
and subject line Re: gcc-10-cross-mipsen: FTBFS: empty variable name
has caused the Debian Bug report #963947,
regarding gcc-10-cross-mipsen: FTBFS: empty variable name
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
963947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-10-cross-mipsen
Version: 2+c1
Severity: serious
Tags: ftbfs

This package fails to build on current sid.

  Command: dpkg-buildpackage -us -uc -b -rfakeroot
  dpkg-buildpackage: info: source package gcc-10-cross-mipsen
  dpkg-buildpackage: info: source version 2+c1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by YunQiang Su 
   dpkg-source --before-build .
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  debian/rules:6: *** empty variable name.  Stop.
  dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
exit status 2
 

This was presumably broken by the backward incompatible changes in
make_4.3-1.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
On Mon, 29 Jun 2020 06:30:47 +0300 Niko Tyni  wrote:
> Source: gcc-10-cross-mipsen
> Version: 2+c1
> Severity: serious
> Tags: ftbfs
> 
> This package fails to build on current sid.

This bug has been fixed by 3+c1.

> 
>   Command: dpkg-buildpackage -us -uc -b -rfakeroot
>   dpkg-buildpackage: info: source package gcc-10-cross-mipsen
>   dpkg-buildpackage: info: source version 2+c1
>   dpkg-buildpackage: info: source distribution unstable
>   dpkg-buildpackage: info: source changed by YunQiang Su 
>dpkg-source --before-build .
>   dpkg-buildpackage: info: host architecture amd64
>fakeroot debian/rules clean
>   debian/rules:6: *** empty variable name.  Stop.
>   dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> exit status 2
>  
> 
> This was presumably broken by the backward incompatible changes in
> make_4.3-1.
> -- 
> Niko Tyni   nt...@debian.org
> 
> --- End Message ---


gcc-10-cross-mipsen_3+c2_source.changes ACCEPTED into unstable

2020-11-14 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 14 Nov 2020 20:13:27 +0800
Source: gcc-10-cross-mipsen
Architecture: source
Version: 3+c2
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: YunQiang Su 
Changes:
 gcc-10-cross-mipsen (3+c2) unstable; urgency=medium
 .
   * Build with gcc 10.2.0-17.
Checksums-Sha1:
 2ef2f59edfe868ae110e452f8ee6d686c4edee62 60574 gcc-10-cross-mipsen_3+c2.dsc
 bb78a0523917609dda6291cfe4b8244a1b19b404 44052 gcc-10-cross-mipsen_3+c2.tar.xz
 5e28940c34a186cf5b8fd45ca19513fab3c2bebb 5465 
gcc-10-cross-mipsen_3+c2_source.buildinfo
Checksums-Sha256:
 9201d773e33a149655b0e56dbb3388dea86a57f15ef826096346eb9269ebe229 60574 
gcc-10-cross-mipsen_3+c2.dsc
 3619c019a622bc0ec82ffa49427d83145c12b990819c6c6b5c0d002186a803e0 44052 
gcc-10-cross-mipsen_3+c2.tar.xz
 be23b33b125082457462d36424c664bcb68bd10f9ed9351fdfcd832fd913fc81 5465 
gcc-10-cross-mipsen_3+c2_source.buildinfo
Files:
 cc0b62ba9053619e6093de59477500cb 60574 devel optional 
gcc-10-cross-mipsen_3+c2.dsc
 e3b6af126631155fcab89b0fee8ebc15 44052 devel optional 
gcc-10-cross-mipsen_3+c2.tar.xz
 ad487a7c13c1ec9eb16326e13fa30bd6 5465 devel optional 
gcc-10-cross-mipsen_3+c2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCAAtFiEET3MbhxKET+7/a6zdW0gHVdEZ6o4FAl+vy/QPHHN5cUBkZWJp
YW4ub3JnAAoJEFtIB1XRGeqOsr8IALWUoTfSW38MOaqwnjM/giSgTI6LU+8YPqFU
sJAcjvlRpC5GVL7LwfuyLSs6Lpp2lIMB+eWINUXt4ey+vTnq1QetImCZB3tBBgr/
yxUhursPavs1uhlqdmqNf86DYZoqVPK3DLoHLIb9iM0KcVXloLiVi4a072ZjAzbv
bbZ9NOeCPbiZOwOHqx42ZPkmK7qSiocN6cgdshAOkSQcK8a7oRJZnN9vBVQ9qelx
eIt4IR12SxmPoanhMlFVhvqB1Wwg3JPEoJ7uevG4DF47DjJgr2kjbPkTR6dfYAf/
LepdzoprkQI8wyUWHQWFK/2/4f14mGMzMdkIsB5gUi+PhpFeZB4=
=Kc9b
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Processing of gcc-10-cross-mipsen_3+c2_source.changes

2020-11-14 Thread Debian FTP Masters
gcc-10-cross-mipsen_3+c2_source.changes uploaded successfully to localhost
along with the files:
  gcc-10-cross-mipsen_3+c2.dsc
  gcc-10-cross-mipsen_3+c2.tar.xz
  gcc-10-cross-mipsen_3+c2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)