LAST_UPDATED: Tue Jun 23 10:08:41 UTC 2015 (revision 224833)
Target: powerpc64le-linux-gnu
gcc version 4.9.2 (Debian 4.9.2-22)
Native configuration is powerpc64le-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/cpp1y/vla-initlist1.C -std=c++1y execution tes
Processing commands for cont...@bugs.debian.org:
> # nothing changed
> reopen 450746
Bug #450746 {Done: Andreas Beckmann } [gcc-4.2] gcc: Generates
extnernal references for static variable.
Warning: Unknown package 'gcc-4.2'
Bug reopened
Warning: Unknown package 'gcc-4.2'
Warning: Unknown package
Processing control commands:
> retitle -1 RM: gcc-4.4, superseded by newer GCC versions
Bug #707276 [gcc-4.4] gcc-4.4: gcc-4.4 is targeted for removal in unstable
Changed Bug title to 'RM: gcc-4.4, superseded by newer GCC versions' from
'gcc-4.4: gcc-4.4 is targeted for removal in unstable'
> rea
Control: retitle -1 RM: gcc-4.4, superseded by newer GCC versions
Control: reassign -1 ftp.debian.org
forgot that we still have this in unstable. Please remove it, already removed
from testing.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 23 Jun 2015 12:26:42 +0200
Source: libabigail
Binary: libabigail-dev libabigail0 libabigail-tools
Architecture: source i386
Version: 0.1~20150623-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC
libabigail_0.1~20150623-1_i386.changes uploaded successfully to localhost
along with the files:
libabigail_0.1~20150623-1.dsc
libabigail_0.1~20150623.orig.tar.xz
libabigail_0.1~20150623-1.debian.tar.xz
libabigail-dev_0.1~20150623-1_i386.deb
libabigail-tools_0.1~20150623-1_i386.deb
development
libx32stdc++-4.9-dev - GNU Standard C++ Library v3 (development files)
libx32stdc++6-4.9-dbg - GNU Standard C++ Library v3 (debugging files)
Closes: 787689 788812
Changes:
gcc-4.9 (4.9.2-22) unstable; urgency=medium
.
* Update to SVN 20150623 (r224833) from the gcc-4_9-branch.
* Fix PR
gcc-4.9_4.9.2-22_ppc64el.changes uploaded successfully to localhost
along with the files:
gcc-4.9_4.9.2-22.dsc
gcc-4.9_4.9.2-22.diff.gz
cpp-4.9_4.9.2-22_ppc64el.deb
g++-4.9_4.9.2-22_ppc64el.deb
gcc-4.9-base_4.9.2-22_ppc64el.deb
gcc-4.9-locales_4.9.2-22_all.deb
gcc-4.9-plugin-dev_4.9.2
ibx32stdc++-4.9-dev - GNU Standard C++ Library v3 (development files)
libx32stdc++6-4.9-dbg - GNU Standard C++ Library v3 (debugging files)
Closes: 787689 788812
Changes:
gcc-4.9 (4.9.2-22) unstable; urgency=medium
.
* Update to SVN 20150623 (r224833) from the gcc-4_9-branch.
* Fix PR target/
This bug is still present on g++-4.8, g++-4.9 and gcc-5
vdanjean@eyak:/tmp$ run() { echo "=> $*"; "$@" ; } ; run cat /tmp/toto.cpp ;
run cat /tmp/titi.cpp ; for v in 4.8 4.9 5 ; do echo "## $v ##" ; run
g++-$v -Wall -c toto.cpp ; run g++-$v -Wall --language=c -c toto.cpp ; run
g++-$v
Processing commands for cont...@bugs.debian.org:
> clone 764280 -1
Bug #764280 [g++-4.9] g++-4.7: g++ ignore "pragma GCC diagnostic ..." directives
Bug 764280 cloned as bug 789666
> reassign -1 g++-5 5.1.1-12
Bug #789666 [g++-4.9] g++-4.7: g++ ignore "pragma GCC diagnostic ..." directives
Bug reas
I will clone and reassign this bug as it is still present in new g++ versions
vdanjean@eyak:/tmp$ run() { echo "=> $*"; "$@" ; } ; run cat /tmp/toto.cpp ;
run cat /tmp/titi.cpp ; for v in 4.8 4.9 5 ; do echo "## $v ##" ; run
g++-$v -Wall -c toto.cpp ; run g++-$v -Wall --language=c -c t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23144
Richard Biener changed:
What|Removed |Added
Target Milestone|4.8.5 |4.9.3
--- Comment #19 from Richard Bien
reopen 85535
reassign 85535 gcc
quit
On Tue, Jun 23, 2015 at 07:39:43AM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the gcc,gcc-4.7 package:
>
> #85535: builtin memcmp() could be optimised
>
> It has been closed
reopen 204687
reassign 204687 gcc
quit
On Tue, Jun 23, 2015 at 07:36:09AM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the gcc-4.6,gcc-4.7 package:
>
> #204687: [PR 11877] gcc should use xor trick with -Os
>
> It
Processing commands for cont...@bugs.debian.org:
> reopen 204687
Bug #204687 {Done: Debian FTP Masters }
[gcc-4.6,gcc-4.7] [PR 11877] gcc should use xor trick with -Os
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to
Processing commands for cont...@bugs.debian.org:
> reopen 85535
Bug #85535 {Done: Debian FTP Masters }
[gcc,gcc-4.7] builtin memcmp() could be optimised
'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.
Bu
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
cpp-4.7 |4.7.4-3 | amd64, arm64, armel, armhf, i386, kfreebsd-amd64,
kfreebsd-i386, mips, mipsel, powerpc, s390x, sparc
cpp-4.7 | 4.7.4-3+b1 | hurd-i386
g++-4.7 |4.7.4-3 |
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #765379,
regarding gcc-4.7 should not ship with jessie
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #85535,
regarding builtin memcmp() could be optimised
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #737459,
regarding g++-4.7 [wheezy] may cause link failure when using lambda functions
to be marked as done.
This means that you claim
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #742700,
regarding spill fail with -fschedule-insns
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #762076,
regarding gcc-4.7: Please disable testsuite on sh4 - it has passed once
to be marked as done.
This means that you claim that t
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #763160,
regarding gcc-4.7: suggests non-existant packages: libmudflap0*, libppl9,
libpwl5, libcloog-ppl0
to be marked as done.
This m
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #762028,
regarding gcc-4.7: internal compiler error: in prepare_cmp_insn, at
optabs.c:4092
to be marked as done.
This means that you c
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #739502,
regarding libstdc++6-4.7-dev: std::set<>::operator== uses operator== to compare
elements
to be marked as done.
This means tha
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #741960,
regarding gcc-4.7: [C++] Bogus narrowing conversion warning when initializing
bit-field in union
to be marked as done.
This m
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #721720,
regarding -floop-parallelize-all misleadingly accepted
to be marked as done.
This means that you claim that the problem has be
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #731886,
regarding g++-4.7: errors from valgrind for C++ program using default locale
to be marked as done.
This means that you claim t
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #742574,
regarding g++-4.7: please backport the latest point release to wheezy
to be marked as done.
This means that you claim that the
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #730654,
regarding gfortran-4.7 -static and libquadmath
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #722139,
regarding gcc-4.7: Segfault on compile of include at:
/usr/include/boost/exception/exception.hpp:387:17.
to be marked as done.
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #716700,
regarding gfortran-4.7: gfortran -Wno-error=unused-parameter dosn't fully take
effect
to be marked as done.
This means that y
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #708142,
regarding mips64 and mips64el support without multilib
to be marked as done.
This means that you claim that the problem has be
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #710830,
regarding gcc-4.7: CVE-2002-2439
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #714839,
regarding [gcc-4.7] gcc generates wrong code with global register variables
to be marked as done.
This means that you claim th
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #714840,
regarding [gcc-4.7] gcc generates wrong code for global register variables
to be marked as done.
This means that you claim tha
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #719730,
regarding gcc-4.7: Should allow poisoned identifier in #elif if previous case
was taken
to be marked as done.
This means that
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #719732,
regarding gcc-4.7: Should allow poisoned identifier in #warning message
to be marked as done.
This means that you claim that t
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #714841,
regarding [gcc-4.7] gcc generates wrong code for global register variables
to be marked as done.
This means that you claim tha
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #669330,
regarding Internal compiler error on i586
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #679075,
regarding gcc 4.7 failt to build imagemagick: segfault
to be marked as done.
This means that you claim that the problem has be
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #701082,
regarding gcc-4.7: gcc generates incorrect code with -O2 compiling libffi
example
to be marked as done.
This means that you c
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #707644,
regarding gcc-4.7: old-style parameter declarations v.s. ANSI C section 3.7.1 ?
to be marked as done.
This means that you clai
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #680776,
regarding [fixed in 4.8] gcc does not use aligned load
to be marked as done.
This means that you claim that the problem has be
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #686645,
regarding Compiling code with -O3 results to segfault in binary
to be marked as done.
This means that you claim that the probl
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #697133,
regarding gcc-4.7: does not define _REENTRANT when run with -pthread on Hurd
to be marked as done.
This means that you claim t
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #683782,
regarding gccgo: please Recommend: binutils-gold on x86
to be marked as done.
This means that you claim that the problem has b
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #681076,
regarding gcc-4.7: gcov can call format_gcov with top > bottom, which is
unexpected and gives 99.99%
to be marked as done.
Th
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #678033,
regarding clang++ --std=gnu++11 fails to compile
to be marked as done.
This means that you claim that the problem has been de
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #686178,
regarding g++-4.7: g++ ignore "pragma GCC diagnostic ..." directives
to be marked as done.
This means that you claim that the
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #474086,
regarding gcc-4.2: Constant optimization for strlen() prints bogus warnings
to be marked as done.
This means that you claim th
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #460264,
regarding g++-4.2: Please make it possible to make the "cannot pass objects of
non-POD type ..." warning into an error
to be m
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #204687,
regarding [PR 11877] gcc should use xor trick with -Os
to be marked as done.
This means that you claim that the problem has be
Your message dated Tue, 23 Jun 2015 07:24:48 +
with message-id
and subject line Bug#789156: Removed package(s) from unstable
has caused the Debian Bug report #452431,
regarding g++-4.2: two cases of bad optimization in x86 (i686) with long long
in 32bit
to be marked as done.
This means that
55 matches
Mail list logo
