This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository llvm.
from 34a4dfe92a4 [FileCollector] Change coding style from LLDB to LLVM (NFC)
new f9732c6d3f2 [llvm-lipo] Add test for -verify_archs
new 15471a7d111 [Object] Add public MaxSectionAlignment to MachOUniversal
new 51e124d8c8b [llvm-lipo] Implement alignment function in -create
The 3 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:
include/llvm/Object/MachOUniversal.h | 2 +
lib/Object/MachOUniversal.cpp | 13 +-
test/tools/llvm-lipo/Inputs/CPU10-slice.yaml | 359 +++++++++++++++++++++
.../Inputs/{i386-slice.yaml => CPU14-slice.yaml} | 2 +-
test/tools/llvm-lipo/create-compute-alignment.test | 20 ++
...lignment.test => create-default-alignment.test} | 0
.../llvm-lipo/verify-arch-universal-binary.test | 1 +
tools/llvm-lipo/llvm-lipo.cpp | 40 ++-
8 files changed, 426 insertions(+), 11 deletions(-)
create mode 100644 test/tools/llvm-lipo/Inputs/CPU10-slice.yaml
copy test/tools/llvm-lipo/Inputs/{i386-slice.yaml => CPU14-slice.yaml} (98%)
create mode 100644 test/tools/llvm-lipo/create-compute-alignment.test
rename test/tools/llvm-lipo/{create-without-alignment.test => create-default-align [...]
--
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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards db398d9a 0: update: binutils-gcc-linux: boot
new dc95a7ae 0: update: binutils-gcc-linux: boot
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 (db398d9a)
\
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:
01-reset_artifacts/console.log | 128 +-
02-prepare_abe/console.log | 438 +-
03-build_abe-binutils/console.log | 11384 +++++++--------
04-build_abe-stage1/console.log | 14496 ++++++++++---------
05-build_linux/console.log | 654 +-
console.log | 27102 ++++++++++++++++++------------------
jenkins/manifest.sh | 16 +-
7 files changed, 26979 insertions(+), 27239 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/ci/base-artifacts.
discards f3ada1b2 0: update: binutils-gcc-linux: all
new 3b86b643 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 (f3ada1b2)
\
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:
01-reset_artifacts/console.log | 164 +-
02-prepare_abe/console.log | 434 +-
03-build_abe-binutils/console.log | 11670 +++++++--------
04-build_abe-stage1/console.log | 14726 ++++++++++---------
05-build_linux/console.log | 628 +-
06-boot_linux/console.log | 6 +-
console.log | 27634 ++++++++++++++++++------------------
jenkins/manifest.sh | 16 +-
8 files changed, 27653 insertions(+), 27625 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 e4dfb6431e7 [docs] Split out a section on LoopInfo in the new loop docu [...]
new a232c74dcfc [Remarks][NFC] Rename remarks::Parser to remarks::RemarkParser
new 34a4dfe92a4 [FileCollector] Change coding style from LLDB to LLVM (NFC)
The 2 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:
include/llvm/Remarks/RemarkParser.h | 16 +--
include/llvm/Support/FileCollector.h | 36 +++---
lib/Remarks/RemarkParser.cpp | 8 +-
lib/Remarks/YAMLRemarkParser.cpp | 2 +-
lib/Remarks/YAMLRemarkParser.h | 6 +-
lib/Support/FileCollector.cpp | 159 +++++++++++++--------------
tools/llvm-opt-report/OptReport.cpp | 4 +-
unittests/Remarks/YAMLRemarksParsingTest.cpp | 20 ++--
8 files changed, 124 insertions(+), 127 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.