This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allyesconfig
in repository toolchain/binutils-gdb.
from bb86dd08b2 Automatic date update in version.in
adds f097f5ad80 Fix crash in "finish"
adds 02e12e3806 Use std::vector in type stacks
adds c65bac3846 Remove string-related cleanup from c-exp.y
adds 9d30e1fd7c Remove remaining cleanups from c-exp.y
adds b91c5d6e5a Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
gdb/ChangeLog | 43 ++++++
gdb/c-exp.y | 164 ++++++++++-----------
gdb/infcmd.c | 5 +-
gdb/parse.c | 24 +--
gdb/parser-defs.h | 9 +-
gdb/python/py-finishbreakpoint.c | 2 +-
gdb/testsuite/ChangeLog | 5 +
...ssing-type-name.exp => typedef-void-finish.exp} | 75 ++++------
9 files changed, 168 insertions(+), 161 deletions(-)
copy gdb/testsuite/gdb.dwarf2/{missing-type-name.exp => typedef-void-finish.exp} (54%)
--
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_kernel/gnu-master-arm-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards b49ec69dc gcc-c2e60613d4f20c053962533c5e82bab932b771ba: all
new 5a89c9a91 binutils-b91c5d6e5a3f373e424cede99cb4e0958792414e: all
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 (b49ec69dc)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-st [...]
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:
1-reset_artifacts/console.log | 64 +-
2-prepare_abe/console.log | 26 +-
3-build_abe-binutils/console.log | 6128 ++--
4-build_abe-stage1/console.log | 13088 ++++----
5-count_linux_objs/console.log | 44989 ++++++++++++++--------------
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 58955 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 6 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 61669 insertions(+), 61603 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_kernel/llvm-master-arm-next-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 019579689 llvm-cdc28a6f803270bc24866026344cd100584ec118: all
new 1231bf4cf linux-a85b6b4f641697f54952f52fec8af1dac0826ecc: all
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 (019579689)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-n [...]
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:
1-reset_artifacts/console.log | 230 +-
2-build_llvm/console.log | 9033 +++++++++++++++++++------------------
3-count_linux_objs/console.log | 205 +-
console.log | 9544 +++++++++++++++++++---------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 9222 insertions(+), 9810 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_kernel/llvm-master-aarch64-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 6de6d24ee llvm-02b3d1343270ac96db9f943f1225e0826dd116ec: 18215
new 2800ab923 llvm-adfcbc121d1ee44f6f73c55d6bbbe276c51da7f5: 18215
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 (6de6d24ee)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-aarch [...]
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:
1-reset_artifacts/console.log | 105 +-
2-build_llvm/console.log | 10109 +++++++++++++-------------
3-count_linux_objs/console.log | 4800 ++++++-------
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 15010 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 6 +-
trigger-bisect-on-failure | 4 +-
10 files changed, 14864 insertions(+), 15180 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_kernel/gnu-master-arm-stable-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 40e6df4a2 binutils-9d30e1fd7cfc742b03b7d973e511f7bfe5cfc295: all
new 0c381af75 gcc-c2e60613d4f20c053962533c5e82bab932b771ba: all
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 (40e6df4a2)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-st [...]
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:
1-reset_artifacts/console.log | 74 +-
2-prepare_abe/console.log | 22 +-
3-build_abe-binutils/console.log | 6381 +++++----
4-build_abe-stage1/console.log | 13181 +++++++++---------
5-count_linux_objs/console.log | 7078 +++++-----
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 26797 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 26730 insertions(+), 26829 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_kernel/gnu-master-aarch64-mainline-allyesconfig
in repository toolchain/binutils-gdb.
from bb86dd08b2 Automatic date update in version.in
adds f097f5ad80 Fix crash in "finish"
adds 02e12e3806 Use std::vector in type stacks
adds c65bac3846 Remove string-related cleanup from c-exp.y
adds 9d30e1fd7c Remove remaining cleanups from c-exp.y
adds b91c5d6e5a Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
gdb/ChangeLog | 43 ++++++
gdb/c-exp.y | 164 ++++++++++-----------
gdb/infcmd.c | 5 +-
gdb/parse.c | 24 +--
gdb/parser-defs.h | 9 +-
gdb/python/py-finishbreakpoint.c | 2 +-
gdb/testsuite/ChangeLog | 5 +
...ssing-type-name.exp => typedef-void-finish.exp} | 75 ++++------
9 files changed, 168 insertions(+), 161 deletions(-)
copy gdb/testsuite/gdb.dwarf2/{missing-type-name.exp => typedef-void-finish.exp} (54%)
--
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_kernel/gnu-master-aarch64-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards c10042e1a gcc-3bf0a1f4750af949909ff1df4ef2a79d6ca2af4a: all
new f33144139 binutils-b91c5d6e5a3f373e424cede99cb4e0958792414e: all
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 (c10042e1a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-aarch6 [...]
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:
1-reset_artifacts/console.log | 104 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3748 ++---
4-build_abe-stage1/console.log | 5171 +++---
5-count_linux_objs/console.log | 24334 ++++++++++++++--------------
console.log | 32405 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 32852 insertions(+), 32934 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.