This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository gcc.
from cb273d81a45 analyzer: round-trip pointer-equality through intptr_t
new d26f37a16e3 PR93561 -- [bounds checking] memory overflow for spill_for
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/ChangeLog | 7 +++++++
gcc/lra-assigns.c | 2 ++
2 files changed, 9 insertions(+)
--
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-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards f25dac0a 2: update: linux-14b549456391a8b8f812529896b2690c16349734: 20275
discards 38378d3a 1: reset: linux-2fe4750e8506da0f23ab80390b762b0d44a04fc5: 20090
discards f6117700 0: update: llvm-6c4a8bc0a9f6a466d90d542bef66d69550c1b041: all
new 4d577dfe 0: update: llvm-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 (f25dac0a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-n [...]
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 | 166 +-
02-build_llvm/console.log | 12530 +++++++++++++++++-----------------
03-build_linux/console.log | 886 ++-
04-boot_linux/console.log | 8 +
05-check_regression/console.log | 13 +-
06-update_baseline/console.log | 46 +-
console.log | 13649 +++++++++++++++++++-------------------
jenkins/manifest.sh | 15 +-
results | 4 +-
9 files changed, 13825 insertions(+), 13492 deletions(-)
create mode 100644 04-boot_linux/console.log
--
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-aarch64-next-allyesconfig
in repository toolchain/ci/gcc.
from 533d051f6d1 Daily bump.
adds 763cec3a131 Daily bump.
No new revisions were added by this update.
Summary of changes:
gcc/DATESTAMP | 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.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards d2602904 0: update: binutils-gcc-linux: all
new 3081b0e6 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 (d2602904)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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:
01-reset_artifacts/console.log | 220 +-
02-prepare_abe/console.log | 268 +-
03-build_abe-binutils/console.log | 11093 ++++++++--------
04-build_abe-stage1/console.log | 13306 ++++++++++---------
05-build_linux/console.log | 691 +-
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 12 +-
08-update_baseline/console.log | 10 +-
console.log | 25659 ++++++++++++++++++------------------
jenkins/manifest.sh | 14 +-
10 files changed, 25603 insertions(+), 25672 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 users/amerey/debuginfod
in repository binutils-gdb.
from 7d33860d1d8 Add debuginfod support to GDB
new f7d53a90546 gdb/debuginfod-support.c: separate stub 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:
gdb/debuginfod-support.c | 39 ++++++++++++++++++++++++---------------
1 file changed, 24 insertions(+), 15 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.