This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O1
in repository toolchain/ci/base-artifacts.
discards 72856904 2: update: binutils-gcc: 0
new 66ee91e3 2: update: binutils-gcc: 0
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (72856904)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log.xz | Bin 1540 -> 1552 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2768 bytes
04-build_abe-binutils/console.log.xz | Bin 24576 -> 24432 bytes
06-check_regression/console.log.xz | Bin 412 -> 412 bytes
07-update_baseline/console.log | 12 ++++++------
jenkins/manifest.sh | 10 +++++-----
6 files changed, 11 insertions(+), 11 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto_lean
in repository toolchain/ci/base-artifacts.
discards 014b46ed 2: update: binutils-gcc: 0
new 43bc134e 2: update: binutils-gcc: 0
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (014b46ed)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log.xz | Bin 1552 -> 1552 bytes
02-prepare_abe/console.log.xz | Bin 2760 -> 2764 bytes
04-build_abe-binutils/console.log.xz | Bin 24780 -> 25048 bytes
06-check_regression/console.log.xz | Bin 412 -> 412 bytes
07-update_baseline/console.log | 50 +++++++++++++++++------------------
jenkins/manifest.sh | 10 +++----
6 files changed, 30 insertions(+), 30 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository binutils-gdb.
from 5f437feef42 Automatic date update in version.in
new 50192212a72 gprofng doesn't build with gcc 5.5
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
gprofng/Makefile.in | 1 +
gprofng/configure | 79 +-
gprofng/configure.ac | 4 +
gprofng/doc/Makefile.in | 1 +
gprofng/gp-display-html/Makefile.in | 1 +
gprofng/libcollector/configure | 20 +-
gprofng/src/DbeSession.cc | 40 +-
gprofng/src/DbeSession.h | 4 +-
gprofng/src/Makefile.am | 6 +-
gprofng/src/Makefile.in | 19 +-
gprofng/src/QLParser.tab.cc | 1453 -------------------------
gprofng/src/QLParser.tab.hh | 2038 -----------------------------------
gprofng/src/QLParser.yy | 142 ++-
13 files changed, 222 insertions(+), 3586 deletions(-)
delete mode 100644 gprofng/src/QLParser.tab.cc
delete mode 100644 gprofng/src/QLParser.tab.hh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository gcc.
from da066c4269c Daily bump.
new 6afb21b824d LoongArch: Fix bug for tmpdir-g++.dg-struct-layout-1/t033.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
gcc/config/loongarch/loongarch.cc | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64
in repository toolchain/ci/base-artifacts.
discards ed677d3b 0: update: gcc-1774ab84863202f5db694914b67e3aef8c6dd807: 1
new f1d675e9 0: update: gcc-da066c4269c7992327bd2abdf51f075a1b1240f7: 1
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (ed677d3b)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log.xz | Bin 1568 -> 1484 bytes
02-prepare_abe/console.log.xz | Bin 2780 -> 2736 bytes
03-build_abe-binutils/console.log.xz | Bin 37924 -> 36648 bytes
04-build_abe-gcc/console.log.xz | Bin 208156 -> 206960 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3888 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2992 -> 2328 bytes
07-check_regression/console.log.xz | Bin 3404 -> 3120 bytes
07-check_regression/fails.sum | 5 +-
07-check_regression/results.compare | 28 +-
07-check_regression/results.compare2 | 88 +-
07-check_regression/results.regressions | 28 +-
08-update_baseline/console.log | 324 +--
08-update_baseline/fails.sum | 5 +-
08-update_baseline/results.compare | 28 +-
08-update_baseline/results.compare2 | 88 +-
08-update_baseline/results.regressions | 28 +-
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 3499484 -> 3474736 bytes
sumfiles/g++.sum | 136 +-
sumfiles/gcc.log.xz | Bin 2988752 -> 2999944 bytes
sumfiles/gcc.sum | 4468 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 1030168 -> 1027220 bytes
sumfiles/gfortran.sum | 94 +-
sumfiles/libatomic.log.xz | Bin 2180 -> 2192 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 201556 -> 201428 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2548 -> 2548 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 430364 -> 432200 bytes
sumfiles/libstdc++.sum | 12 +-
31 files changed, 2637 insertions(+), 2729 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.