This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository gcc.
from 989a5fb3aa5 Add acc_device_radeon to name_of_acc_device_t function
new 0a8f4febf75 libstdc++: Fix conformance issues in <stop_token> (PR92895)
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:
libstdc++-v3/ChangeLog | 69 +++
libstdc++-v3/include/std/stop_token | 478 ++++++++++++++++-----
.../stop_token/stop_callback/deadlock-mt.cc} | 52 ++-
.../stop_token/stop_callback/deadlock.cc} | 25 +-
.../30_threads/stop_token/stop_callback/destroy.cc | 83 ++++
.../stop_token/stop_callback/destructible_neg.cc} | 39 +-
.../stop_token/stop_callback/invocable_neg.cc} | 15 +-
.../stop_token/stop_callback/invoke.cc} | 37 +-
.../stop_token/stop_source/assign.cc} | 28 +-
.../stop_token/stop_token/stop_possible.cc} | 26 +-
10 files changed, 679 insertions(+), 173 deletions(-)
copy libstdc++-v3/testsuite/{20_util/shared_ptr/atomic/3.cc => 30_threads/stop_tok [...]
copy libstdc++-v3/testsuite/{29_atomics/atomic_integral/cons/value_init.cc => 30_t [...]
create mode 100644 libstdc++-v3/testsuite/30_threads/stop_token/stop_callback/destroy.cc
copy libstdc++-v3/testsuite/{std/ranges/access/end_neg.cc => 30_threads/stop_token [...]
copy libstdc++-v3/testsuite/{std/ranges/access/size_neg.cc => 30_threads/stop_toke [...]
copy libstdc++-v3/testsuite/{29_atomics/atomic_float/value_init.cc => 30_threads/s [...]
copy libstdc++-v3/testsuite/{29_atomics/atomic_integral/cons/value_init.cc => 30_t [...]
copy libstdc++-v3/testsuite/{29_atomics/atomic_integral/cons/value_init.cc => 30_t [...]
--
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-next-allnoconfig
in repository toolchain/ci/llvm-project.
from 54b022d3444 [lldb] Fix nondeterminism in TestCppBitfields
adds 684c216d73c [ELF][PPC32] Support --emit-relocs link of R_PPC_PLTREL24
adds 9a174549742 [clangd][Hover] Make tests hermetic by setting target triplet
adds 967658150ed Work around PR44697 in CrashRecoveryContext
No new revisions were added by this update.
Summary of changes:
clang-tools-extra/clangd/unittests/HoverTests.cpp | 71 +++++++++--------------
lld/ELF/InputSection.cpp | 8 +++
lld/test/ELF/ppc32-relocatable-got2.s | 41 +++++++++++++
llvm/lib/Support/CrashRecoveryContext.cpp | 7 +++
4 files changed, 84 insertions(+), 43 deletions(-)
create mode 100644 lld/test/ELF/ppc32-relocatable-got2.s
--
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-next-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 69d23e11 0: update: llvm-linux: all
new 195a4e0e 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 (69d23e11)
\
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:
01-reset_artifacts/console.log | 16 +-
02-build_llvm/console.log | 12662 +++++++++++++++++------------------
03-build_linux/console.log | 706 +-
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 29 +
console.log | 13417 +++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
8 files changed, 13453 insertions(+), 13395 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-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 3f5dad4e 2: update: linux-eb9ebdceaadcab583114dd84f2a630603405e50f: 20299
new ce5f45b8 2: update: binutils-gcc-linux: 20299
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 (3f5dad4e)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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 | 183 +-
02-prepare_abe/console.log | 434 +-
03-build_abe-binutils/console.log | 11123 ++++++-------
04-build_abe-stage1/console.log | 18178 ++++++++++-----------
05-build_linux/console.log | 906 +-
07-check_regression/console.log | 16 +-
08-update_baseline/console.log | 85 +-
console.log | 30925 ++++++++++++++++++------------------
jenkins/manifest.sh | 16 +-
9 files changed, 31601 insertions(+), 30265 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-master-arm-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards 5e6dfd9a 0: update: llvm-linux: boot
new 3017ea16 0: update: llvm-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 (5e6dfd9a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-s [...]
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 | 176 +-
02-build_llvm/console.log | 12584 +++++++++++++++++-----------------
03-build_linux/console.log | 758 +-
04-boot_linux/console.log | 480 +-
05-check_regression/console.log | 10 +-
06-update_baseline/console.log | 29 +
console.log | 14037 +++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
8 files changed, 14079 insertions(+), 14009 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.