This is an automated email from the git hooks/post-receive script.
"Maxim Kuvyrkov pushed a change to branch llvm-kernel-v3
in repository toolchain/jenkins-scripts.
discards 97ca775 Rename tcwg-llvm-kernel.sh
new 0c6c978 Rename tcwg-llvm-kernel.sh
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 (97ca775)
\
N -- N -- N refs/heads/llvm-kernel-v3 (0c6c978)
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:
tcwg-llvm-kernel.sh | 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.
unknown user pushed a change to branch master
in repository newlib.
from 3bc64b88c RTEMS: Add __tls_get_addr() to crt0
new 36cb95f60 CYgwin: fix typo in comment
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:
winsup/cygwin/fhandler_socket_unix.cc | 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.
unknown user pushed a change to branch master
in repository gcc.
from 2515797e5db 2018-08-24 Richard Biener <rguenther(a)suse.de>
new 217cd82aec5 DWARF: Call set_indirect_string on DW_MACINFO_start_file
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 | 6 ++++++
gcc/dwarf2out.c | 6 ++++++
gcc/testsuite/ChangeLog | 5 +++++
gcc/testsuite/gcc.dg/pr79342.c | 18 ++++++++++++++++++
4 files changed, 35 insertions(+)
create mode 100644 gcc/testsuite/gcc.dg/pr79342.c
--
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.
"Maxim Kuvyrkov pushed a change to branch llvm-kernel-v3
in repository toolchain/jenkins-scripts.
discards 4005762 Rename tcwg-llvm-kernel.sh
new 97ca775 Rename tcwg-llvm-kernel.sh
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 (4005762)
\
N -- N -- N refs/heads/llvm-kernel-v3 (97ca775)
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:
tcwg-llvm-kernel.sh | 4 +++-
1 file changed, 3 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.
"Maxim Kuvyrkov pushed a change to branch llvm-kernel-v3
in repository toolchain/jenkins-scripts.
discards dfcaf9f Rename tcwg-llvm-kernel.sh
new 4005762 Rename tcwg-llvm-kernel.sh
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 (dfcaf9f)
\
N -- N -- N refs/heads/llvm-kernel-v3 (4005762)
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:
jenkins-helpers.sh | 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.
unknown user pushed a change to branch master
in repository clang-tools-extra.
from 29c8c28b [clangd] Log memory usage of DexIndex and MemIndex
new 052f22f5 [clangd] Speculative code completion index request before Sem [...]
new 66cc5c29 [clangd] Implement LIMIT iterator
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:
clangd/ClangdServer.cpp | 36 +++++++++--
clangd/ClangdServer.h | 7 +++
clangd/CodeComplete.cpp | 107 +++++++++++++++++++++++++++++----
clangd/CodeComplete.h | 43 ++++++++++++-
clangd/TUScheduler.h | 13 ++++
clangd/index/Index.h | 9 +++
clangd/index/dex/DexIndex.cpp | 4 +-
clangd/index/dex/Iterator.cpp | 81 ++++++++++++++++++-------
clangd/index/dex/Iterator.h | 30 +++++----
clangd/tool/ClangdMain.cpp | 1 +
unittests/clangd/CodeCompleteTests.cpp | 77 +++++++++++++++++++++++-
unittests/clangd/DexIndexTests.cpp | 46 +++++++-------
12 files changed, 375 insertions(+), 79 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 gcc.
from 6fad3a45f02 rs6000: Check that the base of a TOCREL is the TOC (PR86989)
new 2515797e5db 2018-08-24 Richard Biener <rguenther(a)suse.de>
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 | 17 +++++++++++++++
gcc/cfg.c | 2 ++
gcc/cfg.h | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++++
gcc/cfganal.c | 37 ++++-----------------------------
gcc/cfgloop.c | 9 ++++----
gcc/hsa-brig.c | 2 +-
gcc/hsa-dump.c | 2 +-
gcc/hsa-regalloc.c | 4 ++--
gcc/print-rtl.c | 2 +-
gcc/profile-count.c | 2 +-
10 files changed, 94 insertions(+), 43 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 gcc.
from eba1b999281 PR 87073/bootstrap * wide-int-range.cc (wide_int_range_di [...]
new 6fad3a45f02 rs6000: Check that the base of a TOCREL is the TOC (PR86989)
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 | 6 ++++++
gcc/config/rs6000/rs6000.c | 4 +++-
2 files changed, 9 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.
"Maxim Kuvyrkov pushed a change to branch llvm-kernel-v3
in repository toolchain/jenkins-scripts.
discards a2f8048 Rename tcwg-llvm-kernel.sh
new dfcaf9f Rename tcwg-llvm-kernel.sh
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 (a2f8048)
\
N -- N -- N refs/heads/llvm-kernel-v3 (dfcaf9f)
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:
--
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.
"Maxim Kuvyrkov pushed a change to branch llvm-kernel-v3
in repository toolchain/jenkins-scripts.
discards b5a5ffb Rename tcwg-llvm-kernel.sh
new a2f8048 Rename tcwg-llvm-kernel.sh
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 (b5a5ffb)
\
N -- N -- N refs/heads/llvm-kernel-v3 (a2f8048)
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:
tcwg-llvm-kernel.sh | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.