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-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 2d1225ba7f llvm-b33b410283e2759797b5ed264a4c6889a80fc5bb: 16218
new 75ed8cc6ea llvm-7c907bac6fd51835ed4410845cc25b44cdd08c95: 16218
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 (2d1225ba7f)
\
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 | 18 +-
2-build_llvm/console.log | 9155 ++++++++++++++++----------------
3-count_linux_objs/console.log | 1586 +++---
5-update_baseline/console.log | 2 +-
console.log | 10921 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 4 +-
9 files changed, 10802 insertions(+), 10896 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-release-arm-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards af0bc7ca22 linux-12491ed354d23c0ecbe02459bf4be58b8c772bc8: all
new dff7de21a5 gcc-b881d66b4e1312f6232fd44e01be41f5c0f77cff: 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 (af0bc7ca22)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-m [...]
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 | 13 +-
3-build_abe-binutils/console.log | 3070 +++++++++---------
4-build_abe-stage1/console.log | 3415 ++++++++++----------
5-count_linux_objs/console.log | 97 +-
console.log | 6571 +++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
9 files changed, 6586 insertions(+), 6600 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 llvm.
from ab8dc6c3bd7 MIR: Validate LLT types when parsing
new dec46528529 [WebAssembly] MC: Mark more function aliases as functions
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:
lib/CodeGen/AsmPrinter/AsmPrinter.cpp | 12 +++++++++++-
test/MC/WebAssembly/function-alias.ll | 32 ++++++++++++++++++++++++++++++++
2 files changed, 43 insertions(+), 1 deletion(-)
create mode 100644 test/MC/WebAssembly/function-alias.ll
--
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 compiler-rt.
from 41a38ef45 [scudo] Initial standalone skeleton check-in
new ba28e3428 [libFuzzer][Windows] Clean up RawPrint
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:
lib/fuzzer/FuzzerIOWindows.cpp | 3 +--
1 file changed, 1 insertion(+), 2 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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards a2837c5914 gcc-f280c6d35cae94f5ac6aea071a3d84d24f9abec0: all
new 6ba7f1fdf4 linux-12491ed354d23c0ecbe02459bf4be58b8c772bc8: 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 (a2837c5914)
\
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 | 13 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3371 +-
4-build_abe-stage1/console.log | 4551 +-
5-count_linux_objs/console.log | 275002 +++++++++++++++++-----------------
console.log | 283749 ++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 283422 insertions(+), 283288 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-release-arm-lts-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 814a2cca2e linux-dffbba4348e9686d6bf42d54eb0f2cd1c4fb3520: all
new 8d9aa7eb0c llvm-44c793021d5746a3860aaa241e7f0756a48df744: 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 (814a2cca2e)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-arm- [...]
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 | 16 +-
2-build_llvm/console.log | 9115 +++++++++++++++++++--------------------
3-count_linux_objs/console.log | 152 +-
console.log | 9217 ++++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 9187 insertions(+), 9333 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 llvm.
from 02e3a277803 [CGP] fix bogus test names/comments; NFC
new ab8dc6c3bd7 MIR: Validate LLT types when parsing
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:
lib/CodeGen/MIRParser/MIParser.cpp | 41 ++++++++++++++++++----
.../MIR/AArch64/parse-low-level-type-invalid10.mir | 12 +++++++
.../MIR/AArch64/parse-low-level-type-invalid4.mir | 10 ++++++
.../MIR/AArch64/parse-low-level-type-invalid5.mir | 10 ++++++
.../MIR/AArch64/parse-low-level-type-invalid6.mir | 10 ++++++
.../MIR/AArch64/parse-low-level-type-invalid7.mir | 10 ++++++
.../MIR/AArch64/parse-low-level-type-invalid8.mir | 10 ++++++
.../MIR/AArch64/parse-low-level-type-invalid9.mir | 10 ++++++
8 files changed, 107 insertions(+), 6 deletions(-)
create mode 100644 test/CodeGen/MIR/AArch64/parse-low-level-type-invalid10.mir
create mode 100644 test/CodeGen/MIR/AArch64/parse-low-level-type-invalid4.mir
create mode 100644 test/CodeGen/MIR/AArch64/parse-low-level-type-invalid5.mir
create mode 100644 test/CodeGen/MIR/AArch64/parse-low-level-type-invalid6.mir
create mode 100644 test/CodeGen/MIR/AArch64/parse-low-level-type-invalid7.mir
create mode 100644 test/CodeGen/MIR/AArch64/parse-low-level-type-invalid8.mir
create mode 100644 test/CodeGen/MIR/AArch64/parse-low-level-type-invalid9.mir
--
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-release-aarch64-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards cc77340c8f linux-65f42a73e55331961153006e902c4fe0bb4a69bb: all
new e05cecda30 llvm-44c793021d5746a3860aaa241e7f0756a48df744: 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 (cc77340c8f)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-aarc [...]
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 | 16 +-
2-build_llvm/console.log | 5237 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 155 +-
console.log | 5408 ++++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 5424 insertions(+), 5412 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.