control: reopen -1
control: reassign -1 gcc-5
control: found -1 gcc-5/5.3.1-14
control: retitle -1 gcc-5: [arm64] float to double conversion does not silence
sNaN
On 2016-04-18 18:46, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was file
Processing control commands:
> reopen -1
Bug #750834 {Done: Debian FTP Masters }
[gcc-4.8] gcc-4.8: [arm64] float to double conversion does not silence sNaN
'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
control: reopen -1
control: reassign -1 gcc-5
control: found -1 gcc-5/5.3.1-14
control: retitle -1 gcc-5: [armel] float to double conversion does not silence
sNaN
On 2016-04-18 18:46, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed
Processing control commands:
> reopen -1
Bug #748616 {Done: Debian FTP Masters }
[gcc-4.8] gcc-4.8: [armel] float to double conversion does not silence sNaN
'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
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
cpp-4.8 |4.8.5-4 | amd64, arm64, armel, armhf, hurd-i386, i386,
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
g++-4.8 |4.8.5-4 | amd64, arm64
Version: 4.8.5-4+rm
Dear submitter,
as the package gcc-4.8 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/821336
The v
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #799953,
regarding gcc-4.7/4.8/4.9/5: incorrect double to integer conversion on i386
to be marked as done.
This means that you claim th
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #740005,
regarding src:gcc-4.8: [PATCH] Added missing build logic
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #765380,
regarding gcc-4.8: do not ship with Jessie+1
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #737386,
regarding g++-4.8: Segmentation fault thread_local
to be marked as done.
This means that you claim that the problem has been d
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #735564,
regarding gcc-4.8: `__x86.get_pc_thunk.bx' referenced in section `.text':
defined in discarded section…
to be marked as done.
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #739891,
regarding libstdc++: -static-libstdc++ broken
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #754721,
regarding gcc-4.8-hppa64_4.8.3-4: 3.15 and 3.16 Linux kernels fail to boot when
built with GCC 4.8.3-4
to be marked as done.
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #764279,
regarding g++-4.8: g++-4.8 ignore "pragma GCC diagnostic ..." directives
to be marked as done.
This means that you claim that
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #741234,
regarding src:gcc-4.8: [PATCH] When building cross-compilers using prebuilt
libraries, no longer re-build those libraries
to b
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #748616,
regarding gcc-4.8: [armel] float to double conversion does not silence sNaN
to be marked as done.
This means that you claim th
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #750834,
regarding gcc-4.8: [arm64] float to double conversion does not silence sNaN
to be marked as done.
This means that you claim th
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #727621,
regarding armel: std::future appears to be broken?
to be marked as done.
This means that you claim that the problem has been d
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #732549,
regarding libstdc++ 4.8.2 crashes after copying std::unordered_map
to be marked as done.
This means that you claim that the pr
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #732926,
regarding libstdc++-4.8-doc: documentation fails to render
to be marked as done.
This means that you claim that the problem ha
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #733975,
regarding gcc-4.8: -Os optimization bug (address of label)
to be marked as done.
This means that you claim that the problem ha
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #731259,
regarding [gcc-4.8] gcc-4.8 compiled 3.10.x kernel does not boot
to be marked as done.
This means that you claim that the prob
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #717734,
regarding gcc-4.8: busy-spin building with LTO
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #725612,
regarding gcc-4.8: FTBFS on x32: gdc's unittest process hangs
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #722068,
regarding when with_deps_on_target_arch_pkgs=yes, build gccbase
to be marked as done.
This means that you claim that the probl
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #716736,
regarding gcc-4.8-hppa64: Multiarch support broken in upgrade to 4.8.1-6 --
breaks Linux kernel build
to be marked as done.
T
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #714090,
regarding Go fails to build on ia64
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #720363,
regarding gcc-4.8: i386 on armhf cross-compiler FTBFS
to be marked as done.
This means that you claim that the problem has bee
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #489478,
regarding gij: missing output with formatted string
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 18 Apr 2016 18:43:10 +
with message-id
and subject line Bug#821336: Removed package(s) from unstable
has caused the Debian Bug report #703230,
regarding [gcc-4.8] gcc-4.8: -fsanitize=thread requires -fPIC too
to be marked as done.
This means that you claim that the pro
LAST_UPDATED: Thu Apr 14 22:10:49 UTC 2016 (revision 234994)
Native configuration is arm-unknown-linux-gnueabi
=== boehm-gc tests ===
Running target unix
=== boehm-gc Summary ===
# of expected passes12
# of unsupported tests 1
LAST_UPDATED: Thu Apr 14 22:10:49 UTC 2016 (revision 234994)
Target: mips-linux-gnu
gcc version 6.0.0 20160414 (experimental) [trunk revision 234994] (Debian
20160415-1)
Native configuration is mips-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/cpp1y/vla
LAST_UPDATED: Thu Apr 14 22:10:49 UTC 2016 (revision 234994)
Target: mipsel-linux-gnu
gcc version 6.0.0 20160414 (experimental) [trunk revision 234994] (Debian
20160415-1)
Native configuration is mipsel-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/cpp1y
LAST_UPDATED: Sat Apr 9 16:39:31 UTC 2016 (revision 234858)
Target: i586-gnu
gcc version 5.3.1 20160409 (Debian 5.3.1-14)
Native configuration is i586-pc-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/cdce3.C -std=gnu++98 execution test
FAIL: g++.dg/cdce3.C -std=gnu
34 matches
Mail list logo
