Skip to content

Conversation

mingmingl-llvm
Copy link
Contributor

@mingmingl-llvm mingmingl-llvm commented Sep 14, 2025

Before this change, setSectionPrefix overwrites existing section prefix with new one unconditionally.

After this change, setSectionPrefix checks for equivalences, updates conditionally and returns whether an update happens.

Update the existing callers to make use of the return value. PR 155337 is a motivating use case whether the 'update' semantic is needed.

Foo->setSectionPrefix("unlikely");
EXPECT_THAT(Foo->getSectionPrefix(), Optional(StrEq("unlikely")));

// Update prefix to empty is the same as clear.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Update/Set since we have a method called Update too?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

//===----------------------------------------------------------------------===//

#include "llvm/IR/GlobalObject.h"
#include "llvm-c/Core.h"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder what this header is used for?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The headers are copied from FunctionTest.cpp. I removed the unused ones now.

Copy link
Contributor

@teresajohnson teresajohnson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title and summary are both mechanical. Maybe add a 1 sentence description of why this change is needed?

}

bool GlobalObject::updateSectionPrefix(StringRef Prefix) {
auto MD = getMetadata(LLVMContext::MD_section_prefix);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use getSectionPrefix instead? It does some assertion checking that could be useful.

Also, does it make sense to just make this the default behavior of setSectionPrefix?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use getSectionPrefix instead? It does some assertion checking that could be useful.

done.

does it make sense to just make this the default behavior of setSectionPrefix?

Implementation wise, the update method currently calls the set method (the other way around). Technically, no existing caller of 'set' depends on the behavior that 'set' method will overwrite, so either way (with a brief comment on the function decl in header) is fine imo. Doing it the current way will avoid affecting (fwiw) existing user in codegen prepare to set function section prefix though.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does it make sense to just make this the default behavior of setSectionPrefix?

Implementation wise, the update method currently calls the set method (the other way around). Technically, no existing caller of 'set' depends on the behavior that 'set' method will overwrite, so either way (with a brief comment on the function decl in header) is fine imo. Doing it the current way will avoid affecting (fwiw) existing user in codegen prepare to set function section prefix though.

How would existing code be affected if setSectionPrefix was changed to do the update? What is the current behavior if setSectionPrefix is used in a context where a different section prefix already exists?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How would existing code be affected if setSectionPrefix was changed to do the update?

The existing code calls 'set' once for function (callsite) or global variable (callsite). If setSectionPrefix is changed to call update, the outcome is the same, except that they get additional comparisons (and makes a difference to compile time in cases where additional comparisons are not needed, like for functions).

What is the current behavior if setSectionPrefix is used in a context where a different section prefix already exists?

It'll overwrite the existing section prefix per implementation, although existing callers calls this function once, so either an update or not works (in terms of the outcome).

Copy link
Contributor Author

@mingmingl-llvm mingmingl-llvm Sep 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per offline discussion, the question is more about why not changing setSectionPrefix in place rather than calling update inside set.

Technically changing setSectionPrefix is definitely an option, but I previously chose to add update to not affect existing callers.

That said, compile-time changes are trivial enough, and all existing use cases also tracks whether a change happens on the IR/MIR, so I just update the PR to change setSectionPrefix in place for simplicity. One other notable change is that codegenprepare previously doesn't track function prefix change as EverMadeChange, but this patch changes it to be. PTAL, thanks!

@mingmingl-llvm mingmingl-llvm marked this pull request as ready for review September 15, 2025 22:48
@llvmbot
Copy link
Member

llvmbot commented Sep 15, 2025

@llvm/pr-subscribers-llvm-transforms

@llvm/pr-subscribers-llvm-ir

Author: Mingming Liu (mingmingl-llvm)

Changes

This PR introduces two main changes to GlobalObject with unit test coverage.

  • Add method updateSectionPrefix method: This method allows updating the section prefix of a GlobalObject.
  • Changes method setSectionPrefix: when the input is an empty string, clear section_prefix metadata.

This is a split of #155337


Full diff: https://github.com/llvm/llvm-project/pull/158460.diff

4 Files Affected:

  • (modified) llvm/include/llvm/IR/GlobalObject.h (+6-1)
  • (modified) llvm/lib/IR/Globals.cpp (+17)
  • (modified) llvm/unittests/IR/CMakeLists.txt (+1)
  • (added) llvm/unittests/IR/GlobalObjectTest.cpp (+76)
diff --git a/llvm/include/llvm/IR/GlobalObject.h b/llvm/include/llvm/IR/GlobalObject.h
index 08a02b42bdc14..740d7fb9bc41f 100644
--- a/llvm/include/llvm/IR/GlobalObject.h
+++ b/llvm/include/llvm/IR/GlobalObject.h
@@ -121,9 +121,14 @@ class GlobalObject : public GlobalValue {
   /// appropriate default object file section.
   LLVM_ABI void setSection(StringRef S);
 
-  /// Set the section prefix for this global object.
+  /// Set the section prefix for this global object. If \p Prefix is empty,
+  /// the section prefix metadata will be cleared if it exists.
   LLVM_ABI void setSectionPrefix(StringRef Prefix);
 
+  /// If \p Prefix is different from existing prefix, update section prefix.
+  /// Returns true if an update happens and false otherwise.
+  LLVM_ABI bool updateSectionPrefix(StringRef Prefix);
+
   /// Get the section prefix for this global object.
   LLVM_ABI std::optional<StringRef> getSectionPrefix() const;
 
diff --git a/llvm/lib/IR/Globals.cpp b/llvm/lib/IR/Globals.cpp
index 11d33e262fecb..0731fcbde106a 100644
--- a/llvm/lib/IR/Globals.cpp
+++ b/llvm/lib/IR/Globals.cpp
@@ -289,11 +289,28 @@ void GlobalObject::setSection(StringRef S) {
 }
 
 void GlobalObject::setSectionPrefix(StringRef Prefix) {
+  if (Prefix.empty()) {
+    setMetadata(LLVMContext::MD_section_prefix, nullptr);
+    return;
+  }
   MDBuilder MDB(getContext());
   setMetadata(LLVMContext::MD_section_prefix,
               MDB.createGlobalObjectSectionPrefix(Prefix));
 }
 
+bool GlobalObject::updateSectionPrefix(StringRef Prefix) {
+  auto MD = getMetadata(LLVMContext::MD_section_prefix);
+  StringRef ExistingPrefix; // Empty by default.
+  if (MD != nullptr)
+    ExistingPrefix = cast<MDString>(MD->getOperand(1))->getString();
+
+  if (ExistingPrefix != Prefix) {
+    setSectionPrefix(Prefix);
+    return true;
+  }
+  return false;
+}
+
 std::optional<StringRef> GlobalObject::getSectionPrefix() const {
   if (MDNode *MD = getMetadata(LLVMContext::MD_section_prefix)) {
     [[maybe_unused]] StringRef MDName =
diff --git a/llvm/unittests/IR/CMakeLists.txt b/llvm/unittests/IR/CMakeLists.txt
index 8b7bd3997ea27..d62ce66ef9d34 100644
--- a/llvm/unittests/IR/CMakeLists.txt
+++ b/llvm/unittests/IR/CMakeLists.txt
@@ -28,6 +28,7 @@ add_llvm_unittest(IRTests
   DominatorTreeBatchUpdatesTest.cpp
   DroppedVariableStatsIRTest.cpp
   FunctionTest.cpp
+  GlobalObjectTest.cpp
   PassBuilderCallbacksTest.cpp
   IRBuilderTest.cpp
   InstructionsTest.cpp
diff --git a/llvm/unittests/IR/GlobalObjectTest.cpp b/llvm/unittests/IR/GlobalObjectTest.cpp
new file mode 100644
index 0000000000000..26949ae3a39fa
--- /dev/null
+++ b/llvm/unittests/IR/GlobalObjectTest.cpp
@@ -0,0 +1,76 @@
+//===- GlobalObjectTest.cpp - Global object unit tests --------------------===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+//
+//===----------------------------------------------------------------------===//
+
+#include "llvm/IR/GlobalObject.h"
+#include "llvm-c/Core.h"
+#include "llvm/AsmParser/Parser.h"
+#include "llvm/IR/Module.h"
+#include "llvm/Support/SourceMgr.h"
+#include "gmock/gmock.h"
+#include "gtest/gtest.h"
+using namespace llvm;
+namespace {
+using testing::Eq;
+using testing::Optional;
+using testing::StrEq;
+
+static std::unique_ptr<Module> parseIR(LLVMContext &C, const char *IR) {
+  SMDiagnostic Err;
+  std::unique_ptr<Module> Mod = parseAssemblyString(IR, Err, C);
+  if (!Mod)
+    Err.print("GlobalObjectTests", errs());
+  return Mod;
+}
+
+static LLVMContext C;
+static std::unique_ptr<Module> M;
+
+class GlobalObjectTest : public testing::Test {
+public:
+  static void SetUpTestSuite() {
+    M = parseIR(C, R"(
+@foo = global i32 3, !section_prefix !0
+@bar = global i32 0
+
+!0 = !{!"section_prefix", !"hot"}
+)");
+  }
+};
+
+TEST_F(GlobalObjectTest, SectionPrefix) {
+  GlobalVariable *Foo = M->getGlobalVariable("foo");
+
+  // Initial section prefix is hot.
+  ASSERT_NE(Foo, nullptr);
+  ASSERT_THAT(Foo->getSectionPrefix(), Optional(StrEq("hot")));
+
+  // No actual update.
+  EXPECT_FALSE(Foo->updateSectionPrefix("hot"));
+
+  // Update prefix from hot to unlikely.
+  Foo->setSectionPrefix("unlikely");
+  EXPECT_THAT(Foo->getSectionPrefix(), Optional(StrEq("unlikely")));
+
+  // Update prefix to empty is the same as clear.
+  Foo->setSectionPrefix("");
+  EXPECT_THAT(Foo->getSectionPrefix(), Eq(std::nullopt));
+
+  GlobalVariable *Bar = M->getGlobalVariable("bar");
+
+  // Initial section prefix is empty.
+  ASSERT_NE(Bar, nullptr);
+  ASSERT_THAT(Bar->getSectionPrefix(), Eq(std::nullopt));
+
+  // No actual update.
+  EXPECT_FALSE(Bar->updateSectionPrefix(""));
+
+  // Update from empty to hot.
+  EXPECT_TRUE(Bar->updateSectionPrefix("hot"));
+  EXPECT_THAT(Bar->getSectionPrefix(), Optional(StrEq("hot")));
+}
+} // namespace

Copy link
Contributor Author

@mingmingl-llvm mingmingl-llvm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title and summary are both mechanical. Maybe add a 1 sentence description of why this change is needed?

Sure! The updated PR description points to the use case.

Also clicked 'ready for review' to make this non-draft. Forgot to do this when I requested reviews before.

Foo->setSectionPrefix("unlikely");
EXPECT_THAT(Foo->getSectionPrefix(), Optional(StrEq("unlikely")));

// Update prefix to empty is the same as clear.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

//===----------------------------------------------------------------------===//

#include "llvm/IR/GlobalObject.h"
#include "llvm-c/Core.h"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The headers are copied from FunctionTest.cpp. I removed the unused ones now.

}

bool GlobalObject::updateSectionPrefix(StringRef Prefix) {
auto MD = getMetadata(LLVMContext::MD_section_prefix);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use getSectionPrefix instead? It does some assertion checking that could be useful.

done.

does it make sense to just make this the default behavior of setSectionPrefix?

Implementation wise, the update method currently calls the set method (the other way around). Technically, no existing caller of 'set' depends on the behavior that 'set' method will overwrite, so either way (with a brief comment on the function decl in header) is fine imo. Doing it the current way will avoid affecting (fwiw) existing user in codegen prepare to set function section prefix though.

@snehasish
Copy link

Did you push your changes yet? I don't see the updated diff.

@mingmingl-llvm
Copy link
Contributor Author

Did you push your changes yet? I don't see the updated diff.

Sorry! This is pushed now.

Copy link

@snehasish snehasish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

EXPECT_TRUE(Bar->updateSectionPrefix("hot"));
EXPECT_THAT(Bar->getSectionPrefix(), Optional(StrEq("hot")));

// Teset that update method returns true and section prefix is cleared.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: test

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

@mingmingl-llvm mingmingl-llvm changed the title [NFCI][Globals]For GlobalObjects, add updateSectionPrefix and change setSectionPrefix to handle empty strings [NFCI][Globals] In GlobalObjects::setSectionPrefix, do conditional update if existing prefix is not equivalent to the new one. Returns whether prefix changed. Sep 16, 2025
Copy link
Contributor

@teresajohnson teresajohnson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm but comment needs a slight fix as noted below.


/// Set the section prefix for this global object.
LLVM_ABI void setSectionPrefix(StringRef Prefix);
/// If existing prefix is different from \p Prefix is different, set it to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

redundant "different"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for the catch! fixed it.

@mingmingl-llvm mingmingl-llvm enabled auto-merge (squash) September 16, 2025 18:13
@mingmingl-llvm
Copy link
Contributor Author

In both windows and linux, the failed tests are irrelevant. Going to merge this change.

  ********************
  Failed Tests (2):
    LLVM :: CodeGen/X86/memcmp-pgso-x32.ll
    LLVM :: CodeGen/X86/memcmp-pgso.ll

@mingmingl-llvm mingmingl-llvm merged commit 027bccc into main Sep 16, 2025
7 of 9 checks passed
@mingmingl-llvm mingmingl-llvm deleted the users/mingmingl-llvm/unittest branch September 16, 2025 19:01
@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 16, 2025

LLVM Buildbot has detected a new failure on builder llvm-clang-x86_64-sie-ubuntu-fast running on sie-linux-worker while building llvm at step 6 "test-build-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/144/builds/35592

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/llc < /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/FileCheck /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/llc -mtriple=x86_64-unknown-unknown
# note: command had no output on stdout or stderr
# executed command: /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/FileCheck /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | �[1m/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: �[0m�[0;1;31merror: �[0m�[1mX64-NEXT: expected string not found in input
�[0m# | �[1m�[0m; X64-NEXT: jne .LBB4_3
# | �[0;1;32m            ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:66:15: �[0m�[0;1;30mnote: �[0m�[1mscanning from here
�[0m# | �[1m�[0m cmpw %cx, %ax
# | �[0;1;32m              ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:67:2: �[0m�[0;1;30mnote: �[0m�[1mpossible intended match here
�[0m# | �[1m�[0m jne .LBB4_1
# | �[0;1;32m ^
�[0m# | �[0;1;32m�[0m�[1m/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: �[0m�[0;1;31merror: �[0m�[1mX64-NEXT: expected string not found in input
�[0m# | �[1m�[0m; X64-NEXT: jne .LBB9_3
# | �[0;1;32m            ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:146:17: �[0m�[0;1;30mnote: �[0m�[1mscanning from here
�[0m# | �[1m�[0m cmpl %ecx, %eax
# | �[0;1;32m                ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:147:2: �[0m�[0;1;30mnote: �[0m�[1mpossible intended match here
�[0m# | �[1m�[0m jne .LBB9_1
# | �[0;1;32m ^
�[0m# | �[0;1;32m�[0m�[1m/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: �[0m�[0;1;31merror: �[0m�[1mX64-NEXT: expected string not found in input
�[0m# | �[1m�[0m; X64-NEXT: jne .LBB15_2
# | �[0;1;32m            ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:242:17: �[0m�[0;1;30mnote: �[0m�[1mscanning from here
�[0m# | �[1m�[0m cmpq %rdx, %rcx
# | �[0;1;32m                ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:243:2: �[0m�[0;1;30mnote: �[0m�[1mpossible intended match here
�[0m# | �[1m�[0m jne .LBB15_1
# | �[0;1;32m ^
�[0m# | �[0;1;32m�[0m�[1m/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:277:13: �[0m�[0;1;31merror: �[0m�[1mX64-NEXT: expected string not found in input
�[0m# | �[1m�[0m; X64-NEXT: jne .LBB16_2
# | �[0;1;32m            ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:272:17: �[0m�[0;1;30mnote: �[0m�[1mscanning from here
�[0m# | �[1m�[0m cmpq %rdx, %rcx
# | �[0;1;32m                ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:273:2: �[0m�[0;1;30mnote: �[0m�[1mpossible intended match here
�[0m# | �[1m�[0m jne .LBB16_1
# | �[0;1;32m ^
�[0m# | �[0;1;32m�[0m
# | Input file: <stdin>
# | Check file: /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 16, 2025

LLVM Buildbot has detected a new failure on builder fuchsia-x86_64-linux running on fuchsia-debian-64-us-central1-a-1 while building llvm at step 4 "annotate".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/11/builds/24109

Here is the relevant piece of the build log for the reference
Step 4 (annotate) failure: 'python ../llvm-zorg/zorg/buildbot/builders/annotated/fuchsia-linux.py ...' (failure)
...
  Passed           : 46849 (97.55%)
  Expectedly Failed:    28 (0.06%)
[1434/1436] Linking CXX executable unittests/tools/llvm-exegesis/LLVMExegesisTests
[1435/1436] Running the LLVM regression tests
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld.lld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/ld.lld
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using lld-link: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/lld-link
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/ld64.lld
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/wasm-ld
-- Testing: 61114 tests, 60 workers --
Testing:  0.. 10.. 20.. 30.. 40
FAIL: LLVM :: CodeGen/X86/memcmp-pgso-x32.ll (27888 of 61114)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso-x32.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/llc < /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll -mtriple=i686-unknown-unknown -mattr=cmov | /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/FileCheck /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# executed command: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/llc -mtriple=i686-unknown-unknown -mattr=cmov
# executed command: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/FileCheck /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# .---command stderr------------
# | /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:83:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:75:15: note: scanning from here
# |  cmpw %si, %dx
# |               ^
# | <stdin>:76:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:173:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:167:17: note: scanning from here
# |  cmpl %esi, %edx
# |                 ^
# | <stdin>:168:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:219:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB11_2
# |             ^
# | <stdin>:214:17: note: scanning from here
# |  cmpl %edx, %ecx
# |                 ^
# | <stdin>:215:2: note: possible intended match here
# |  jne .LBB11_1
# |  ^
# | 
Step 7 (check) failure: check (failure)
...
  Passed           : 46849 (97.55%)
  Expectedly Failed:    28 (0.06%)
[1434/1436] Linking CXX executable unittests/tools/llvm-exegesis/LLVMExegesisTests
[1435/1436] Running the LLVM regression tests
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld.lld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/ld.lld
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using lld-link: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/lld-link
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/ld64.lld
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/wasm-ld
-- Testing: 61114 tests, 60 workers --
Testing:  0.. 10.. 20.. 30.. 40
FAIL: LLVM :: CodeGen/X86/memcmp-pgso-x32.ll (27888 of 61114)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso-x32.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/llc < /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll -mtriple=i686-unknown-unknown -mattr=cmov | /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/FileCheck /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# executed command: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/llc -mtriple=i686-unknown-unknown -mattr=cmov
# executed command: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-b4bd1evt/bin/FileCheck /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# .---command stderr------------
# | /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:83:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:75:15: note: scanning from here
# |  cmpw %si, %dx
# |               ^
# | <stdin>:76:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:173:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:167:17: note: scanning from here
# |  cmpl %esi, %edx
# |                 ^
# | <stdin>:168:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:219:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB11_2
# |             ^
# | <stdin>:214:17: note: scanning from here
# |  cmpl %edx, %ecx
# |                 ^
# | <stdin>:215:2: note: possible intended match here
# |  jne .LBB11_1
# |  ^
# | 

llvm-sync bot pushed a commit to arm/arm-toolchain that referenced this pull request Sep 16, 2025
…, do conditional update if existing prefix is not equivalent to the new one. Returns whether prefix changed." (#159159)

Reverts llvm/llvm-project#158460 due to buildbot failures
@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 16, 2025

LLVM Buildbot has detected a new failure on builder clang-m68k-linux-cross running on suse-gary-m68k-cross while building llvm at step 5 "ninja check 1".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/27/builds/16139

Here is the relevant piece of the build log for the reference
Step 5 (ninja check 1) failure: stage 1 checked (failure)
...
[183/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Driver/DXCModeTest.cpp.o
[184/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Parse/ParseHLSLRootSignatureTest.cpp.o
[185/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/ArenaTest.cpp.o
[186/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/FormulaTest.cpp.o
[187/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Driver/ToolChainTest.cpp.o
[188/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/DataflowAnalysisContextTest.cpp.o
[189/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/CloneDetectionTest.cpp.o
[190/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/MacroExpansionContextTest.cpp.o
[191/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/ValueTest.cpp.o
[192/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/SignAnalysisTest.cpp.o
FAILED: tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/SignAnalysisTest.cpp.o 
/usr/bin/c++ -DGTEST_HAS_RTTI=0 -DLLVM_BUILD_STATIC -D_DEBUG -D_GLIBCXX_ASSERTIONS -D_GLIBCXX_USE_CXX11_ABI=1 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/tools/clang/unittests -I/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/clang/unittests -I/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/clang/include -I/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/tools/clang/include -I/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/include -I/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/llvm/include -I/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/clang/unittests/Tooling -I/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/third-party/unittest/googletest/include -I/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/third-party/unittest/googlemock/include -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-uninitialized -Wno-nonnull -Wno-class-memaccess -Wno-dangling-reference -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -O3 -DNDEBUG -std=c++17  -Wno-variadic-macros -fno-exceptions -funwind-tables -fno-rtti -UNDEBUG -Wno-suggest-override -MD -MT tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/SignAnalysisTest.cpp.o -MF tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/SignAnalysisTest.cpp.o.d -o tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/SignAnalysisTest.cpp.o -c /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/clang/unittests/Analysis/FlowSensitive/SignAnalysisTest.cpp
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
[193/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/StaticAnalyzer/AnalyzerOptionsTest.cpp.o
[194/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/SmartPointerAccessorCachingTest.cpp.o
[195/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/DeterminismTest.cpp.o
[196/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/RecordOpsTest.cpp.o
[197/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/MapLatticeTest.cpp.o
[198/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/CFGTest.cpp.o
[199/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/MatchSwitchTest.cpp.o
[200/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/CFGMatchSwitchTest.cpp.o
[201/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/LifetimeSafetyTest.cpp.o
[202/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/StaticAnalyzer/BlockEntranceCallbackTest.cpp.o
[203/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/CFGDominatorTree.cpp.o
[204/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/StaticAnalyzer/CallEventTest.cpp.o
[205/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/StaticAnalyzer/APSIntTypeTest.cpp.o
[206/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/LoggerTest.cpp.o
[207/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/SimplifyConstraintsTest.cpp.o
[208/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/ASTOpsTest.cpp.o
[209/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/TransferBranchTest.cpp.o
[210/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/TestingSupport.cpp.o
[211/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/DebugSupportTest.cpp.o
[212/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/CachedConstAccessorsLatticeTest.cpp.o
[213/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/IntervalPartitionTest.cpp.o
[214/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/TestingSupportTest.cpp.o
[215/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/ChromiumCheckModelTest.cpp.o
[216/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/SingleVarConstantPropagationTest.cpp.o
[217/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/MultiVarConstantPropagationTest.cpp.o
[218/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/DataflowEnvironmentTest.cpp.o
[219/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/ExprMutationAnalyzerTest.cpp.o
[220/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/StaticAnalyzer/BugReportInterestingnessTest.cpp.o
[221/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/UncheckedOptionalAccessModelTest.cpp.o
[222/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/StaticAnalyzer/CallDescriptionTest.cpp.o
[223/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/WatchedLiteralsSolverTest.cpp.o
[224/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/TypeErasedDataflowAnalysisTest.cpp.o
[225/1190] Building CXX object tools/clang/unittests/CMakeFiles/AllClangUnitTests.dir/Analysis/FlowSensitive/TransferTest.cpp.o
ninja: build stopped: subcommand failed.

mingmingl-llvm added a commit that referenced this pull request Sep 16, 2025
…itional update if existing prefix is not equivalent to the new one. Returns whether prefix changed." (#159161)

This is a reland of #158460

Test failures are gone once I undo the changes in codegenprepare.
@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 16, 2025

LLVM Buildbot has detected a new failure on builder arc-builder running on arc-worker while building llvm at step 6 "test-build-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/3/builds/22025

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/buildbot/worker/arc-folder/build/bin/llc < /buildbot/worker/arc-folder/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /buildbot/worker/arc-folder/build/bin/FileCheck /buildbot/worker/arc-folder/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /buildbot/worker/arc-folder/build/bin/llc -mtriple=x86_64-unknown-unknown
# executed command: /buildbot/worker/arc-folder/build/bin/FileCheck /buildbot/worker/arc-folder/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /buildbot/worker/arc-folder/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /buildbot/worker/arc-folder/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /buildbot/worker/arc-folder/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^
# | /buildbot/worker/arc-folder/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:277:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB16_2
# |             ^
# | <stdin>:272:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:273:2: note: possible intended match here
# |  jne .LBB16_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /buildbot/worker/arc-folder/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll
# | 
...

llvm-sync bot pushed a commit to arm/arm-toolchain that referenced this pull request Sep 16, 2025
…ix, do conditional update if existing prefix is not equivalent to the new one. Returns whether prefix changed." (#159161)

This is a reland of llvm/llvm-project#158460

Test failures are gone once I undo the changes in codegenprepare.
@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 16, 2025

LLVM Buildbot has detected a new failure on builder llvm-clang-x86_64-darwin running on doug-worker-3 while building llvm at step 6 "test-build-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/23/builds/13935

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/Volumes/RAMDisk/buildbot-root/x86_64-darwin/build/bin/llc < /Volumes/RAMDisk/buildbot-root/x86_64-darwin/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /Volumes/RAMDisk/buildbot-root/x86_64-darwin/build/bin/FileCheck /Volumes/RAMDisk/buildbot-root/x86_64-darwin/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /Volumes/RAMDisk/buildbot-root/x86_64-darwin/build/bin/llc -mtriple=x86_64-unknown-unknown
# note: command had no output on stdout or stderr
# executed command: /Volumes/RAMDisk/buildbot-root/x86_64-darwin/build/bin/FileCheck /Volumes/RAMDisk/buildbot-root/x86_64-darwin/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /Volumes/RAMDisk/buildbot-root/x86_64-darwin/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /Volumes/RAMDisk/buildbot-root/x86_64-darwin/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /Volumes/RAMDisk/buildbot-root/x86_64-darwin/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^
# | /Volumes/RAMDisk/buildbot-root/x86_64-darwin/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:277:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB16_2
# |             ^
# | <stdin>:272:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:273:2: note: possible intended match here
# |  jne .LBB16_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /Volumes/RAMDisk/buildbot-root/x86_64-darwin/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 16, 2025

LLVM Buildbot has detected a new failure on builder clang-aarch64-sve2-vla running on linaro-g4-02 while building llvm at step 7 "ninja check 1".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/198/builds/7911

Here is the relevant piece of the build log for the reference
Step 7 (ninja check 1) failure: stage 1 checked (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso-x32.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/stage1/bin/llc < /home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll -mtriple=i686-unknown-unknown -mattr=cmov | /home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/stage1/bin/FileCheck /home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# executed command: /home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/stage1/bin/llc -mtriple=i686-unknown-unknown -mattr=cmov
# executed command: /home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/stage1/bin/FileCheck /home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# .---command stderr------------
# | /home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:83:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:75:15: note: scanning from here
# |  cmpw %si, %dx
# |               ^
# | <stdin>:76:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:173:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:167:17: note: scanning from here
# |  cmpl %esi, %edx
# |                 ^
# | <stdin>:168:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:219:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB11_2
# |             ^
# | <stdin>:214:17: note: scanning from here
# |  cmpl %edx, %ecx
# |                 ^
# | <stdin>:215:2: note: possible intended match here
# |  jne .LBB11_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /home/tcwg-buildbot/worker/clang-aarch64-sve2-vla/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# |             .
# |             .
# |             .
# |            70:  movl 8(%esp), %eax 
# |            71:  movzwl (%eax), %edx 
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder ppc64le-lld-multistage-test running on ppc64le-lld-multistage-test while building llvm at step 7 "test-build-stage1-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/168/builds/16188

Here is the relevant piece of the build log for the reference
Step 7 (test-build-stage1-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage1/bin/llc < /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage1/bin/FileCheck /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage1/bin/llc -mtriple=x86_64-unknown-unknown
# executed command: /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage1/bin/FileCheck /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:277:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB16_2
# |             ^
# | <stdin>:272:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:273:2: note: possible intended match here
# |  jne .LBB16_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll
# | 
...
Step 13 (test-build-stage2-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso-x32.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage2/bin/llc < /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll -mtriple=i686-unknown-unknown -mattr=cmov | /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage2/bin/FileCheck /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# executed command: /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage2/bin/llc -mtriple=i686-unknown-unknown -mattr=cmov
# executed command: /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage2/bin/FileCheck /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# .---command stderr------------
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:83:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:75:15: note: scanning from here
# |  cmpw %si, %dx
# |               ^
# | <stdin>:76:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:173:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:167:17: note: scanning from here
# |  cmpl %esi, %edx
# |                 ^
# | <stdin>:168:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:219:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB11_2
# |             ^
# | <stdin>:214:17: note: scanning from here
# |  cmpl %edx, %ecx
# |                 ^
# | <stdin>:215:2: note: possible intended match here
# |  jne .LBB11_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# |             .
# |             .
# |             .
# |            70:  movl 8(%esp), %eax 
# |            71:  movzwl (%eax), %edx 
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder clang-ppc64le-rhel running on ppc64le-clang-rhel-test while building llvm at step 7 "test-build-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/145/builds/9807

Here is the relevant piece of the build log for the reference
Step 7 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso-x32.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/build/bin/llc < /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll -mtriple=i686-unknown-unknown -mattr=cmov | /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/build/bin/FileCheck /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# executed command: /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/build/bin/llc -mtriple=i686-unknown-unknown -mattr=cmov
# executed command: /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/build/bin/FileCheck /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# .---command stderr------------
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:83:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:75:15: note: scanning from here
# |  cmpw %si, %dx
# |               ^
# | <stdin>:76:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:173:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:167:17: note: scanning from here
# |  cmpl %esi, %edx
# |                 ^
# | <stdin>:168:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:219:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB11_2
# |             ^
# | <stdin>:214:17: note: scanning from here
# |  cmpl %edx, %ecx
# |                 ^
# | <stdin>:215:2: note: possible intended match here
# |  jne .LBB11_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-rhel-test/clang-ppc64le-rhel/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# |             .
# |             .
# |             .
# |            70:  movl 8(%esp), %eax 
# |            71:  movzwl (%eax), %edx 
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder llvm-nvptx64-nvidia-ubuntu running on as-builder-7 while building llvm at step 6 "test-build-unified-tree-check-llvm".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/160/builds/24995

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-llvm) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso-x32.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/build/bin/llc < /home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll -mtriple=i686-unknown-unknown -mattr=cmov | /home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# executed command: /home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/build/bin/llc -mtriple=i686-unknown-unknown -mattr=cmov
# executed command: /home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# .---command stderr------------
# | /home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:83:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:75:15: note: scanning from here
# |  cmpw %si, %dx
# |               ^
# | <stdin>:76:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:173:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:167:17: note: scanning from here
# |  cmpl %esi, %edx
# |                 ^
# | <stdin>:168:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:219:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB11_2
# |             ^
# | <stdin>:214:17: note: scanning from here
# |  cmpl %edx, %ecx
# |                 ^
# | <stdin>:215:2: note: possible intended match here
# |  jne .LBB11_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /home/buildbot/worker/as-builder-7/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# |             .
# |             .
# |             .
# |            70:  movl 8(%esp), %eax 
# |            71:  movzwl (%eax), %edx 
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder llvm-nvptx-nvidia-ubuntu running on as-builder-7 while building llvm at step 6 "test-build-unified-tree-check-llvm".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/180/builds/25135

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-llvm) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/build/bin/llc < /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/build/bin/llc -mtriple=x86_64-unknown-unknown
# executed command: /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^
# | /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:277:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB16_2
# |             ^
# | <stdin>:272:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:273:2: note: possible intended match here
# |  jne .LBB16_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /home/buildbot/worker/as-builder-7/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll
# | 
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder clang-debian-cpp20 running on clang-debian-cpp20 while building llvm at step 6 "test-build-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/108/builds/17751

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/bin/llc < /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/bin/FileCheck /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/bin/llc -mtriple=x86_64-unknown-unknown
# executed command: /vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/bin/FileCheck /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^
# | /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:277:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB16_2
# |             ^
# | <stdin>:272:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:273:2: note: possible intended match here
# |  jne .LBB16_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll
# | 
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder clang-aarch64-global-isel running on linaro-clang-aarch64-global-isel while building llvm at step 7 "ninja check 1".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/125/builds/10397

Here is the relevant piece of the build log for the reference
Step 7 (ninja check 1) failure: stage 1 checked (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/tcwg-buildbot/worker/clang-aarch64-global-isel/stage1/bin/llc < /home/tcwg-buildbot/worker/clang-aarch64-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /home/tcwg-buildbot/worker/clang-aarch64-global-isel/stage1/bin/FileCheck /home/tcwg-buildbot/worker/clang-aarch64-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /home/tcwg-buildbot/worker/clang-aarch64-global-isel/stage1/bin/llc -mtriple=x86_64-unknown-unknown
# executed command: /home/tcwg-buildbot/worker/clang-aarch64-global-isel/stage1/bin/FileCheck /home/tcwg-buildbot/worker/clang-aarch64-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /home/tcwg-buildbot/worker/clang-aarch64-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/tcwg-buildbot/worker/clang-aarch64-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/tcwg-buildbot/worker/clang-aarch64-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^
# | /home/tcwg-buildbot/worker/clang-aarch64-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso.ll:277:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB16_2
# |             ^
# | <stdin>:272:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:273:2: note: possible intended match here
# |  jne .LBB16_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /home/tcwg-buildbot/worker/clang-aarch64-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso.ll
# | 
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder sanitizer-x86_64-linux-fast running on sanitizer-buildbot4 while building llvm at step 2 "annotate".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/169/builds/14972

Here is the relevant piece of the build log for the reference
Step 2 (annotate) failure: 'python ../sanitizer_buildbot/sanitizers/zorg/buildbot/builders/sanitizers/buildbot_selector.py' (failure)
...
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using lld-link: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/lld-link
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/ld64.lld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/wasm-ld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld.lld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/ld.lld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using lld-link: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/lld-link
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/ld64.lld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/wasm-ld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/main.py:74: note: The test suite configuration requested an individual test timeout of 0 seconds but a timeout of 900 seconds was requested on the command line. Forcing timeout to be 900 seconds.
-- Testing: 91977 tests, 64 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60
FAIL: LLVM :: CodeGen/X86/memcmp-pgso.ll (14081 of 91977)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/llc < /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/FileCheck /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/llc -mtriple=x86_64-unknown-unknown
# note: command had no output on stdout or stderr
# executed command: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/FileCheck /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^
Step 10 (stage2/asan_ubsan check) failure: stage2/asan_ubsan check (failure)
...
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using lld-link: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/lld-link
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/ld64.lld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/wasm-ld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld.lld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/ld.lld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using lld-link: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/lld-link
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/ld64.lld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/wasm-ld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/main.py:74: note: The test suite configuration requested an individual test timeout of 0 seconds but a timeout of 900 seconds was requested on the command line. Forcing timeout to be 900 seconds.
-- Testing: 91977 tests, 64 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60
FAIL: LLVM :: CodeGen/X86/memcmp-pgso.ll (14081 of 91977)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/llc < /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/FileCheck /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/llc -mtriple=x86_64-unknown-unknown
# note: command had no output on stdout or stderr
# executed command: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_asan_ubsan/bin/FileCheck /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^
Step 14 (stage2/msan check) failure: stage2/msan check (failure)
...
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using lld-link: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/lld-link
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/ld64.lld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/wasm-ld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld.lld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/ld.lld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using lld-link: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/lld-link
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/ld64.lld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/wasm-ld
llvm-lit: /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/utils/lit/lit/main.py:74: note: The test suite configuration requested an individual test timeout of 0 seconds but a timeout of 900 seconds was requested on the command line. Forcing timeout to be 900 seconds.
-- Testing: 91976 tests, 64 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 
FAIL: LLVM :: CodeGen/X86/memcmp-pgso.ll (5556 of 91976)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/llc < /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/FileCheck /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/llc -mtriple=x86_64-unknown-unknown
# note: command had no output on stdout or stderr
# executed command: /home/b/sanitizer-x86_64-linux-fast/build/llvm_build_msan/bin/FileCheck /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/b/sanitizer-x86_64-linux-fast/build/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder clang-arm64-windows-msvc running on linaro-armv8-windows-msvc-04 while building llvm at step 6 "test-build-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/161/builds/7898

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso-x32.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
c:\users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\bin\llc.exe < C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\llvm-project\llvm\test\CodeGen\X86\memcmp-pgso-x32.ll -mtriple=i686-unknown-unknown -mattr=cmov | c:\users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\bin\filecheck.exe C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\llvm-project\llvm\test\CodeGen\X86\memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# executed command: 'c:\users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\bin\llc.exe' -mtriple=i686-unknown-unknown -mattr=cmov
# executed command: 'c:\users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\bin\filecheck.exe' 'C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\llvm-project\llvm\test\CodeGen\X86\memcmp-pgso-x32.ll' --check-prefixes=X86,X86-NOSSE
# .---command stderr------------
# | C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\llvm-project\llvm\test\CodeGen\X86\memcmp-pgso-x32.ll:83:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:75:15: note: scanning from here
# |  cmpw %si, %dx
# |               ^
# | <stdin>:76:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\llvm-project\llvm\test\CodeGen\X86\memcmp-pgso-x32.ll:173:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:167:17: note: scanning from here
# |  cmpl %esi, %edx
# |                 ^
# | <stdin>:168:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\llvm-project\llvm\test\CodeGen\X86\memcmp-pgso-x32.ll:219:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB11_2
# |             ^
# | <stdin>:214:17: note: scanning from here
# |  cmpl %edx, %ecx
# |                 ^
# | <stdin>:215:2: note: possible intended match here
# |  jne .LBB11_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\llvm-project\llvm\test\CodeGen\X86\memcmp-pgso-x32.ll
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# |             .
# |             .
# |             .
# |            70:  movl 8(%esp), %eax 
# |            71:  movzwl (%eax), %edx 
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder clang-ppc64le-linux-test-suite running on ppc64le-clang-test-suite while building llvm at step 3 "clean-build-dir".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/95/builds/18270

Here is the relevant piece of the build log for the reference
Step 3 (clean-build-dir) failure: Delete failed. (failure) (timed out)
Step 6 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/bin/llc < /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/bin/FileCheck /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/bin/llc -mtriple=x86_64-unknown-unknown
# executed command: /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/bin/FileCheck /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^
# | /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:277:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB16_2
# |             ^
# | <stdin>:272:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:273:2: note: possible intended match here
# |  jne .LBB16_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll
# | 
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder llvm-clang-x86_64-gcc-ubuntu-no-asserts running on doug-worker-6 while building llvm at step 6 "test-build-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/202/builds/3365

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso-x32.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/buildbot/buildbot-root/gcc-no-asserts/build/bin/llc < /home/buildbot/buildbot-root/gcc-no-asserts/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll -mtriple=i686-unknown-unknown -mattr=cmov | /home/buildbot/buildbot-root/gcc-no-asserts/build/bin/FileCheck /home/buildbot/buildbot-root/gcc-no-asserts/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# executed command: /home/buildbot/buildbot-root/gcc-no-asserts/build/bin/llc -mtriple=i686-unknown-unknown -mattr=cmov
# note: command had no output on stdout or stderr
# executed command: /home/buildbot/buildbot-root/gcc-no-asserts/build/bin/FileCheck /home/buildbot/buildbot-root/gcc-no-asserts/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# .---command stderr------------
# | �[1m/home/buildbot/buildbot-root/gcc-no-asserts/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:83:13: �[0m�[0;1;31merror: �[0m�[1mX86-NEXT: expected string not found in input
�[0m# | �[1m�[0m; X86-NEXT: jne .LBB4_3
# | �[0;1;32m            ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:75:15: �[0m�[0;1;30mnote: �[0m�[1mscanning from here
�[0m# | �[1m�[0m cmpw %si, %dx
# | �[0;1;32m              ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:76:2: �[0m�[0;1;30mnote: �[0m�[1mpossible intended match here
�[0m# | �[1m�[0m jne .LBB4_1
# | �[0;1;32m ^
�[0m# | �[0;1;32m�[0m�[1m/home/buildbot/buildbot-root/gcc-no-asserts/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:173:13: �[0m�[0;1;31merror: �[0m�[1mX86-NEXT: expected string not found in input
�[0m# | �[1m�[0m; X86-NEXT: jne .LBB9_3
# | �[0;1;32m            ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:167:17: �[0m�[0;1;30mnote: �[0m�[1mscanning from here
�[0m# | �[1m�[0m cmpl %esi, %edx
# | �[0;1;32m                ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:168:2: �[0m�[0;1;30mnote: �[0m�[1mpossible intended match here
�[0m# | �[1m�[0m jne .LBB9_1
# | �[0;1;32m ^
�[0m# | �[0;1;32m�[0m�[1m/home/buildbot/buildbot-root/gcc-no-asserts/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:219:13: �[0m�[0;1;31merror: �[0m�[1mX86-NEXT: expected string not found in input
�[0m# | �[1m�[0m; X86-NEXT: jne .LBB11_2
# | �[0;1;32m            ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:214:17: �[0m�[0;1;30mnote: �[0m�[1mscanning from here
�[0m# | �[1m�[0m cmpl %edx, %ecx
# | �[0;1;32m                ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:215:2: �[0m�[0;1;30mnote: �[0m�[1mpossible intended match here
�[0m# | �[1m�[0m jne .LBB11_1
# | �[0;1;32m ^
�[0m# | �[0;1;32m�[0m
# | Input file: <stdin>
# | Check file: /home/buildbot/buildbot-root/gcc-no-asserts/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# | �[1m�[0m�[0;1;30m             1: �[0m�[1m�[0;1;46m .file "<stdin>" �[0m
# | �[0;1;30m             2: �[0m�[1m�[0;1;46m .section .text.unlikely.,"ax",@progbits �[0m
# | �[0;1;30m             3: �[0m�[1m�[0;1;46m .globl length2 # -- Begin function length2 �[0m
# | �[0;1;30m             4: �[0m�[1m�[0;1;46m .p2align 4 �[0m
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder sanitizer-ppc64le-linux running on ppc64le-sanitizer while building llvm at step 2 "annotate".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/72/builds/15098

Here is the relevant piece of the build log for the reference
Step 2 (annotate) failure: 'python ../sanitizer_buildbot/sanitizers/zorg/buildbot/builders/sanitizers/buildbot_selector.py' (failure)
...
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/llvm/utils/lit/lit/discovery.py:276: warning: input '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/Unit' contained no tests
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
Testing:  0.. 10.. 20.. 30.. 40.. 50.
FAIL: SanitizerCommon-asan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp (2982 of 5236)
******************** TEST 'SanitizerCommon-asan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp' FAILED ********************
Exit Code: 134

Command Output (stderr):
--
/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang  --driver-mode=g++ -gline-tables-only -fsanitize=address  -m64 -fno-function-sections -funwind-tables -nobuiltininc -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include -idirafter /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include -resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build -Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux  -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp &&  /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp # RUN: at line 2
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang --driver-mode=g++ -gline-tables-only -fsanitize=address -m64 -fno-function-sections -funwind-tables -nobuiltininc -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include -idirafter /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include -resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build -Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp
getpwnam_r_invalid_user.cpp.tmp: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp:17: int main(): Assertion `res == 0 || res == ENOENT' failed.
/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.script: line 1: 1766331 Aborted                 /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp

--

********************
Testing:  0.. 10.. 20.. 30.. 40.. 50.
FAIL: SanitizerCommon-msan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp (3005 of 5236)
******************** TEST 'SanitizerCommon-msan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp' FAILED ********************
Exit Code: 134

Command Output (stderr):
--
/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang  --driver-mode=g++ -gline-tables-only -fsanitize=memory  -m64 -fno-function-sections -funwind-tables -nobuiltininc -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include -idirafter /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include -resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build -Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux  -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp &&  /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp # RUN: at line 2
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang --driver-mode=g++ -gline-tables-only -fsanitize=memory -m64 -fno-function-sections -funwind-tables -nobuiltininc -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include -idirafter /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include -resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build -Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp
getpwnam_r_invalid_user.cpp.tmp: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp:17: int main(): Assertion `res == 0 || res == ENOENT' failed.
/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.script: line 1: 1773391 Aborted                 /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp

--

********************
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60..
FAIL: SanitizerCommon-lsan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp (3563 of 5236)
******************** TEST 'SanitizerCommon-lsan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp' FAILED ********************
Exit Code: 134

Command Output (stderr):
--
/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang  --driver-mode=g++ -gline-tables-only -fsanitize=leak  -m64 -fno-function-sections -funwind-tables -nobuiltininc -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include -idirafter /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include -resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build -Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux  -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/lsan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp &&  /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/lsan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp # RUN: at line 2
Step 14 (test standalone compiler-rt) failure: test standalone compiler-rt (failure)
...
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/llvm/utils/lit/lit/discovery.py:276: warning: input '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/Unit' contained no tests
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
llvm-lit: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/lit.common.cfg.py:60: warning: Path reported by clang does not exist: "/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/powerpc64le-unknown-linux-gnu". This path was found by running ['/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang', '--target=powerpc64le-unknown-linux-gnu', '-m64', '-fno-function-sections', '-nobuiltininc', '-I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include', '-idirafter', '/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include', '-resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build', '-Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux', '-print-runtime-dir'].
Testing:  0.. 10.. 20.. 30.. 40.. 50.
FAIL: SanitizerCommon-asan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp (2982 of 5236)
******************** TEST 'SanitizerCommon-asan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp' FAILED ********************
Exit Code: 134

Command Output (stderr):
--
/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang  --driver-mode=g++ -gline-tables-only -fsanitize=address  -m64 -fno-function-sections -funwind-tables -nobuiltininc -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include -idirafter /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include -resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build -Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux  -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp &&  /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp # RUN: at line 2
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang --driver-mode=g++ -gline-tables-only -fsanitize=address -m64 -fno-function-sections -funwind-tables -nobuiltininc -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include -idirafter /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include -resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build -Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp
getpwnam_r_invalid_user.cpp.tmp: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp:17: int main(): Assertion `res == 0 || res == ENOENT' failed.
/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.script: line 1: 1766331 Aborted                 /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp

--

********************
Testing:  0.. 10.. 20.. 30.. 40.. 50.
FAIL: SanitizerCommon-msan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp (3005 of 5236)
******************** TEST 'SanitizerCommon-msan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp' FAILED ********************
Exit Code: 134

Command Output (stderr):
--
/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang  --driver-mode=g++ -gline-tables-only -fsanitize=memory  -m64 -fno-function-sections -funwind-tables -nobuiltininc -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include -idirafter /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include -resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build -Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux  -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp &&  /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp # RUN: at line 2
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang --driver-mode=g++ -gline-tables-only -fsanitize=memory -m64 -fno-function-sections -funwind-tables -nobuiltininc -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include -idirafter /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include -resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build -Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp
getpwnam_r_invalid_user.cpp.tmp: /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp:17: int main(): Assertion `res == 0 || res == ENOENT' failed.
/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.script: line 1: 1773391 Aborted                 /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/msan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp

--

********************
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60..
FAIL: SanitizerCommon-lsan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp (3563 of 5236)
******************** TEST 'SanitizerCommon-lsan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp' FAILED ********************
Exit Code: 134

Command Output (stderr):
--
/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/bin/clang  --driver-mode=g++ -gline-tables-only -fsanitize=leak  -m64 -fno-function-sections -funwind-tables -nobuiltininc -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/include -idirafter /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/build_default/lib/clang/22/include -resource-dir=/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build -Wl,-rpath,/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/lib/linux  -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/lsan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp &&  /home/buildbots/llvm-external-buildbots/workers/ppc64le-sanitizer/sanitizer-ppc64le/build/compiler_rt_build/test/sanitizer_common/lsan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp # RUN: at line 2

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 17, 2025

LLVM Buildbot has detected a new failure on builder clang-armv7-global-isel running on linaro-clang-armv7-global-isel while building llvm at step 7 "ninja check 1".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/39/builds/7898

Here is the relevant piece of the build log for the reference
Step 7 (ninja check 1) failure: stage 1 checked (failure)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso-x32.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/tcwg-buildbot/worker/clang-armv7-global-isel/stage1/bin/llc < /home/tcwg-buildbot/worker/clang-armv7-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll -mtriple=i686-unknown-unknown -mattr=cmov | /home/tcwg-buildbot/worker/clang-armv7-global-isel/stage1/bin/FileCheck /home/tcwg-buildbot/worker/clang-armv7-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# executed command: /home/tcwg-buildbot/worker/clang-armv7-global-isel/stage1/bin/llc -mtriple=i686-unknown-unknown -mattr=cmov
# executed command: /home/tcwg-buildbot/worker/clang-armv7-global-isel/stage1/bin/FileCheck /home/tcwg-buildbot/worker/clang-armv7-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# .---command stderr------------
# | /home/tcwg-buildbot/worker/clang-armv7-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:83:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:75:15: note: scanning from here
# |  cmpw %si, %dx
# |               ^
# | <stdin>:76:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/tcwg-buildbot/worker/clang-armv7-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:173:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:167:17: note: scanning from here
# |  cmpl %esi, %edx
# |                 ^
# | <stdin>:168:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/tcwg-buildbot/worker/clang-armv7-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:219:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB11_2
# |             ^
# | <stdin>:214:17: note: scanning from here
# |  cmpl %edx, %ecx
# |                 ^
# | <stdin>:215:2: note: possible intended match here
# |  jne .LBB11_1
# |  ^
# | 
# | Input file: <stdin>
# | Check file: /home/tcwg-buildbot/worker/clang-armv7-global-isel/llvm/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# |             .
# |             .
# |             .
# |            70:  movl 8(%esp), %eax 
# |            71:  movzwl (%eax), %edx 
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 18, 2025

LLVM Buildbot has detected a new failure on builder clang-with-thin-lto-ubuntu running on as-worker-92 while building llvm at step 7 "test-stage1-compiler".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/127/builds/4747

Here is the relevant piece of the build log for the reference
Step 7 (test-stage1-compiler) failure: build (failure)
...
llvm-lit: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/bin/ld64.lld
llvm-lit: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/bin/wasm-ld
llvm-lit: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/utils/lit/tests/lit.cfg:111: warning: Setting a timeout per test not supported. Requires the Python psutil module but it could not be found. Try installing it via pip or via your operating system's package manager.
 Some tests will be skipped and the --timeout command line argument will not work.
llvm-lit: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld.lld: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/bin/ld.lld
llvm-lit: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using lld-link: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/bin/lld-link
llvm-lit: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/bin/ld64.lld
llvm-lit: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/bin/wasm-ld
-- Testing: 87367 tests, 72 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.
FAIL: LLVM :: CodeGen/X86/memcmp-pgso.ll (50467 of 87367)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/bin/llc < /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll -mtriple=x86_64-unknown-unknown | /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/bin/FileCheck /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# executed command: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/bin/llc -mtriple=x86_64-unknown-unknown
# executed command: /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/build/stage1/bin/FileCheck /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll --check-prefixes=X64,X64-SSE2
# .---command stderr------------
# | /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:75:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:66:15: note: scanning from here
# |  cmpw %cx, %ax
# |               ^
# | <stdin>:67:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:153:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:146:17: note: scanning from here
# |  cmpl %ecx, %eax
# |                 ^
# | <stdin>:147:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:247:13: error: X64-NEXT: expected string not found in input
# | ; X64-NEXT: jne .LBB15_2
# |             ^
# | <stdin>:242:17: note: scanning from here
# |  cmpq %rdx, %rcx
# |                 ^
# | <stdin>:243:2: note: possible intended match here
# |  jne .LBB15_1
# |  ^
# | /home/buildbot/as-worker-92/clang-with-thin-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso.ll:277:13: error: X64-NEXT: expected string not found in input

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 21, 2025

LLVM Buildbot has detected a new failure on builder clang-with-lto-ubuntu running on as-worker-91 while building llvm at step 7 "test-stage1-compiler".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/49/builds/2239

Here is the relevant piece of the build log for the reference
Step 7 (test-stage1-compiler) failure: build (failure)
...
llvm-lit: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/bin/ld64.lld
llvm-lit: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/bin/wasm-ld
llvm-lit: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/utils/lit/tests/lit.cfg:111: warning: Setting a timeout per test not supported. Requires the Python psutil module but it could not be found. Try installing it via pip or via your operating system's package manager.
 Some tests will be skipped and the --timeout command line argument will not work.
llvm-lit: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld.lld: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/bin/ld.lld
llvm-lit: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using lld-link: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/bin/lld-link
llvm-lit: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using ld64.lld: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/bin/ld64.lld
llvm-lit: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/utils/lit/lit/llvm/config.py:530: note: using wasm-ld: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/bin/wasm-ld
-- Testing: 87367 tests, 72 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.
FAIL: LLVM :: CodeGen/X86/memcmp-pgso-x32.ll (50466 of 87367)
******************** TEST 'LLVM :: CodeGen/X86/memcmp-pgso-x32.ll' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 2
/home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/bin/llc < /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll -mtriple=i686-unknown-unknown -mattr=cmov | /home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/bin/FileCheck /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# executed command: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/bin/llc -mtriple=i686-unknown-unknown -mattr=cmov
# executed command: /home/buildbot/as-worker-91/clang-with-lto-ubuntu/build/stage1/bin/FileCheck /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll --check-prefixes=X86,X86-NOSSE
# .---command stderr------------
# | /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:83:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB4_3
# |             ^
# | <stdin>:75:15: note: scanning from here
# |  cmpw %si, %dx
# |               ^
# | <stdin>:76:2: note: possible intended match here
# |  jne .LBB4_1
# |  ^
# | /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:173:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB9_3
# |             ^
# | <stdin>:167:17: note: scanning from here
# |  cmpl %esi, %edx
# |                 ^
# | <stdin>:168:2: note: possible intended match here
# |  jne .LBB9_1
# |  ^
# | /home/buildbot/as-worker-91/clang-with-lto-ubuntu/llvm-project/llvm/test/CodeGen/X86/memcmp-pgso-x32.ll:219:13: error: X86-NEXT: expected string not found in input
# | ; X86-NEXT: jne .LBB11_2
# |             ^
# | <stdin>:214:17: note: scanning from here
# |  cmpl %edx, %ecx
# |                 ^
# | <stdin>:215:2: note: possible intended match here
# |  jne .LBB11_1
# |  ^
# | 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants