This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository clang.
from 7e03c676e4 Refactor DependencyScanningTool to its own file
new 25e98e8a3e [clang-fuzzer] Update proto fuzzer example for r375453.
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:
tools/clang-fuzzer/ExampleClangProtoFuzzer.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
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 040439bd9e1 [testsuite] Make the Wnonnull independent of system headers.
new 024e3aa735e [C++] Avoid exposing internal details in aka types
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/cp/ChangeLog | 11 ++
gcc/cp/cp-tree.h | 13 ++-
gcc/cp/error.c | 10 +-
gcc/cp/tree.c | 80 +++++++------
gcc/testsuite/ChangeLog | 7 ++
.../diag-aka-5.h => g++.dg/diagnostic/aka5.h} | 0
gcc/testsuite/g++.dg/diagnostic/aka5a.C | 127 +++++++++++++++++++++
gcc/testsuite/g++.dg/diagnostic/aka5b.C | 127 +++++++++++++++++++++
gcc/testsuite/g++.target/aarch64/diag_aka_1.C | 13 +++
9 files changed, 350 insertions(+), 38 deletions(-)
copy gcc/testsuite/{gcc.dg/diag-aka-5.h => g++.dg/diagnostic/aka5.h} (100%)
create mode 100644 gcc/testsuite/g++.dg/diagnostic/aka5a.C
create mode 100644 gcc/testsuite/g++.dg/diagnostic/aka5b.C
create mode 100644 gcc/testsuite/g++.target/aarch64/diag_aka_1.C
--
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_bmk/llvm-release-aarch64-spec2k6-O2_LTO
in repository toolchain/ci/base-artifacts.
discards eec509c 0: update: gcc-7bdd6b659acb56cc745c2971e9977ce9f1f384b2: 0
new e3abb50 0: update: glibc-5397c399f9604f4e0d0b17f5600e7bc756577549: 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 (eec509c)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk/llvm-release-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 | 64 +-
02-prepare_abe/console.log | 438 +-
03-build_abe-binutils/console.log | 10084 +--
04-build_abe-stage1/console.log | 13745 ++--
05-build_abe-linux/console.log | 266 +-
06-build_abe-glibc/console.log | 38767 ++++-----
07-build_abe-stage2/console.log | 40394 +++++-----
08-build_llvm-true/console.log | 11422 +--
09-benchmark-O2_LTO/benchmark-start.log | 2 +-
09-benchmark-O2_LTO/benchmark.log | 5 +-
09-benchmark-O2_LTO/console.log | 134 +-
10-check_regression/console.log | 2855 +-
10-check_regression/results-0.csv | 1872 +-
10-check_regression/results-1.csv | 1845 +-
10-check_regression/results-compare.csv | 8 +-
10-check_regression/results-full.csv | 2006 +-
10-check_regression/results.csv | 159 +-
10-check_regression/results.log | 2360 +-
11-update_baseline/console.log | 2865 +-
11-update_baseline/results-0.csv | 1872 +-
11-update_baseline/results-1.csv | 1845 +-
11-update_baseline/results-compare.csv | 8 +-
11-update_baseline/results-full.csv | 2006 +-
11-update_baseline/results.csv | 159 +-
11-update_baseline/results.log | 2356 +-
console.log | 121034 ++++++++++++++---------------
jenkins/manifest.sh | 8 +-
results_id | 2 +-
28 files changed, 128904 insertions(+), 129677 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-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 4e10456 2: update: llvm-linux: 17874
new 248fcfb 2: update: llvm-linux: 17874
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 (4e10456)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-s [...]
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 | 130 +-
02-build_llvm/console.log | 12432 +++++++++++++--------------
03-build_linux/console.log | 4806 +++++------
05-check_regression/console.log | 8 +-
06-update_baseline/console.log | 20 +-
console.log | 17396 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
7 files changed, 17404 insertions(+), 17396 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-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards f3f0dcc 0: update: binutils-gcc-linux: all
new 9c55310 0: update: binutils-gcc-linux: 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 (f3f0dcc)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ma [...]
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 | 220 +-
02-prepare_abe/console.log | 438 +-
03-build_abe-binutils/console.log | 11111 ++++++------
04-build_abe-stage1/console.log | 20227 +++++++++++----------
05-build_linux/console.log | 2228 ++-
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 8 +-
08-update_baseline/console.log | 8 +-
console.log | 34321 ++++++++++++++++++------------------
jenkins/manifest.sh | 12 +-
10 files changed, 34259 insertions(+), 34316 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.