This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository gcc.
from 767c098247a Fix middle-end/102395: reg_class having only NO_REGS and ALL_REGS.
new 69337e7495d [PATCH] Remove unused function make_unique_name.
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/attribs.c | 34 ----------------------------------
gcc/attribs.h | 1 -
2 files changed, 35 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-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 4815d6bf 2: update: binutils-gcc-linux-qemu: 21351
new 7533f36a 2: update: binutils-gcc-linux-qemu: 21372
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 (4815d6bf)
\
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.xz | Bin 1596 -> 1560 bytes
02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes
03-build_abe-binutils/console.log.xz | Bin 43688 -> 43540 bytes
04-build_abe-stage1/console.log.xz | Bin 71548 -> 71360 bytes
05-build_abe-qemu/console.log.xz | Bin 30552 -> 30648 bytes
06-build_linux/console.log.xz | Bin 44704 -> 44192 bytes
08-check_regression/console.log.xz | Bin 512 -> 548 bytes
09-update_baseline/console.log | 156 +++++++++++++++++------------------
jenkins/manifest.sh | 22 ++---
results | 2 +-
10 files changed, 90 insertions(+), 90 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-aarch64-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards ecfe3ebc 0: update: binutils-llvm-qemu: all
new e6a3a781 0: update: linux-e84d67fb673b51597917f5edcbdfcdabcb5d3a02: 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 (ecfe3ebc)
\
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:
01-reset_artifacts/console.log.xz | Bin 1536 -> 1556 bytes
02-prepare_abe/console.log.xz | Bin 2760 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 42512 -> 41932 bytes
04-build_llvm/console.log.xz | Bin 57944 -> 58368 bytes
05-build_abe-qemu/console.log.xz | Bin 30048 -> 31520 bytes
06-build_linux/console.log.xz | Bin 5336 -> 3396 bytes
07-boot_linux/console.log.xz | Bin 576 -> 576 bytes
08-check_regression/console.log.xz | Bin 536 -> 528 bytes
09-update_baseline/console.log | 10 +++++-----
jenkins/manifest.sh | 12 +++++-------
results | 2 +-
11 files changed, 11 insertions(+), 13 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_check_bootstrap/master-arm-check_bootstrap_lto
in repository toolchain/ci/base-artifacts.
discards 324f26e9 0: update: binutils-10c21d953d8b26f75e73d6fdba1320093c657b6c: 1
new 1f1da4f2 0: update: binutils-034ce7b42a1da639979fd743d8b9b1fb86c22d1c: 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 (324f26e9)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check_bootstrap/mast [...]
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 1548 -> 1504 bytes
02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes
03-build_abe-binutils/console.log.xz | Bin 62876 -> 62888 bytes
04-build_abe-bootstrap_lto/console.log.xz | Bin 470828 -> 469428 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3804 bytes
06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2440 -> 2436 bytes
07-check_regression/console.log.xz | Bin 2948 -> 2804 bytes
07-check_regression/extra-bisect-params | 1 -
07-check_regression/fails.sum | 7 -
07-check_regression/results.compare | 25 +-
07-check_regression/results.compare2 | 52 +-
07-check_regression/results.regressions | 27 -
08-update_baseline/console.log | 280 +-
08-update_baseline/extra-bisect-params | 1 -
08-update_baseline/fails.sum | 7 -
08-update_baseline/results.compare | 25 +-
08-update_baseline/results.compare2 | 52 +-
08-update_baseline/results.regressions | 27 -
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 2738248 -> 2694608 bytes
sumfiles/g++.sum | 134 +-
sumfiles/gcc.log.xz | Bin 2328724 -> 2372132 bytes
sumfiles/gcc.sum | 3822 +++++++++++------------
sumfiles/gfortran.log.xz | Bin 893344 -> 907512 bytes
sumfiles/gfortran.sum | 94 +-
sumfiles/libatomic.log.xz | Bin 2300 -> 2284 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 171112 -> 171888 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2708 -> 2708 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 461796 -> 460524 bytes
sumfiles/libstdc++.sum | 10 +-
33 files changed, 2259 insertions(+), 2339 deletions(-)
delete mode 100644 07-check_regression/extra-bisect-params
delete mode 100644 07-check_regression/fails.sum
delete mode 100644 07-check_regression/results.regressions
delete mode 100644 08-update_baseline/extra-bisect-params
delete mode 100644 08-update_baseline/fails.sum
delete mode 100644 08-update_baseline/results.regressions
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.