Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TLI] Add basic support for fdim libcall #108702

Merged
merged 1 commit into from
Sep 20, 2024
Merged

Conversation

braw-lee
Copy link
Contributor

first PR to fix #108695

Signed-off-by: Kushal Pal <kushalpal109@gmail.com>
@llvmbot
Copy link
Collaborator

llvmbot commented Sep 14, 2024

@llvm/pr-subscribers-llvm-analysis

Author: None (braw-lee)

Changes

first PR to fix #108695


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

6 Files Affected:

  • (modified) llvm/include/llvm/Analysis/TargetLibraryInfo.def (+15)
  • (modified) llvm/lib/Analysis/TargetLibraryInfo.cpp (+2)
  • (modified) llvm/lib/Transforms/Utils/BuildLibCalls.cpp (+3)
  • (modified) llvm/test/Transforms/InferFunctionAttrs/annotate.ll (+10)
  • (modified) llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml (+16-4)
  • (modified) llvm/unittests/Analysis/TargetLibraryInfoTest.cpp (+3)
diff --git a/llvm/include/llvm/Analysis/TargetLibraryInfo.def b/llvm/include/llvm/Analysis/TargetLibraryInfo.def
index 5914324b286c05..a18952f038cc31 100644
--- a/llvm/include/llvm/Analysis/TargetLibraryInfo.def
+++ b/llvm/include/llvm/Analysis/TargetLibraryInfo.def
@@ -2067,6 +2067,21 @@ TLI_DEFINE_ENUM_INTERNAL(remquol)
 TLI_DEFINE_STRING_INTERNAL("remquol")
 TLI_DEFINE_SIG_INTERNAL(LDbl, LDbl, LDbl, Ptr)
 
+/// double fdim(double x, double y);
+TLI_DEFINE_ENUM_INTERNAL(fdim)
+TLI_DEFINE_STRING_INTERNAL("fdim")
+TLI_DEFINE_SIG_INTERNAL(Dbl, Dbl, Dbl)
+
+/// float fdimf(float x, float y);
+TLI_DEFINE_ENUM_INTERNAL(fdimf)
+TLI_DEFINE_STRING_INTERNAL("fdimf")
+TLI_DEFINE_SIG_INTERNAL(Flt, Flt, Flt)
+
+/// long double fdiml(long double x, long double y);
+TLI_DEFINE_ENUM_INTERNAL(fdiml)
+TLI_DEFINE_STRING_INTERNAL("fdiml")
+TLI_DEFINE_SIG_INTERNAL(LDbl, LDbl, LDbl)
+
 /// int remove(const char *path);
 TLI_DEFINE_ENUM_INTERNAL(remove)
 TLI_DEFINE_STRING_INTERNAL("remove")
diff --git a/llvm/lib/Analysis/TargetLibraryInfo.cpp b/llvm/lib/Analysis/TargetLibraryInfo.cpp
index 47413239f3c6cc..1785d77bca985c 100644
--- a/llvm/lib/Analysis/TargetLibraryInfo.cpp
+++ b/llvm/lib/Analysis/TargetLibraryInfo.cpp
@@ -306,6 +306,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
       TLI.setUnavailable(LibFunc_powf);
       TLI.setUnavailable(LibFunc_remainderf);
       TLI.setUnavailable(LibFunc_remquof);
+      TLI.setUnavailable(LibFunc_fdimf);
       TLI.setUnavailable(LibFunc_sinf);
       TLI.setUnavailable(LibFunc_sinhf);
       TLI.setUnavailable(LibFunc_sqrtf);
@@ -337,6 +338,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
     TLI.setUnavailable(LibFunc_powl);
     TLI.setUnavailable(LibFunc_remainderl);
     TLI.setUnavailable(LibFunc_remquol);
+    TLI.setUnavailable(LibFunc_fdiml);
     TLI.setUnavailable(LibFunc_sinl);
     TLI.setUnavailable(LibFunc_sinhl);
     TLI.setUnavailable(LibFunc_sqrtl);
diff --git a/llvm/lib/Transforms/Utils/BuildLibCalls.cpp b/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
index b0da19813f0a4b..abe0d8c3d2e999 100644
--- a/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
+++ b/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
@@ -1191,6 +1191,9 @@ bool llvm::inferNonMandatoryLibFuncAttrs(Function &F,
   case LibFunc_fabs:
   case LibFunc_fabsf:
   case LibFunc_fabsl:
+  case LibFunc_fdim:
+  case LibFunc_fdiml:
+  case LibFunc_fdimf:
   case LibFunc_ffs:
   case LibFunc_ffsl:
   case LibFunc_ffsll:
diff --git a/llvm/test/Transforms/InferFunctionAttrs/annotate.ll b/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
index bc0d7a509e1f5d..267a288345dc10 100644
--- a/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
+++ b/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
@@ -830,6 +830,16 @@ declare float @remquof(float, float, ptr)
 ; CHECK: declare x86_fp80 @remquol(x86_fp80, x86_fp80, ptr nocapture) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
 declare x86_fp80 @remquol(x86_fp80, x86_fp80, ptr)
 
+
+; CHECK: declare double @fdim(double, double) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare double @fdim(double, double)
+
+; CHECK: declare float @fdimf(float, float) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare float @fdimf(float, float)
+
+; CHECK: declare x86_fp80 @fdiml(x86_fp80, x86_fp80) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare x86_fp80 @fdiml(x86_fp80, x86_fp80)
+
 ; CHECK: declare noundef i32 @rename(ptr nocapture noundef readonly, ptr nocapture noundef readonly) [[NOFREE_NOUNWIND]]
 declare i32 @rename(ptr, ptr)
 
diff --git a/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml b/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
index 47aeb0ad8fdef9..767a962402b783 100644
--- a/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+++ b/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
@@ -34,7 +34,7 @@
 #
 # CHECK: << Total TLI yes SDK no:  18
 # CHECK: >> Total TLI no  SDK yes: 0
-# CHECK: == Total TLI yes SDK yes: 250
+# CHECK: == Total TLI yes SDK yes: 253
 #
 # WRONG_DETAIL: << TLI yes SDK no : '_ZdaPv' aka operator delete[](void*)
 # WRONG_DETAIL: >> TLI no  SDK yes: '_ZdaPvj' aka operator delete[](void*, unsigned int)
@@ -48,14 +48,14 @@
 # WRONG_DETAIL: << TLI yes SDK no : 'fminimum_numl'
 # WRONG_SUMMARY: << Total TLI yes SDK no:  19{{$}}
 # WRONG_SUMMARY: >> Total TLI no  SDK yes: 1{{$}}
-# WRONG_SUMMARY: == Total TLI yes SDK yes: 249
+# WRONG_SUMMARY: == Total TLI yes SDK yes: 252
 #
 ## The -COUNT suffix doesn't care if there are too many matches, so check
 ## the exact count first; the two directives should add up to that.
 ## Yes, this means additions to TLI will fail this test, but the argument
 ## to -COUNT can't be an expression.
-# AVAIL: TLI knows 501 symbols, 268 available
-# AVAIL-COUNT-268: {{^}} available
+# AVAIL: TLI knows 504 symbols, 271 available
+# AVAIL-COUNT-271: {{^}} available
 # AVAIL-NOT:       {{^}} available
 # UNAVAIL-COUNT-233: not available
 # UNAVAIL-NOT:       not available
@@ -814,6 +814,18 @@ DynamicSymbols:
     Type:            STT_FUNC
     Section:         .text
     Binding:         STB_GLOBAL
+  - Name:            fdim
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
+  - Name:            fdimf
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
+  - Name:            fdiml
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
   - Name:            rewind
     Type:            STT_FUNC
     Section:         .text
diff --git a/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp b/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
index c081c44ed35d00..ed6a91ce611acf 100644
--- a/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
+++ b/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
@@ -317,6 +317,9 @@ TEST_F(TargetLibraryInfoTest, ValidProto) {
       "declare double @remquo(double, double, ptr)\n"
       "declare float @remquof(float, float, ptr)\n"
       "declare x86_fp80 @remquol(x86_fp80, x86_fp80, ptr)\n"
+      "declare double @fdim(double, double)\n"
+      "declare float @fdimf(float, float)\n"
+      "declare x86_fp80 @fdiml(x86_fp80, x86_fp80)\n"
       "declare i32 @rename(i8*, i8*)\n"
       "declare void @rewind(%struct*)\n"
       "declare double @rint(double)\n"

@llvmbot
Copy link
Collaborator

llvmbot commented Sep 14, 2024

@llvm/pr-subscribers-llvm-transforms

Author: None (braw-lee)

Changes

first PR to fix #108695


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

6 Files Affected:

  • (modified) llvm/include/llvm/Analysis/TargetLibraryInfo.def (+15)
  • (modified) llvm/lib/Analysis/TargetLibraryInfo.cpp (+2)
  • (modified) llvm/lib/Transforms/Utils/BuildLibCalls.cpp (+3)
  • (modified) llvm/test/Transforms/InferFunctionAttrs/annotate.ll (+10)
  • (modified) llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml (+16-4)
  • (modified) llvm/unittests/Analysis/TargetLibraryInfoTest.cpp (+3)
diff --git a/llvm/include/llvm/Analysis/TargetLibraryInfo.def b/llvm/include/llvm/Analysis/TargetLibraryInfo.def
index 5914324b286c05..a18952f038cc31 100644
--- a/llvm/include/llvm/Analysis/TargetLibraryInfo.def
+++ b/llvm/include/llvm/Analysis/TargetLibraryInfo.def
@@ -2067,6 +2067,21 @@ TLI_DEFINE_ENUM_INTERNAL(remquol)
 TLI_DEFINE_STRING_INTERNAL("remquol")
 TLI_DEFINE_SIG_INTERNAL(LDbl, LDbl, LDbl, Ptr)
 
+/// double fdim(double x, double y);
+TLI_DEFINE_ENUM_INTERNAL(fdim)
+TLI_DEFINE_STRING_INTERNAL("fdim")
+TLI_DEFINE_SIG_INTERNAL(Dbl, Dbl, Dbl)
+
+/// float fdimf(float x, float y);
+TLI_DEFINE_ENUM_INTERNAL(fdimf)
+TLI_DEFINE_STRING_INTERNAL("fdimf")
+TLI_DEFINE_SIG_INTERNAL(Flt, Flt, Flt)
+
+/// long double fdiml(long double x, long double y);
+TLI_DEFINE_ENUM_INTERNAL(fdiml)
+TLI_DEFINE_STRING_INTERNAL("fdiml")
+TLI_DEFINE_SIG_INTERNAL(LDbl, LDbl, LDbl)
+
 /// int remove(const char *path);
 TLI_DEFINE_ENUM_INTERNAL(remove)
 TLI_DEFINE_STRING_INTERNAL("remove")
diff --git a/llvm/lib/Analysis/TargetLibraryInfo.cpp b/llvm/lib/Analysis/TargetLibraryInfo.cpp
index 47413239f3c6cc..1785d77bca985c 100644
--- a/llvm/lib/Analysis/TargetLibraryInfo.cpp
+++ b/llvm/lib/Analysis/TargetLibraryInfo.cpp
@@ -306,6 +306,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
       TLI.setUnavailable(LibFunc_powf);
       TLI.setUnavailable(LibFunc_remainderf);
       TLI.setUnavailable(LibFunc_remquof);
+      TLI.setUnavailable(LibFunc_fdimf);
       TLI.setUnavailable(LibFunc_sinf);
       TLI.setUnavailable(LibFunc_sinhf);
       TLI.setUnavailable(LibFunc_sqrtf);
@@ -337,6 +338,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
     TLI.setUnavailable(LibFunc_powl);
     TLI.setUnavailable(LibFunc_remainderl);
     TLI.setUnavailable(LibFunc_remquol);
+    TLI.setUnavailable(LibFunc_fdiml);
     TLI.setUnavailable(LibFunc_sinl);
     TLI.setUnavailable(LibFunc_sinhl);
     TLI.setUnavailable(LibFunc_sqrtl);
diff --git a/llvm/lib/Transforms/Utils/BuildLibCalls.cpp b/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
index b0da19813f0a4b..abe0d8c3d2e999 100644
--- a/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
+++ b/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
@@ -1191,6 +1191,9 @@ bool llvm::inferNonMandatoryLibFuncAttrs(Function &F,
   case LibFunc_fabs:
   case LibFunc_fabsf:
   case LibFunc_fabsl:
+  case LibFunc_fdim:
+  case LibFunc_fdiml:
+  case LibFunc_fdimf:
   case LibFunc_ffs:
   case LibFunc_ffsl:
   case LibFunc_ffsll:
diff --git a/llvm/test/Transforms/InferFunctionAttrs/annotate.ll b/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
index bc0d7a509e1f5d..267a288345dc10 100644
--- a/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
+++ b/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
@@ -830,6 +830,16 @@ declare float @remquof(float, float, ptr)
 ; CHECK: declare x86_fp80 @remquol(x86_fp80, x86_fp80, ptr nocapture) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
 declare x86_fp80 @remquol(x86_fp80, x86_fp80, ptr)
 
+
+; CHECK: declare double @fdim(double, double) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare double @fdim(double, double)
+
+; CHECK: declare float @fdimf(float, float) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare float @fdimf(float, float)
+
+; CHECK: declare x86_fp80 @fdiml(x86_fp80, x86_fp80) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare x86_fp80 @fdiml(x86_fp80, x86_fp80)
+
 ; CHECK: declare noundef i32 @rename(ptr nocapture noundef readonly, ptr nocapture noundef readonly) [[NOFREE_NOUNWIND]]
 declare i32 @rename(ptr, ptr)
 
diff --git a/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml b/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
index 47aeb0ad8fdef9..767a962402b783 100644
--- a/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+++ b/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
@@ -34,7 +34,7 @@
 #
 # CHECK: << Total TLI yes SDK no:  18
 # CHECK: >> Total TLI no  SDK yes: 0
-# CHECK: == Total TLI yes SDK yes: 250
+# CHECK: == Total TLI yes SDK yes: 253
 #
 # WRONG_DETAIL: << TLI yes SDK no : '_ZdaPv' aka operator delete[](void*)
 # WRONG_DETAIL: >> TLI no  SDK yes: '_ZdaPvj' aka operator delete[](void*, unsigned int)
@@ -48,14 +48,14 @@
 # WRONG_DETAIL: << TLI yes SDK no : 'fminimum_numl'
 # WRONG_SUMMARY: << Total TLI yes SDK no:  19{{$}}
 # WRONG_SUMMARY: >> Total TLI no  SDK yes: 1{{$}}
-# WRONG_SUMMARY: == Total TLI yes SDK yes: 249
+# WRONG_SUMMARY: == Total TLI yes SDK yes: 252
 #
 ## The -COUNT suffix doesn't care if there are too many matches, so check
 ## the exact count first; the two directives should add up to that.
 ## Yes, this means additions to TLI will fail this test, but the argument
 ## to -COUNT can't be an expression.
-# AVAIL: TLI knows 501 symbols, 268 available
-# AVAIL-COUNT-268: {{^}} available
+# AVAIL: TLI knows 504 symbols, 271 available
+# AVAIL-COUNT-271: {{^}} available
 # AVAIL-NOT:       {{^}} available
 # UNAVAIL-COUNT-233: not available
 # UNAVAIL-NOT:       not available
@@ -814,6 +814,18 @@ DynamicSymbols:
     Type:            STT_FUNC
     Section:         .text
     Binding:         STB_GLOBAL
+  - Name:            fdim
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
+  - Name:            fdimf
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
+  - Name:            fdiml
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
   - Name:            rewind
     Type:            STT_FUNC
     Section:         .text
diff --git a/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp b/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
index c081c44ed35d00..ed6a91ce611acf 100644
--- a/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
+++ b/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
@@ -317,6 +317,9 @@ TEST_F(TargetLibraryInfoTest, ValidProto) {
       "declare double @remquo(double, double, ptr)\n"
       "declare float @remquof(float, float, ptr)\n"
       "declare x86_fp80 @remquol(x86_fp80, x86_fp80, ptr)\n"
+      "declare double @fdim(double, double)\n"
+      "declare float @fdimf(float, float)\n"
+      "declare x86_fp80 @fdiml(x86_fp80, x86_fp80)\n"
       "declare i32 @rename(i8*, i8*)\n"
       "declare void @rewind(%struct*)\n"
       "declare double @rint(double)\n"

@dtcxzyw dtcxzyw requested a review from arsenm September 14, 2024 14:19
@braw-lee
Copy link
Contributor Author

hi @dtcxzyw
i am following your PRs for this issue #99497
i annotated the testcases manually
there aren't any scripts/commands that i should be using instead, right?

Copy link
Member

@dtcxzyw dtcxzyw left a comment

Choose a reason for hiding this comment

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

LG

@dtcxzyw
Copy link
Member

dtcxzyw commented Sep 14, 2024

hi @dtcxzyw i am following your PRs for this issue #99497 i annotated the testcases manually there aren't any scripts/commands that i should be using instead, right?

Yeah. Tests without header comment ; NOTE: Assertions have been autogenerated by XXX are maintained manually.

@arsenm arsenm added the floating-point Floating-point math label Sep 15, 2024
@@ -337,6 +338,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
TLI.setUnavailable(LibFunc_powl);
TLI.setUnavailable(LibFunc_remainderl);
TLI.setUnavailable(LibFunc_remquol);
TLI.setUnavailable(LibFunc_fdiml);
Copy link
Contributor

Choose a reason for hiding this comment

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

Don't believe this is tested

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this line marks the long double library function unavailable for Win32
sry but i am not sure what you want to me to do here

Copy link
Contributor

Choose a reason for hiding this comment

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

Add a test that shows fdiml is not recognized as a libcall on windows

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i added it because there's a comment above stating long double functions are not supported by Win32
are there any previous such tests that i can refer to?

Copy link
Contributor

Choose a reason for hiding this comment

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

There seem to be 3 ways it's done. The most direct way has an example in TargetLibraryInfoTest.cpp in TLITestAarch64.

There's also an underutilized looking direct test in llvm/test/tools/llvm-tli-checker, which currently only covers ps4.

The indirect way most TLI tests do is to add a negative instcombine test for some transform, e.g. test/Transforms/InstCombine/memcmp-1.ll

Copy link
Contributor Author

Choose a reason for hiding this comment

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

tried to add a test but its failing
mingw32 is generating fdimf

i feel like this was not the correct way to test

; CHECK-LABEL: define fp128 @fdim_fp128(
; MINGW32-NOT: fp128 @fdiml
;
%1 = call fp128 @fdiml(fp128 %x, fp128 %y)
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't understand this test; what positive transform would happen? This is an ordinary, unoptimizable call?

Copy link
Contributor Author

@braw-lee braw-lee Sep 19, 2024

Choose a reason for hiding this comment

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

yh, unoptimizable call
tbh i thought windows will not generate fdiml and that would be enough
i will try the other 2 ways, but i think i will need some help, sry, i am new to the codebase

Copy link
Contributor

Choose a reason for hiding this comment

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

In your constant folding patch, this wouldn't constant fold on windows. so you could test it there I suppose

Copy link
Contributor Author

Choose a reason for hiding this comment

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

alright, I will just remove the 2nd commit from this PR

Copy link
Contributor

@arsenm arsenm left a comment

Choose a reason for hiding this comment

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

LGTM. We really ought to round out the llvm-tli-checker tests for more platforms, but that's a separate change. Please make sure to add a negative constant folding test in the other PR

@arsenm arsenm merged commit 173841c into llvm:main Sep 20, 2024
13 of 15 checks passed
@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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/5432

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/build/bin/yaml2obj /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/build/bin/yaml2obj /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx64-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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/7501

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/yaml2obj /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/yaml2obj /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /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/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /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/tools/llvm-tli-checker/ps4-tli-check.yaml
�[1m/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: �[0m�[0;1;31merror: �[0m�[1mCHECK: expected string not found in input
�[0m# CHECK: == Total TLI yes SDK yes: 253
�[0;1;32m         ^
�[0m�[1m<stdin>:25:27: �[0m�[0;1;30mnote: �[0m�[1mscanning from here
�[0m>> Total TLI no SDK yes: 0
�[0;1;32m                          ^
�[0m�[1m<stdin>:26:1: �[0m�[0;1;30mnote: �[0m�[1mpossible intended match here
�[0m== Total TLI yes SDK yes: 256
�[0;1;32m^
�[0m
Input file: <stdin>
Check file: /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
�[1m�[0m�[0;1;30m            1: �[0m�[1m�[0;1;46mTLI knows 507 symbols, 274 available for 'x86_64-scei-ps4' �[0m
�[0;1;30m            2: �[0m�[1m�[0;1;46m �[0m
�[0;1;30m            3: �[0m�[1m�[0;1;46mLooking for symbols in '/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1' �[0m
�[0;1;30m            4: �[0m�[1m�[0;1;46mFound 256 global function symbols in '/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1' �[0m
�[0;1;30m            5: �[0m�[1m�[0;1;46mFound a grand total of 256 library symbols �[0m
�[0;1;30m            6: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_Znam12__hot_cold_t' aka operator new[](unsigned long, __hot_cold_t) �[0m
�[0;1;30m            7: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnamRKSt9nothrow_t12__hot_cold_t' aka operator new[](unsigned long, std::nothrow_t const&, __hot_cold_t) �[0m
�[0;1;30m            8: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnamSt11align_val_t12__hot_cold_t' aka operator new[](unsigned long, std::align_val_t, __hot_cold_t) �[0m
�[0;1;30m            9: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnamSt11align_val_tRKSt9nothrow_t12__hot_cold_t' aka operator new[](unsigned long, std::align_val_t, std::nothrow_t const&, __hot_cold_t) �[0m
�[0;1;30m           10: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_Znwm12__hot_cold_t' aka operator new(unsigned long, __hot_cold_t) �[0m
�[0;1;30m           11: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnwmRKSt9nothrow_t12__hot_cold_t' aka operator new(unsigned long, std::nothrow_t const&, __hot_cold_t) �[0m
�[0;1;30m           12: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnwmSt11align_val_t12__hot_cold_t' aka operator new(unsigned long, std::align_val_t, __hot_cold_t) �[0m
�[0;1;30m           13: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnwmSt11align_val_tRKSt9nothrow_t12__hot_cold_t' aka operator new(unsigned long, std::align_val_t, std::nothrow_t const&, __hot_cold_t) �[0m
�[0;1;30m           14: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new' �[0m
�[0;1;30m           15: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new_hot_cold' �[0m
�[0;1;30m           16: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new_aligned' �[0m
�[0;1;30m           17: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new_aligned_hot_cold' �[0m
�[0;1;30m           18: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fmaximum_num' �[0m
�[0;1;30m           19: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fmaximum_numf' �[0m
�[0;1;30m           20: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fmaximum_numl' �[0m
�[0;1;30m           21: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fminimum_num' �[0m
�[0;1;30m           22: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fminimum_numf' �[0m
�[0;1;30m           23: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fminimum_numl' �[0m
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

LLVM Buildbot has detected a new failure on builder openmp-offload-sles-build-only running on rocm-worker-hw-04-sles while building llvm at step 8 "Add check check-llvm".

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

Here is the relevant piece of the build log for the reference
Step 8 (Add check check-llvm) failure: test (failure)
******************** TEST 'LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.build/bin/yaml2obj /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/botworker/bbot/builds/openmp-offload-sles-build/llvm.build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.build/bin/yaml2obj /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/botworker/bbot/builds/openmp-offload-sles-build/llvm.build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.build/bin/FileCheck /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.build/bin/FileCheck /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
/home/botworker/bbot/builds/openmp-offload-sles-build/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /home/botworker/bbot/builds/openmp-offload-sles-build/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

LLVM Buildbot has detected a new failure on builder clang-ve-ninja running on hpce-ve-main while building llvm at step 4 "annotate".

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

Here is the relevant piece of the build log for the reference
Step 4 (annotate) failure: 'python ../llvm-zorg/zorg/buildbot/builders/annotated/ve-linux.py ...' (failure)
...
[656/657] Running the LLVM regression tests
Unknown option: -C
usage: git [--version] [--help] [-c name=value]
           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
           [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
           <command> [<args>]
An error occurred retrieving the git revision: Command '['git', '-C', '/scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm', 'rev-parse', 'HEAD']' returned non-zero exit status 129.
-- Testing: 55362 tests, 48 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90
FAIL: LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml (52929 of 55362)
******************** TEST 'LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/bin/yaml2obj /scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/bin/yaml2obj /scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/bin/FileCheck /scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/bin/FileCheck /scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
Step 8 (check-llvm) failure: check-llvm (failure)
...
[656/657] Running the LLVM regression tests
Unknown option: -C
usage: git [--version] [--help] [-c name=value]
           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
           [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
           <command> [<args>]
An error occurred retrieving the git revision: Command '['git', '-C', '/scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm', 'rev-parse', 'HEAD']' returned non-zero exit status 129.
-- Testing: 55362 tests, 48 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90
FAIL: LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml (52929 of 55362)
******************** TEST 'LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/bin/yaml2obj /scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/bin/yaml2obj /scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/bin/FileCheck /scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /scratch/buildbot/bothome/clang-ve-ninja/build/build_llvm/bin/FileCheck /scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /scratch/buildbot/bothome/clang-ve-ninja/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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/5430

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/bin/yaml2obj /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/bin/yaml2obj /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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/4914

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /buildbot/worker/arc-folder/build/bin/yaml2obj /buildbot/worker/arc-folder/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/buildbot/worker/arc-folder/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /buildbot/worker/arc-folder/build/bin/yaml2obj /buildbot/worker/arc-folder/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/buildbot/worker/arc-folder/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /buildbot/worker/arc-folder/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /buildbot/worker/arc-folder/build/bin/FileCheck /buildbot/worker/arc-folder/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ /buildbot/worker/arc-folder/build/bin/FileCheck /buildbot/worker/arc-folder/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /buildbot/worker/arc-folder/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
/buildbot/worker/arc-folder/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /buildbot/worker/arc-folder/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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

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

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/build/bin/yaml2obj /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/build/bin/yaml2obj /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/build/bin/FileCheck /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/build/bin/FileCheck /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
�[1m/home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: �[0m�[0;1;31merror: �[0m�[1mCHECK: expected string not found in input
�[0m# CHECK: == Total TLI yes SDK yes: 253
�[0;1;32m         ^
�[0m�[1m<stdin>:25:27: �[0m�[0;1;30mnote: �[0m�[1mscanning from here
�[0m>> Total TLI no SDK yes: 0
�[0;1;32m                          ^
�[0m�[1m<stdin>:26:1: �[0m�[0;1;30mnote: �[0m�[1mpossible intended match here
�[0m== Total TLI yes SDK yes: 256
�[0;1;32m^
�[0m
Input file: <stdin>
Check file: /home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
�[1m�[0m�[0;1;30m            1: �[0m�[1m�[0;1;46mTLI knows 507 symbols, 274 available for 'x86_64-scei-ps4' �[0m
�[0;1;30m            2: �[0m�[1m�[0;1;46m �[0m
�[0;1;30m            3: �[0m�[1m�[0;1;46mLooking for symbols in '/home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1' �[0m
�[0;1;30m            4: �[0m�[1m�[0;1;46mFound 256 global function symbols in '/home/buildbot/buildbot-root/llvm-clang-x86_64-gcc-ubuntu/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1' �[0m
�[0;1;30m            5: �[0m�[1m�[0;1;46mFound a grand total of 256 library symbols �[0m
�[0;1;30m            6: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_Znam12__hot_cold_t' aka operator new[](unsigned long, __hot_cold_t) �[0m
�[0;1;30m            7: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnamRKSt9nothrow_t12__hot_cold_t' aka operator new[](unsigned long, std::nothrow_t const&, __hot_cold_t) �[0m
�[0;1;30m            8: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnamSt11align_val_t12__hot_cold_t' aka operator new[](unsigned long, std::align_val_t, __hot_cold_t) �[0m
�[0;1;30m            9: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnamSt11align_val_tRKSt9nothrow_t12__hot_cold_t' aka operator new[](unsigned long, std::align_val_t, std::nothrow_t const&, __hot_cold_t) �[0m
�[0;1;30m           10: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_Znwm12__hot_cold_t' aka operator new(unsigned long, __hot_cold_t) �[0m
�[0;1;30m           11: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnwmRKSt9nothrow_t12__hot_cold_t' aka operator new(unsigned long, std::nothrow_t const&, __hot_cold_t) �[0m
�[0;1;30m           12: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnwmSt11align_val_t12__hot_cold_t' aka operator new(unsigned long, std::align_val_t, __hot_cold_t) �[0m
�[0;1;30m           13: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnwmSt11align_val_tRKSt9nothrow_t12__hot_cold_t' aka operator new(unsigned long, std::align_val_t, std::nothrow_t const&, __hot_cold_t) �[0m
�[0;1;30m           14: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new' �[0m
�[0;1;30m           15: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new_hot_cold' �[0m
�[0;1;30m           16: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new_aligned' �[0m
�[0;1;30m           17: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new_aligned_hot_cold' �[0m
�[0;1;30m           18: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fmaximum_num' �[0m
�[0;1;30m           19: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fmaximum_numf' �[0m
�[0;1;30m           20: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fmaximum_numl' �[0m
�[0;1;30m           21: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fminimum_num' �[0m
�[0;1;30m           22: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fminimum_numf' �[0m
�[0;1;30m           23: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fminimum_numl' �[0m
...

@braw-lee
Copy link
Contributor Author

@arsenm
43c9203
looks like this commit incremented the total TLI in ps4-tli-check.yaml to 253, so my commit of fdim should increment to 256
should this be handled in a new PR?

@arsenm
Copy link
Contributor

arsenm commented Sep 20, 2024

@arsenm 43c9203 looks like this commit incremented the total TLI in ps4-tli-check.yaml to 253, so my commit of fdim should increment to 256 should this be handled in a new PR?

Should push a fix asap, not sure how this failed. It passed the precheck

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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

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

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 4
z:\b\llvm-clang-x86_64-sie-win\build\bin\yaml2obj.exe Z:\b\llvm-clang-x86_64-sie-win\llvm-project\llvm\test\tools\llvm-tli-checker\ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=Z:\b\llvm-clang-x86_64-sie-win\build\test\tools\llvm-tli-checker\Output\ps4-tli-check.yaml.tmp1
# executed command: 'z:\b\llvm-clang-x86_64-sie-win\build\bin\yaml2obj.exe' 'Z:\b\llvm-clang-x86_64-sie-win\llvm-project\llvm\test\tools\llvm-tli-checker\ps4-tli-check.yaml' -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv '-o=Z:\b\llvm-clang-x86_64-sie-win\build\test\tools\llvm-tli-checker\Output\ps4-tli-check.yaml.tmp1'
# RUN: at line 5
llvm-tli-checker --triple=x86_64-scei-ps4 Z:\b\llvm-clang-x86_64-sie-win\build\test\tools\llvm-tli-checker\Output\ps4-tli-check.yaml.tmp1 | z:\b\llvm-clang-x86_64-sie-win\build\bin\filecheck.exe Z:\b\llvm-clang-x86_64-sie-win\llvm-project\llvm\test\tools\llvm-tli-checker\ps4-tli-check.yaml
# executed command: llvm-tli-checker --triple=x86_64-scei-ps4 'Z:\b\llvm-clang-x86_64-sie-win\build\test\tools\llvm-tli-checker\Output\ps4-tli-check.yaml.tmp1'
# executed command: 'z:\b\llvm-clang-x86_64-sie-win\build\bin\filecheck.exe' 'Z:\b\llvm-clang-x86_64-sie-win\llvm-project\llvm\test\tools\llvm-tli-checker\ps4-tli-check.yaml'
# .---command stderr------------
# | �[1mZ:\b\llvm-clang-x86_64-sie-win\llvm-project\llvm\test\tools\llvm-tli-checker\ps4-tli-check.yaml:37:10: �[0m�[0;1;31merror: �[0m�[1mCHECK: expected string not found in input
�[0m# | �[1m�[0m# CHECK: == Total TLI yes SDK yes: 253
# | �[0;1;32m         ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:25:27: �[0m�[0;1;30mnote: �[0m�[1mscanning from here
�[0m# | �[1m�[0m>> Total TLI no SDK yes: 0
# | �[0;1;32m                          ^
�[0m# | �[0;1;32m�[0m�[1m<stdin>:26:1: �[0m�[0;1;30mnote: �[0m�[1mpossible intended match here
�[0m# | �[1m�[0m== Total TLI yes SDK yes: 256
# | �[0;1;32m^
�[0m# | �[0;1;32m�[0m
# | Input file: <stdin>
# | Check file: Z:\b\llvm-clang-x86_64-sie-win\llvm-project\llvm\test\tools\llvm-tli-checker\ps4-tli-check.yaml
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# | �[1m�[0m�[0;1;30m            1: �[0m�[1m�[0;1;46mTLI knows 507 symbols, 274 available for 'x86_64-scei-ps4' �[0m
# | �[0;1;30m            2: �[0m�[1m�[0;1;46m �[0m
# | �[0;1;30m            3: �[0m�[1m�[0;1;46mLooking for symbols in 'Z:\b\llvm-clang-x86_64-sie-win\build\test\tools\llvm-tli-checker\Output\ps4-tli-check.yaml.tmp1' �[0m
# | �[0;1;30m            4: �[0m�[1m�[0;1;46mFound 256 global function symbols in 'Z:\b\llvm-clang-x86_64-sie-win\build\test\tools\llvm-tli-checker\Output\ps4-tli-check.yaml.tmp1' �[0m
# | �[0;1;30m            5: �[0m�[1m�[0;1;46mFound a grand total of 256 library symbols �[0m
# | �[0;1;30m            6: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_Znam12__hot_cold_t' aka operator new[](unsigned long, __hot_cold_t) �[0m
# | �[0;1;30m            7: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnamRKSt9nothrow_t12__hot_cold_t' aka operator new[](unsigned long, std::nothrow_t const&, __hot_cold_t) �[0m
# | �[0;1;30m            8: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnamSt11align_val_t12__hot_cold_t' aka operator new[](unsigned long, std::align_val_t, __hot_cold_t) �[0m
# | �[0;1;30m            9: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnamSt11align_val_tRKSt9nothrow_t12__hot_cold_t' aka operator new[](unsigned long, std::align_val_t, std::nothrow_t const&, __hot_cold_t) �[0m
# | �[0;1;30m           10: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_Znwm12__hot_cold_t' aka operator new(unsigned long, __hot_cold_t) �[0m
# | �[0;1;30m           11: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnwmRKSt9nothrow_t12__hot_cold_t' aka operator new(unsigned long, std::nothrow_t const&, __hot_cold_t) �[0m
# | �[0;1;30m           12: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnwmSt11align_val_t12__hot_cold_t' aka operator new(unsigned long, std::align_val_t, __hot_cold_t) �[0m
# | �[0;1;30m           13: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '_ZnwmSt11align_val_tRKSt9nothrow_t12__hot_cold_t' aka operator new(unsigned long, std::align_val_t, std::nothrow_t const&, __hot_cold_t) �[0m
# | �[0;1;30m           14: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new' �[0m
# | �[0;1;30m           15: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new_hot_cold' �[0m
# | �[0;1;30m           16: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new_aligned' �[0m
# | �[0;1;30m           17: �[0m�[1m�[0;1;46m<< TLI yes SDK no : '__size_returning_new_aligned_hot_cold' �[0m
# | �[0;1;30m           18: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fmaximum_num' �[0m
# | �[0;1;30m           19: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fmaximum_numf' �[0m
# | �[0;1;30m           20: �[0m�[1m�[0;1;46m<< TLI yes SDK no : 'fmaximum_numl' �[0m
...

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

LLVM Buildbot has detected a new failure on builder ml-opt-devrel-x86-64 running on ml-opt-devrel-x86-64-b1 while building llvm at step 6 "test-build-unified-tree-check-all".

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

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /b/ml-opt-devrel-x86-64-b1/build/bin/yaml2obj /b/ml-opt-devrel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/ml-opt-devrel-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/ml-opt-devrel-x86-64-b1/build/bin/yaml2obj /b/ml-opt-devrel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/ml-opt-devrel-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /b/ml-opt-devrel-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /b/ml-opt-devrel-x86-64-b1/build/bin/FileCheck /b/ml-opt-devrel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ /b/ml-opt-devrel-x86-64-b1/build/bin/FileCheck /b/ml-opt-devrel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /b/ml-opt-devrel-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
/b/ml-opt-devrel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /b/ml-opt-devrel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

LLVM Buildbot has detected a new failure on builder ml-opt-rel-x86-64 running on ml-opt-rel-x86-64-b1 while building llvm at step 6 "test-build-unified-tree-check-all".

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

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /b/ml-opt-rel-x86-64-b1/build/bin/yaml2obj /b/ml-opt-rel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/ml-opt-rel-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/ml-opt-rel-x86-64-b1/build/bin/yaml2obj /b/ml-opt-rel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/ml-opt-rel-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /b/ml-opt-rel-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /b/ml-opt-rel-x86-64-b1/build/bin/FileCheck /b/ml-opt-rel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /b/ml-opt-rel-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/ml-opt-rel-x86-64-b1/build/bin/FileCheck /b/ml-opt-rel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/b/ml-opt-rel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /b/ml-opt-rel-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@arsenm
Copy link
Contributor

arsenm commented Sep 20, 2024

Fixed by 2c6e5ef

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

LLVM Buildbot has detected a new failure on builder openmp-offload-libc-amdgpu-runtime running on omp-vega20-1 while building llvm at step 8 "Add check check-llvm".

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

Here is the relevant piece of the build log for the reference
Step 8 (Add check check-llvm) failure: test (failure)
******************** TEST 'LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.build/bin/yaml2obj /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.build/bin/yaml2obj /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.build/bin/FileCheck /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.build/bin/FileCheck /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /home/ompworker/bbot/openmp-offload-libc-amdgpu-runtime/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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/5321

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)
...
[1319/1324] Building CXX object unittests/Transforms/Scalar/CMakeFiles/ScalarTests.dir/LoopPassManagerTest.cpp.o
clang++: warning: optimization flag '-ffat-lto-objects' is not supported [-Wignored-optimization-argument]
[1320/1324] Linking CXX executable unittests/Transforms/Scalar/ScalarTests
[1320/1324] Running the LLVM regression tests
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:506: note: using ld.lld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/ld.lld
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:506: note: using lld-link: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/lld-link
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:506: note: using ld64.lld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/ld64.lld
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:506: note: using wasm-ld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/wasm-ld
-- Testing: 55724 tests, 60 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90
FAIL: LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml (52897 of 55724)
******************** TEST 'LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/yaml2obj /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/yaml2obj /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/FileCheck /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/FileCheck /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
Step 7 (check) failure: check (failure)
...
[1319/1324] Building CXX object unittests/Transforms/Scalar/CMakeFiles/ScalarTests.dir/LoopPassManagerTest.cpp.o
clang++: warning: optimization flag '-ffat-lto-objects' is not supported [-Wignored-optimization-argument]
[1320/1324] Linking CXX executable unittests/Transforms/Scalar/ScalarTests
[1320/1324] Running the LLVM regression tests
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:506: note: using ld.lld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/ld.lld
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:506: note: using lld-link: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/lld-link
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:506: note: using ld64.lld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/ld64.lld
llvm-lit: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/utils/lit/lit/llvm/config.py:506: note: using wasm-ld: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/wasm-ld
-- Testing: 55724 tests, 60 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90
FAIL: LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml (52897 of 55724)
******************** TEST 'LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/yaml2obj /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/yaml2obj /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/FileCheck /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /var/lib/buildbot/fuchsia-x86_64-linux/build/llvm-build-m69s3a6f/bin/FileCheck /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /var/lib/buildbot/fuchsia-x86_64-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 

@braw-lee
Copy link
Contributor Author

Fixed by 2c6e5ef

thank you!

@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

LLVM Buildbot has detected a new failure on builder ml-opt-dev-x86-64 running on ml-opt-dev-x86-64-b2 while building llvm at step 6 "test-build-unified-tree-check-all".

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

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /b/ml-opt-dev-x86-64-b1/build/bin/yaml2obj /b/ml-opt-dev-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/ml-opt-dev-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/ml-opt-dev-x86-64-b1/build/bin/yaml2obj /b/ml-opt-dev-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/ml-opt-dev-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /b/ml-opt-dev-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /b/ml-opt-dev-x86-64-b1/build/bin/FileCheck /b/ml-opt-dev-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /b/ml-opt-dev-x86-64-b1/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/ml-opt-dev-x86-64-b1/build/bin/FileCheck /b/ml-opt-dev-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/b/ml-opt-dev-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /b/ml-opt-dev-x86-64-b1/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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 6 "test-build-unified-tree-check-all".

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

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/bin/yaml2obj /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/bin/yaml2obj /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /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/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /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/tools/llvm-tli-checker/ps4-tli-check.yaml
/home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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

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

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/bin/yaml2obj /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/bin/yaml2obj /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/bin/FileCheck /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/bin/FileCheck /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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/3946

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/bin/yaml2obj /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/bin/yaml2obj /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/bin/FileCheck /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ /vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/bin/FileCheck /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /vol/worker/clang-debian-cpp20/clang-debian-cpp20/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
/vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /vol/worker/clang-debian-cpp20/clang-debian-cpp20/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

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/3544

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage1/bin/yaml2obj /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage1/bin/yaml2obj /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /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/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /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/tools/llvm-tli-checker/ps4-tli-check.yaml
/home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************

Step 13 (test-build-stage2-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage2/bin/yaml2obj /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage2/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage2/bin/yaml2obj /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage2/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage2/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /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/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/build/stage2/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /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/tools/llvm-tli-checker/ps4-tli-check.yaml
/home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /home/buildbots/llvm-external-buildbots/workers/ppc64le-lld-multistage-test/ppc64le-lld-multistage-test/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 20, 2024

LLVM Buildbot has detected a new failure on builder premerge-monolithic-linux running on premerge-linux-1 while building llvm at step 7 "test-build-unified-tree-check-all".

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

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 :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /build/buildbot/premerge-monolithic-linux/build/bin/yaml2obj /build/buildbot/premerge-monolithic-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/build/buildbot/premerge-monolithic-linux/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /build/buildbot/premerge-monolithic-linux/build/bin/yaml2obj /build/buildbot/premerge-monolithic-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/build/buildbot/premerge-monolithic-linux/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /build/buildbot/premerge-monolithic-linux/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /build/buildbot/premerge-monolithic-linux/build/bin/FileCheck /build/buildbot/premerge-monolithic-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ /build/buildbot/premerge-monolithic-linux/build/bin/FileCheck /build/buildbot/premerge-monolithic-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /build/buildbot/premerge-monolithic-linux/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
/build/buildbot/premerge-monolithic-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml:37:10: error: CHECK: expected string not found in input
# CHECK: == Total TLI yes SDK yes: 253
         ^
<stdin>:25:27: note: scanning from here
>> Total TLI no SDK yes: 0
                          ^
<stdin>:26:1: note: possible intended match here
== Total TLI yes SDK yes: 256
^

Input file: <stdin>
Check file: /build/buildbot/premerge-monolithic-linux/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           20: << TLI yes SDK no : 'fmaximum_numl' 
           21: << TLI yes SDK no : 'fminimum_num' 
           22: << TLI yes SDK no : 'fminimum_numf' 
           23: << TLI yes SDK no : 'fminimum_numl' 
           24: << Total TLI yes SDK no: 18 
           25: >> Total TLI no SDK yes: 0 
check:37'0                               X error: no match found
           26: == Total TLI yes SDK yes: 256 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

********************


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.

fdim(x, y) is not folded at the compilation time when (x, y) is constant
5 participants