This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm
in repository toolchain/ci/base-artifacts.
discards 498bfacd 0: update: binutils-gcc-linux-glibc-gdb: 1
new 6710cca3 0: update: binutils-gcc-linux-glibc-gdb: 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 (498bfacd)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]
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 1620 -> 1612 bytes
02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes
03-build_abe-binutils/console.log.xz | Bin 51360 -> 51424 bytes
04-build_abe-gcc/console.log.xz | Bin 231300 -> 231868 bytes
05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes
06-build_abe-linux/console.log.xz | Bin 8820 -> 8760 bytes
07-build_abe-glibc/console.log.xz | Bin 233600 -> 232036 bytes
08-build_abe-gdb/console.log.xz | Bin 48952 -> 50344 bytes
09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3808 bytes
10-build_abe-check_gcc/console.log.xz | Bin 2532 -> 2520 bytes
11-check_regression/console.log.xz | Bin 3172 -> 2372 bytes
11-check_regression/results.compare | 31 +-
11-check_regression/results.compare2 | 79 +-
12-update_baseline/console.log | 453 ++--
12-update_baseline/results.compare | 31 +-
12-update_baseline/results.compare2 | 79 +-
jenkins/manifest.sh | 20 +-
sumfiles/g++.log.xz | Bin 2845516 -> 2863404 bytes
sumfiles/g++.sum | 130 +-
sumfiles/gcc.log.xz | Bin 2502672 -> 2474980 bytes
sumfiles/gcc.sum | 4642 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 943656 -> 940792 bytes
sumfiles/gfortran.sum | 92 +-
sumfiles/libatomic.log.xz | Bin 2256 -> 2264 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 215344 -> 214572 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 458316 -> 455508 bytes
sumfiles/libstdc++.sum | 10 +-
31 files changed, 2676 insertions(+), 2917 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_O3
in repository toolchain/ci/base-artifacts.
discards 676714aa 0: update: binutils-gcc: 2
new 1e949b50 0: update: binutils-gcc: 2
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 (676714aa)
\
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 1604 -> 1616 bytes
02-prepare_abe/console.log.xz | Bin 2736 -> 2720 bytes
04-build_abe-binutils/console.log.xz | Bin 38088 -> 38084 bytes
05-build_abe-bootstrap_O3/console.log.xz | Bin 270908 -> 272968 bytes
06-check_regression/console.log.xz | Bin 416 -> 416 bytes
07-update_baseline/console.log | 37 +++++++++++++++++++++++++++++++
jenkins/manifest.sh | 12 +++++-----
7 files changed, 43 insertions(+), 6 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_lto
in repository toolchain/ci/base-artifacts.
discards 99929883 0: update: binutils-gcc: 2
new 3906ac77 0: update: binutils-gcc: 2
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 (99929883)
\
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 1608 -> 1600 bytes
02-prepare_abe/console.log.xz | Bin 2708 -> 2724 bytes
04-build_abe-binutils/console.log.xz | Bin 37856 -> 38280 bytes
05-build_abe-bootstrap_lto/console.log.xz | Bin 273924 -> 273560 bytes
06-check_regression/console.log.xz | Bin 416 -> 416 bytes
07-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 12 ++++++------
7 files changed, 7 insertions(+), 7 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-arm-bootstrap
in repository toolchain/ci/gcc.
from 2fa8c4a659a xtensa: Fix conflicting hard regno between indirect sibcall [...]
adds a63b99f24df libgo: use SYS_timer_settime32
No new revisions were added by this update.
Summary of changes:
gcc/go/gofrontend/MERGE | 2 +-
libgo/sysinfo.c | 5 +++++
2 files changed, 6 insertions(+), 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.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap
in repository toolchain/ci/base-artifacts.
discards d9207458 0: update: binutils-gcc: 2
new cfae21c5 0: update: binutils-gcc: 2
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 (d9207458)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-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:
01-reset_artifacts/console.log.xz | Bin 1600 -> 1616 bytes
02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes
04-build_abe-binutils/console.log.xz | Bin 51720 -> 51332 bytes
05-build_abe-bootstrap/console.log.xz | Bin 461904 -> 461980 bytes
06-check_regression/console.log.xz | Bin 416 -> 416 bytes
07-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 8 ++++----
7 files changed, 12 insertions(+), 12 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_gnu_cross_check_gcc/master-arm
in repository toolchain/ci/qemu.
from fc2cc19ffa ci: Upgrade msys2 release to 20220603
adds 587858ed0d hw/loongarch: Rename file 'loongson3.XXX' to 'virt.XXX'
adds 74725231d6 hw/loongarch: Change macro name 'LS7A_XXX' to 'VIRT_XXX'
adds 3916603e0c Merge tag 'pull-la-20220729' of https://gitlab.com/rth7680/q [...]
No new revisions were added by this update.
Summary of changes:
MAINTAINERS | 2 +-
hw/loongarch/acpi-build.c | 18 ++++++------
hw/loongarch/meson.build | 2 +-
hw/loongarch/{loongson3.c => virt.c} | 56 ++++++++++++++++++------------------
include/hw/loongarch/virt.h | 8 +++---
include/hw/pci-host/ls7a.h | 43 +++++++++++++--------------
target/loongarch/README | 2 +-
7 files changed, 64 insertions(+), 67 deletions(-)
rename hw/loongarch/{loongson3.c => virt.c} (93%)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.