Bug#906085: gcc-8: 2 simultaneous threads of compilation cause machine shutdown

Hi Arthur On Tue, Aug 14, 2018 at 08:32:18AM +0930, Arthur Marsh wrote: > results in machine shutdown. Setting CONCURRENCY_LEGVEL=1 avoids the problem. While gcc may use the system in unusual ways, it does not have the permissions to shutdown a system. If a user space program breaks a system,

gcc-6_6.4.0-20_source.changes ACCEPTED into unstable

libx32stdc++-6-dev - GNU Standard C++ Library v3 (development files) libx32stdc++6-6-dbg - GNU Standard C++ Library v3 (debugging files) Closes: 905708 905714 Changes: gcc-6 (6.4.0-20) unstable; urgency=medium . * Update to SVN 20180814 (r263539) from the gcc-6-branch. - Fix PR libstdc

Bug#905708: marked as done (gcc-6: FTBFS with isl 0.20)

C++ Library v3 (development files) libx32stdc++6-6-dbg - GNU Standard C++ Library v3 (debugging files) Closes: 905708 905714 Changes: gcc-6 (6.4.0-20) unstable; urgency=medium . * Update to SVN 20180814 (r263539) from the gcc-6-branch. - Fix PR libstdc++/83982, PR libstdc++/80893, PR lib

Bug#905714: marked as done (gcc-6: FTBFS on hurd-i386)

. * Update to SVN 20180814 (r263539) from the gcc-6-branch. - Fix PR libstdc++/83982, PR libstdc++/80893, PR libstdc++/80893, PR libstdc++/68519, PR libstdc++/86292, PR libstdc++/60555, PR libstdc++/86734, PR libstdc++/66145, PR libstdc++/85222, PR target/86197 (PPC). - Fix

Processing of gcc-6_6.4.0-20_source.changes

gcc-6_6.4.0-20_source.changes uploaded successfully to localhost along with the files: gcc-6_6.4.0-20.dsc gcc-6_6.4.0-20.diff.gz gcc-6_6.4.0-20_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#905707: marked as done (gcc-8: x32 gcc builds have older versions than i386 and x86_64 builds)

Your message dated Tue, 14 Aug 2018 11:38:29 +0200 with message-id and subject line Re: Bug#905707: gcc-8: x32 gcc builds have older versions than i386 and x86_64 builds has caused the Debian Bug report #905707, regarding gcc-8: x32 gcc builds have older versions than i386 and x86_64 builds to

Bug#905792: [libcloog-isl-dev] Conflict against libisl-dev

On 09.08.2018 19:01, Agustin Henze wrote: > Package: libcloog-isl-dev > Version: 0.18.4-2 > Severity: normal > > Dear GCC Maintainers, when I try installing libcloog-isl-dev and libisl-dev > together I got the following error. > > The following packages have unmet dependencies: >

Bug#905792: marked as done ([libcloog-isl-dev] Conflict against libisl-dev)

Your message dated Tue, 14 Aug 2018 10:51:37 + with message-id and subject line Bug#905792: fixed in isl 0.20-2 has caused the Debian Bug report #905792, regarding [libcloog-isl-dev] Conflict against libisl-dev to be marked as done. This means that you claim that the problem has been dealt

isl_0.20-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 14 Aug 2018 12:14:35 +0200 Source: isl Binary: libisl-dev libisl19 Architecture: source Version: 0.20-2 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose

Bug#804190: please support cross compiler builds without relying on binutils-multiarch

Control: tags -1 - patch Control: tags -1 + moreinfo On 11.08.2018 18:18, Helmut Grohne wrote: > I didn't encounter a single binary package that ships both host and > target objects. Whenever they do, we can simply split the packages. at least gccgo-8- is such a package. Please also check for

Processed: Re: Bug#804190: please support cross compiler builds without relying on binutils-multiarch

Processing control commands: > tags -1 - patch Bug #804190 [src:gcc-8] please support cross compiler builds without relying on binutils-multiarch Removed tag(s) patch. > tags -1 + moreinfo Bug #804190 [src:gcc-8] please support cross compiler builds without relying on binutils-multiarch Added

Processing of isl_0.20-2_source.changes

isl_0.20-2_source.changes uploaded successfully to localhost along with the files: isl_0.20-2.dsc isl_0.20-2.debian.tar.xz isl_0.20-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#906085: gcc-8: 2 simultaneous threads of compilation cause machine shutdown

Hi, it appears that the symptoms were caused by running the build under a kernel revision (between 4.18.0-rc8 and 4.18.0) that had issues. Apologies for the trouble. Please close the bug report. On 14 August 2018 4:07:30 pm ACST, Bastian Blank wrote: >Hi Arthur > >On Tue, Aug 14, 2018 at

Processing of gcc-8_8.2.0-4_source.changes

gcc-8_8.2.0-4_source.changes uploaded successfully to localhost along with the files: gcc-8_8.2.0-4.dsc gcc-8_8.2.0-4.diff.gz gcc-8_8.2.0-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

gcc-7_7.3.0-28_source.changes ACCEPTED into unstable

) libx32stdc++6-7-dbg - GNU Standard C++ Library v3 (debugging files) libx32ubsan0 - UBSan -- undefined behaviour sanitizer (x32) libx32ubsan0-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symbols) Closes: 905539 Changes: gcc-7 (7.3.0-28) unstable; urgency=medium . * Update to SVN 20180814

Processing of gcc-7_7.3.0-28_source.changes

gcc-7_7.3.0-28_source.changes uploaded successfully to localhost along with the files: gcc-7_7.3.0-28.dsc gcc-7_7.3.0-28.diff.gz gcc-7_7.3.0-28_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

gcc-8_8.2.0-4_source.changes ACCEPTED into unstable

v3 (x32) libx32stdc++6-8-dbg - GNU Standard C++ Library v3 (debugging files) libx32ubsan1 - UBSan -- undefined behaviour sanitizer (x32) libx32ubsan1-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symbols) Changes: gcc-8 (8.2.0-4) unstable; urgency=medium . * Update to SVN 20180814

Bug#905539: marked as done (gcc-7 FTBFS with isl 0.20)

behaviour sanitizer (x32) libx32ubsan0-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symbols) Closes: 905539 Changes: gcc-7 (7.3.0-28) unstable; urgency=medium . * Update to SVN 20180814 (r264534) from the gcc-7-branch. - Fix PR libstdc++/86138, PR libstdc++/85672, PR libstdc++/84654