Processing control commands:
> forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89232
Bug #833931 [g++-8] c++: Fail to build when and the noreturn
keyword is used
Set Bug forwarded-to-address to
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89232'.
--
833931: https://bugs.debian.org/
Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89232
I registered the issue upstream.
--
Happy hacking
Petter Reinholdtsen
Processing control commands:
> reopen -1
Bug #833931 {Done: Debian FTP Masters }
[g++-6] c++: Fail to build when and the noreturn keyword is used
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reop
Control: reopen -1
Control: reassign -1 g++-8
Control: found -1 8.2.0-14
I had a look, and this issue still exist with GCC 8.2. Reassigning as
appropriate.
% gcc c++-noreturn.c
c++-noreturn.c: In function 'stop_now':
c++-noreturn.c:10:1: warning: 'noreturn' function does return
}
^
% clang c+
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
cpp-6 |6.4.0-7 | kfreebsd-amd64
cpp-6 |6.5.0-1 | mipsel
cpp-6 |6.5.0-2 | amd64, arm64, armel, armhf, hurd-i386, i386,
kfreebsd-i386, mips, mips64el, ppc64el, s39
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #843198,
regarding gcc-6: Cross-compiles older GCC badly
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #841419,
regarding linux-source-4.7: debian linux source package incompatible with
default gcc6 in unstable?
to be marked as done.
Thi
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #840190,
regarding provide /usr/bin/go via alternatives
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #846214,
regarding gcc-6: wrong code generation in protobuf-c testsuite, adding printf
works around
to be marked as done.
This means t
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #841533,
regarding gcc-6: versions 6.2.0-[7-9] break construction of linux kernel with
-fstack-protector-
to be marked as done.
Th
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #838874,
regarding gcc-6: crash on malformed __FILE__
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #845493,
regarding g++-6: Internal compiler error in tsubst, at cp/pt.c:13073
to be marked as done.
This means that you claim that the
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #844439,
regarding gcc-6 broken for kernel development work
to be marked as done.
This means that you claim that the problem has been d
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #841419,
regarding --enable-default-pie breaks kernel build on amd64
to be marked as done.
This means that you claim that the problem h
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #846530,
regarding g++-6: uint64_t toto=800*16'800'000; // -Woverflow reported
to be marked as done.
This means that you claim that the
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #841419,
regarding gcc-6: Unable to compile upstream kernel with previous .config
to be marked as done.
This means that you claim that
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #836848,
regarding libasan3: AddressSanitizer breaks when LD_PRELOAD is defined
to be marked as done.
This means that you claim that th
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #836944,
regarding gcc: autoconf test failing on amd64 with -pie -static combination
to be marked as done.
This means that you claim th
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #836864,
regarding libasan3: -fsanitize=address -static-libasan doesn't always work
to be marked as done.
This means that you claim tha
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #829604,
regarding g++-6: In c++11/14 mode whitespaces are ignored between enum type and
::
to be marked as done.
This means that you
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #823778,
regarding gcc-6: please make -mmusl return an error instead of doing the wrong
thing
to be marked as done.
This means that yo
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #827787,
regarding gcc-6: improve gcj cross build
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #814221,
regarding gnat currently ftbfs with GCC trunk (GCC 6) on m68k
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #833931,
regarding c++: Fail to build when and the noreturn keyword is
used
to be marked as done.
This means that you claim that the
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #833850,
regarding dpkg-dev: add per-architecture optimisation flags to dpkg-buildflags
to be marked as done.
This means that you claim
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #798710,
regarding gcc-6: libgccjit is broken on mips*
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #773065,
regarding selecting target via dpkg-buildpackage --target-arch
to be marked as done.
This means that you claim that the proble
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #781457,
regarding ada bootstrap failure on mips and mipsel
to be marked as done.
This means that you claim that the problem has been d
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #539912,
regarding gcc-6: for c99, POSIX requires that option -D have a lower precedence
than -U
to be marked as done.
This means that
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #666106,
regarding kfreebsd-i386, hurd-i386: Exceptions with tracebacks cause
STORAGE_ERROR or SEGFAULT
to be marked as done.
This mea
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 02 Feb 2019 08:33:41 +0800
Source: gcc-defaults-mipsen
Binary: cpp-mips64-linux-gnuabi64 cpp-mipsisa32r6-linux-gnu
cpp-mipsisa32r6el-linux-gnu cpp-mipsisa64r6-linux-gnuabi64
cpp-mipsisa64r6el-linux-gnuabi64 g++-
Your message dated Wed, 6 Feb 2019 15:14:07 +0100
with message-id <4385580f-a321-31bb-60b5-9e92806b0...@debian.org>
and subject line Re: Bug#921512: GCC 9 ftbfs on alpha
has caused the Debian Bug report #921512,
regarding GCC 9 ftbfs on alpha
to be marked as done.
This means that you claim that th
On 06.02.19 12:40, Matthias Klose wrote:
> Package: src:gcc-9
> Severity: important
>
> At least in a cross build according to
> https://launchpadlibrarian.net/409942596/buildlog_ubuntu-disco-amd64.gcc-9-cross-ports_0ubuntu1_BUILDING.txt.gz
>
> The native alpha build wasn't yet started.
>
> dh_m
Package: src:gcc-9
Severity: important
At least in a cross build according to
https://launchpadlibrarian.net/409942596/buildlog_ubuntu-disco-amd64.gcc-9-cross-ports_0ubuntu1_BUILDING.txt.gz
The native alpha build wasn't yet started.
dh_movefiles -plibgfortran-9-dev-alpha-cross
usr/lib/gcc-cross/
34 matches
Mail list logo
