Skip to content

[TLI] Add support for hypot libcall. #113724

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

Merged
merged 1 commit into from
Oct 30, 2024

Conversation

MouriNaruto
Copy link
Contributor

This patch adds basic support for hypot. Constant folding support will be submitted in a subsequent patch.

Related issue: #113711

Note: It's my first time contributing to the LLVM with encouragement from one of my friends, @fawdlstty. I learned a lot from #99611, and thanks for that.

Kenji Mouri

Copy link

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

@llvmbot llvmbot added llvm:analysis Includes value tracking, cost tables and constant folding llvm:transforms labels Oct 25, 2024
@llvmbot
Copy link
Member

llvmbot commented Oct 25, 2024

@llvm/pr-subscribers-llvm-transforms

Author: Kenji Mouri / 毛利 研二 (MouriNaruto)

Changes

This patch adds basic support for hypot. Constant folding support will be submitted in a subsequent patch.

Related issue: #113711

Note: It's my first time contributing to the LLVM with encouragement from one of my friends, @fawdlstty. I learned a lot from #99611, and thanks for that.

Kenji Mouri


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

6 Files Affected:

  • (modified) llvm/include/llvm/Analysis/TargetLibraryInfo.def (+15)
  • (modified) llvm/lib/Analysis/TargetLibraryInfo.cpp (+3)
  • (modified) llvm/lib/Transforms/Utils/BuildLibCalls.cpp (+3)
  • (modified) llvm/test/Transforms/InferFunctionAttrs/annotate.ll (+9)
  • (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 f890e2b9ec4c82..f43ee40fa1b87f 100644
--- a/llvm/include/llvm/Analysis/TargetLibraryInfo.def
+++ b/llvm/include/llvm/Analysis/TargetLibraryInfo.def
@@ -1656,6 +1656,21 @@ TLI_DEFINE_ENUM_INTERNAL(htons)
 TLI_DEFINE_STRING_INTERNAL("htons")
 TLI_DEFINE_SIG_INTERNAL(Int16, Int16)
 
+/// double hypot(double x, double y);
+TLI_DEFINE_ENUM_INTERNAL(hypot)
+TLI_DEFINE_STRING_INTERNAL("hypot")
+TLI_DEFINE_SIG_INTERNAL(Dbl, Dbl, Dbl)
+
+/// float hypotf(float x, float y);
+TLI_DEFINE_ENUM_INTERNAL(hypotf)
+TLI_DEFINE_STRING_INTERNAL("hypotf")
+TLI_DEFINE_SIG_INTERNAL(Flt, Flt, Flt)
+
+/// long double hypotl(long double x, long double y);
+TLI_DEFINE_ENUM_INTERNAL(hypotl)
+TLI_DEFINE_STRING_INTERNAL("hypotl")
+TLI_DEFINE_SIG_INTERNAL(LDbl, LDbl, LDbl)
+
 /// int iprintf(const char *format, ...);
 TLI_DEFINE_ENUM_INTERNAL(iprintf)
 TLI_DEFINE_STRING_INTERNAL("iprintf")
diff --git a/llvm/lib/Analysis/TargetLibraryInfo.cpp b/llvm/lib/Analysis/TargetLibraryInfo.cpp
index 0ee83d217a5001..947f168fcaf618 100644
--- a/llvm/lib/Analysis/TargetLibraryInfo.cpp
+++ b/llvm/lib/Analysis/TargetLibraryInfo.cpp
@@ -300,6 +300,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
       TLI.setUnavailable(LibFunc_expf);
       TLI.setUnavailable(LibFunc_floorf);
       TLI.setUnavailable(LibFunc_fmodf);
+      TLI.setUnavailable(LibFunc_hypotf);
       TLI.setUnavailable(LibFunc_log10f);
       TLI.setUnavailable(LibFunc_logf);
       TLI.setUnavailable(LibFunc_modff);
@@ -331,6 +332,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
     TLI.setUnavailable(LibFunc_floorl);
     TLI.setUnavailable(LibFunc_fmodl);
     TLI.setUnavailable(LibFunc_frexpl);
+    TLI.setUnavailable(LibFunc_hypotl);
     TLI.setUnavailable(LibFunc_ldexpl);
     TLI.setUnavailable(LibFunc_log10l);
     TLI.setUnavailable(LibFunc_logl);
@@ -367,6 +369,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
       TLI.setUnavailable(LibFunc_fmaxf);
       TLI.setUnavailable(LibFunc_fmin);
       TLI.setUnavailable(LibFunc_fminf);
+      TLI.setAvailableWithName(LibFunc_hypot, "_hypot");
       TLI.setUnavailable(LibFunc_log1p);
       TLI.setUnavailable(LibFunc_log1pf);
       TLI.setUnavailable(LibFunc_log2);
diff --git a/llvm/lib/Transforms/Utils/BuildLibCalls.cpp b/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
index 13323604eb514a..905ae9ba186c84 100644
--- a/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
+++ b/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
@@ -1212,6 +1212,9 @@ bool llvm::inferNonMandatoryLibFuncAttrs(Function &F,
   case LibFunc_fmod:
   case LibFunc_fmodf:
   case LibFunc_fmodl:
+  case LibFunc_hypot:
+  case LibFunc_hypotf:
+  case LibFunc_hypotl:
   case LibFunc_isascii:
   case LibFunc_isdigit:
   case LibFunc_labs:
diff --git a/llvm/test/Transforms/InferFunctionAttrs/annotate.ll b/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
index 3e9b2d94efda89..e6a8172cd9f85e 100644
--- a/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
+++ b/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
@@ -589,6 +589,15 @@ declare ptr @gets(ptr)
 ; CHECK: declare noundef i32 @gettimeofday(ptr nocapture noundef, ptr nocapture noundef) [[NOFREE_NOUNWIND]]
 declare i32 @gettimeofday(ptr, ptr)
 
+; CHECK: declare double @hypot(double, double) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare double @hypot(double, double)
+
+; CHECK: declare float @hypotf(float, float) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare float @hypotf(float, float)
+
+; CHECK: declare x86_fp80 @hypotl(x86_fp80, x86_fp80) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare x86_fp80 @hypotl(x86_fp80, x86_fp80)
+
 ; CHECK: declare i32 @isascii(i32) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
 declare i32 @isascii(i32)
 
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 20e7e15e3efb55..85729c0e549114 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: 265
+# CHECK: == Total TLI yes SDK yes: 268
 #
 # 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: 264
+# WRONG_SUMMARY: == Total TLI yes SDK yes: 267
 #
 ## 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 516 symbols, 283 available
-# AVAIL-COUNT-283: {{^}} available
+# AVAIL: TLI knows 519 symbols, 286 available
+# AVAIL-COUNT-286: {{^}} available
 # AVAIL-NOT:       {{^}} available
 # UNAVAIL-COUNT-233: not available
 # UNAVAIL-NOT:       not available
@@ -590,6 +590,18 @@ DynamicSymbols:
     Type:            STT_FUNC
     Section:         .text
     Binding:         STB_GLOBAL
+  - Name:            hypot
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
+  - Name:            hypotf
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
+  - Name:            hypotl
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
   - Name:            isdigit
     Type:            STT_FUNC
     Section:         .text
diff --git a/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp b/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
index 346940384aff91..e7b531612329f6 100644
--- a/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
+++ b/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
@@ -249,6 +249,9 @@ TEST_F(TargetLibraryInfoTest, ValidProto) {
       "declare %struct* @getpwnam(i8*)\n"
       "declare i8* @gets(i8*)\n"
       "declare i32 @gettimeofday(%struct*, i8*)\n"
+      "declare double @hypot(double, double)\n"
+      "declare float @hypotf(float, float)\n"
+      "declare x86_fp80 @hypotl(x86_fp80, x86_fp80)\n"
       "declare i32 @_Z7isasciii(i32)\n"
       "declare i32 @_Z7isdigiti(i32)\n"
       "declare i64 @labs(i64)\n"

@llvmbot
Copy link
Member

llvmbot commented Oct 25, 2024

@llvm/pr-subscribers-llvm-analysis

Author: Kenji Mouri / 毛利 研二 (MouriNaruto)

Changes

This patch adds basic support for hypot. Constant folding support will be submitted in a subsequent patch.

Related issue: #113711

Note: It's my first time contributing to the LLVM with encouragement from one of my friends, @fawdlstty. I learned a lot from #99611, and thanks for that.

Kenji Mouri


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

6 Files Affected:

  • (modified) llvm/include/llvm/Analysis/TargetLibraryInfo.def (+15)
  • (modified) llvm/lib/Analysis/TargetLibraryInfo.cpp (+3)
  • (modified) llvm/lib/Transforms/Utils/BuildLibCalls.cpp (+3)
  • (modified) llvm/test/Transforms/InferFunctionAttrs/annotate.ll (+9)
  • (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 f890e2b9ec4c82..f43ee40fa1b87f 100644
--- a/llvm/include/llvm/Analysis/TargetLibraryInfo.def
+++ b/llvm/include/llvm/Analysis/TargetLibraryInfo.def
@@ -1656,6 +1656,21 @@ TLI_DEFINE_ENUM_INTERNAL(htons)
 TLI_DEFINE_STRING_INTERNAL("htons")
 TLI_DEFINE_SIG_INTERNAL(Int16, Int16)
 
+/// double hypot(double x, double y);
+TLI_DEFINE_ENUM_INTERNAL(hypot)
+TLI_DEFINE_STRING_INTERNAL("hypot")
+TLI_DEFINE_SIG_INTERNAL(Dbl, Dbl, Dbl)
+
+/// float hypotf(float x, float y);
+TLI_DEFINE_ENUM_INTERNAL(hypotf)
+TLI_DEFINE_STRING_INTERNAL("hypotf")
+TLI_DEFINE_SIG_INTERNAL(Flt, Flt, Flt)
+
+/// long double hypotl(long double x, long double y);
+TLI_DEFINE_ENUM_INTERNAL(hypotl)
+TLI_DEFINE_STRING_INTERNAL("hypotl")
+TLI_DEFINE_SIG_INTERNAL(LDbl, LDbl, LDbl)
+
 /// int iprintf(const char *format, ...);
 TLI_DEFINE_ENUM_INTERNAL(iprintf)
 TLI_DEFINE_STRING_INTERNAL("iprintf")
diff --git a/llvm/lib/Analysis/TargetLibraryInfo.cpp b/llvm/lib/Analysis/TargetLibraryInfo.cpp
index 0ee83d217a5001..947f168fcaf618 100644
--- a/llvm/lib/Analysis/TargetLibraryInfo.cpp
+++ b/llvm/lib/Analysis/TargetLibraryInfo.cpp
@@ -300,6 +300,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
       TLI.setUnavailable(LibFunc_expf);
       TLI.setUnavailable(LibFunc_floorf);
       TLI.setUnavailable(LibFunc_fmodf);
+      TLI.setUnavailable(LibFunc_hypotf);
       TLI.setUnavailable(LibFunc_log10f);
       TLI.setUnavailable(LibFunc_logf);
       TLI.setUnavailable(LibFunc_modff);
@@ -331,6 +332,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
     TLI.setUnavailable(LibFunc_floorl);
     TLI.setUnavailable(LibFunc_fmodl);
     TLI.setUnavailable(LibFunc_frexpl);
+    TLI.setUnavailable(LibFunc_hypotl);
     TLI.setUnavailable(LibFunc_ldexpl);
     TLI.setUnavailable(LibFunc_log10l);
     TLI.setUnavailable(LibFunc_logl);
@@ -367,6 +369,7 @@ static void initializeLibCalls(TargetLibraryInfoImpl &TLI, const Triple &T,
       TLI.setUnavailable(LibFunc_fmaxf);
       TLI.setUnavailable(LibFunc_fmin);
       TLI.setUnavailable(LibFunc_fminf);
+      TLI.setAvailableWithName(LibFunc_hypot, "_hypot");
       TLI.setUnavailable(LibFunc_log1p);
       TLI.setUnavailable(LibFunc_log1pf);
       TLI.setUnavailable(LibFunc_log2);
diff --git a/llvm/lib/Transforms/Utils/BuildLibCalls.cpp b/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
index 13323604eb514a..905ae9ba186c84 100644
--- a/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
+++ b/llvm/lib/Transforms/Utils/BuildLibCalls.cpp
@@ -1212,6 +1212,9 @@ bool llvm::inferNonMandatoryLibFuncAttrs(Function &F,
   case LibFunc_fmod:
   case LibFunc_fmodf:
   case LibFunc_fmodl:
+  case LibFunc_hypot:
+  case LibFunc_hypotf:
+  case LibFunc_hypotl:
   case LibFunc_isascii:
   case LibFunc_isdigit:
   case LibFunc_labs:
diff --git a/llvm/test/Transforms/InferFunctionAttrs/annotate.ll b/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
index 3e9b2d94efda89..e6a8172cd9f85e 100644
--- a/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
+++ b/llvm/test/Transforms/InferFunctionAttrs/annotate.ll
@@ -589,6 +589,15 @@ declare ptr @gets(ptr)
 ; CHECK: declare noundef i32 @gettimeofday(ptr nocapture noundef, ptr nocapture noundef) [[NOFREE_NOUNWIND]]
 declare i32 @gettimeofday(ptr, ptr)
 
+; CHECK: declare double @hypot(double, double) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare double @hypot(double, double)
+
+; CHECK: declare float @hypotf(float, float) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare float @hypotf(float, float)
+
+; CHECK: declare x86_fp80 @hypotl(x86_fp80, x86_fp80) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
+declare x86_fp80 @hypotl(x86_fp80, x86_fp80)
+
 ; CHECK: declare i32 @isascii(i32) [[NOFREE_NOUNWIND_WILLRETURN_WRITEONLY]]
 declare i32 @isascii(i32)
 
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 20e7e15e3efb55..85729c0e549114 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: 265
+# CHECK: == Total TLI yes SDK yes: 268
 #
 # 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: 264
+# WRONG_SUMMARY: == Total TLI yes SDK yes: 267
 #
 ## 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 516 symbols, 283 available
-# AVAIL-COUNT-283: {{^}} available
+# AVAIL: TLI knows 519 symbols, 286 available
+# AVAIL-COUNT-286: {{^}} available
 # AVAIL-NOT:       {{^}} available
 # UNAVAIL-COUNT-233: not available
 # UNAVAIL-NOT:       not available
@@ -590,6 +590,18 @@ DynamicSymbols:
     Type:            STT_FUNC
     Section:         .text
     Binding:         STB_GLOBAL
+  - Name:            hypot
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
+  - Name:            hypotf
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
+  - Name:            hypotl
+    Type:            STT_FUNC
+    Section:         .text
+    Binding:         STB_GLOBAL
   - Name:            isdigit
     Type:            STT_FUNC
     Section:         .text
diff --git a/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp b/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
index 346940384aff91..e7b531612329f6 100644
--- a/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
+++ b/llvm/unittests/Analysis/TargetLibraryInfoTest.cpp
@@ -249,6 +249,9 @@ TEST_F(TargetLibraryInfoTest, ValidProto) {
       "declare %struct* @getpwnam(i8*)\n"
       "declare i8* @gets(i8*)\n"
       "declare i32 @gettimeofday(%struct*, i8*)\n"
+      "declare double @hypot(double, double)\n"
+      "declare float @hypotf(float, float)\n"
+      "declare x86_fp80 @hypotl(x86_fp80, x86_fp80)\n"
       "declare i32 @_Z7isasciii(i32)\n"
       "declare i32 @_Z7isdigiti(i32)\n"
       "declare i64 @labs(i64)\n"

@MouriNaruto MouriNaruto force-pushed the hypot-support-libcall branch 2 times, most recently from 1c28e1a to 19d1588 Compare October 25, 2024 18:38
@MouriNaruto
Copy link
Contributor Author

@arsenm @nikic @fhahn @dtcxzyw

Kenji Mouri

@dtcxzyw dtcxzyw requested a review from arsenm October 26, 2024 07:58
@MouriNaruto MouriNaruto requested a review from arsenm October 26, 2024 17:33
@MouriNaruto
Copy link
Contributor Author

@arsenm Ping

Kenji Mouri

@MouriNaruto MouriNaruto force-pushed the hypot-support-libcall branch from eba1641 to 7db20b1 Compare October 29, 2024 06:10
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.

It's still not good that TargetLibraryInfo operates on an opt-out system

@arsenm arsenm merged commit feb2d86 into llvm:main Oct 30, 2024
8 checks passed
Copy link

@MouriNaruto Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!

@llvm-ci
Copy link
Collaborator

llvm-ci commented Oct 30, 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/10445

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: 268
�[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: 271
�[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 522 symbols, 289 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 271 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 271 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 Oct 30, 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/9787

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
+ 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.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: 268
         ^
<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: 271
^

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: 271 
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 Oct 30, 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/8597

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)
...
[668/669] 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: 56162 tests, 48 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90
FAIL: LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml (53672 of 56162)
******************** 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: 268
         ^
<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: 271
^

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: 271 
Step 8 (check-llvm) failure: check-llvm (failure)
...
[668/669] 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: 56162 tests, 48 workers --
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90
FAIL: LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml (53672 of 56162)
******************** 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: 268
         ^
<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: 271
^

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: 271 

@llvm-ci
Copy link
Collaborator

llvm-ci commented Oct 30, 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/7523

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: 268
         ^
<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: 271
^

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: 271 
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 Oct 30, 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/7525

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: 268
         ^
<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: 271
^

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: 271 
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 Oct 30, 2024

LLVM Buildbot has detected a new failure on builder ml-opt-rel-x86-64 running on ml-opt-rel-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/185/builds/7634

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: 268
         ^
<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: 271
^

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: 271 
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 Oct 30, 2024

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

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

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

Command Output (stderr):
--
RUN: at line 4: /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/bin/yaml2obj /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/bin/yaml2obj /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/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/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/bin/FileCheck /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/stage1/bin/FileCheck /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/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: 268
         ^
<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: 271
^

Input file: <stdin>
Check file: /var/lib/buildbot/workers/suse-gary-m68k-cross/clang-m68k-linux-cross/llvm/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: 271 
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 Oct 30, 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/6911

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: 268
         ^
<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: 271
^

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: 271 
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 Oct 30, 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/7649

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
+ 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/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: 268
         ^
<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: 271
^

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: 271 
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 Oct 30, 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/7747

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
+ /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/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: 268
         ^
<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: 271
^

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: 271 
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 Oct 30, 2024

LLVM Buildbot has detected a new failure on builder clang-cmake-x86_64-avx512-linux running on avx512-intel64 while building llvm at step 7 "ninja check 1".

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

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

Command Output (stderr):
--
RUN: at line 4: /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/yaml2obj /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/yaml2obj /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/FileCheck /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/FileCheck /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/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: 268
         ^
<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: 271
^

Input file: <stdin>
Check file: /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/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: 271 
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 Oct 30, 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/7602

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: 268
�[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: 271
�[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 522 symbols, 289 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 271 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 271 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 Oct 30, 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/7075

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: 268
# | �[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: 271
# | �[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 522 symbols, 289 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 271 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 271 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 Oct 30, 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/7773

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: 268
         ^
<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: 271
^

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: 271 
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 Oct 30, 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/5604

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: 268
         ^
<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: 271
^

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: 271 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

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


@gulfemsavrun
Copy link
Contributor

The test added by this change is failing. Can we please revert it or fix it?

FAIL: LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml (53645 of 56538)
******************** TEST 'LLVM :: tools/llvm-tli-checker/ps4-tli-check.yaml' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 4: /b/s/w/ir/x/w/llvm_build/bin/yaml2obj /b/s/w/ir/x/w/llvm-llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/s/w/ir/x/w/llvm_build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/s/w/ir/x/w/llvm_build/bin/yaml2obj /b/s/w/ir/x/w/llvm-llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/s/w/ir/x/w/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 /b/s/w/ir/x/w/llvm_build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /b/s/w/ir/x/w/llvm_build/bin/FileCheck /b/s/w/ir/x/w/llvm-llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /b/s/w/ir/x/w/llvm_build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/s/w/ir/x/w/llvm_build/bin/FileCheck /b/s/w/ir/x/w/llvm-llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/b/s/w/ir/x/w/llvm-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: 268
         ^
<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: 271
^

Input file: <stdin>
Check file: /b/s/w/ir/x/w/llvm-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: 271 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

https://luci-milo.appspot.com/ui/p/fuchsia/builders/toolchain.ci/clang-base-linux-x64/b8732632481414041409/overview

@MouriNaruto
Copy link
Contributor Author

MouriNaruto commented Oct 30, 2024

It seems we need a fix like 2c6e5ef because the TLI test number update has not been updated properly.

Kenji Mouri

@llvm-ci
Copy link
Collaborator

llvm-ci commented Oct 30, 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/13193

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
+ 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/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: 268
         ^
<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: 271
^

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: 271 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

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


@ormris
Copy link
Collaborator

ormris commented Oct 30, 2024

@MouriNaruto This test failure has been blocking our CI. Any objections to a revert? I'd like to get the bots green again.

@llvm-ci
Copy link
Collaborator

llvm-ci commented Oct 30, 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/5581

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
+ /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/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: 268
         ^
<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: 271
^

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: 271 
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 Oct 30, 2024

LLVM Buildbot has detected a new failure on builder llvm-x86_64-debian-dylib running on gribozavr4 while building llvm at step 7 "test-build-unified-tree-check-llvm".

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

Here is the relevant piece of the build log for the reference
Step 7 (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: /b/1/llvm-x86_64-debian-dylib/build/bin/yaml2obj /b/1/llvm-x86_64-debian-dylib/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/1/llvm-x86_64-debian-dylib/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/1/llvm-x86_64-debian-dylib/build/bin/yaml2obj /b/1/llvm-x86_64-debian-dylib/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/1/llvm-x86_64-debian-dylib/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/1/llvm-x86_64-debian-dylib/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /b/1/llvm-x86_64-debian-dylib/build/bin/FileCheck /b/1/llvm-x86_64-debian-dylib/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /b/1/llvm-x86_64-debian-dylib/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/1/llvm-x86_64-debian-dylib/build/bin/FileCheck /b/1/llvm-x86_64-debian-dylib/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/b/1/llvm-x86_64-debian-dylib/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: 268
         ^
<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: 271
^

Input file: <stdin>
Check file: /b/1/llvm-x86_64-debian-dylib/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: 271 
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 Oct 30, 2024

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

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

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/1/clang-x86_64-debian-fast/llvm.obj/bin/yaml2obj /b/1/clang-x86_64-debian-fast/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/1/clang-x86_64-debian-fast/llvm.obj/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/1/clang-x86_64-debian-fast/llvm.obj/bin/yaml2obj /b/1/clang-x86_64-debian-fast/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/1/clang-x86_64-debian-fast/llvm.obj/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
RUN: at line 5: llvm-tli-checker --triple=x86_64-scei-ps4 /b/1/clang-x86_64-debian-fast/llvm.obj/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /b/1/clang-x86_64-debian-fast/llvm.obj/bin/FileCheck /b/1/clang-x86_64-debian-fast/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /b/1/clang-x86_64-debian-fast/llvm.obj/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/1/clang-x86_64-debian-fast/llvm.obj/bin/FileCheck /b/1/clang-x86_64-debian-fast/llvm.src/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/b/1/clang-x86_64-debian-fast/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: 268
         ^
<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: 271
^

Input file: <stdin>
Check file: /b/1/clang-x86_64-debian-fast/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: 271 
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 Oct 30, 2024

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

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

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/1/llvm-clang-x86_64-expensive-checks-debian/build/bin/yaml2obj /b/1/llvm-clang-x86_64-expensive-checks-debian/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/1/llvm-clang-x86_64-expensive-checks-debian/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/1/llvm-clang-x86_64-expensive-checks-debian/build/bin/yaml2obj /b/1/llvm-clang-x86_64-expensive-checks-debian/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml -DTYPE=ET_REL -DLABEL=Symbols -DZDAPV=_ZdaPv -o=/b/1/llvm-clang-x86_64-expensive-checks-debian/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/1/llvm-clang-x86_64-expensive-checks-debian/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1 | /b/1/llvm-clang-x86_64-expensive-checks-debian/build/bin/FileCheck /b/1/llvm-clang-x86_64-expensive-checks-debian/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
+ llvm-tli-checker --triple=x86_64-scei-ps4 /b/1/llvm-clang-x86_64-expensive-checks-debian/build/test/tools/llvm-tli-checker/Output/ps4-tli-check.yaml.tmp1
+ /b/1/llvm-clang-x86_64-expensive-checks-debian/build/bin/FileCheck /b/1/llvm-clang-x86_64-expensive-checks-debian/llvm-project/llvm/test/tools/llvm-tli-checker/ps4-tli-check.yaml
/b/1/llvm-clang-x86_64-expensive-checks-debian/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: 268
         ^
<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: 271
^

Input file: <stdin>
Check file: /b/1/llvm-clang-x86_64-expensive-checks-debian/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: 271 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:37'1     ?                              possible intended match
           27: FAIL: LLVM TLI doesn't match SDK libraries. 
check:37'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>

--

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


arsenm pushed a commit that referenced this pull request Oct 31, 2024
This patch adds basic support for `hypot`. Constant folding support will
be submitted in a subsequent patch.

Related issue: #113711

Note: It's my first time contributing to the LLVM with encouragement
from one of my friends, @fawdlstty. I learned a lot from
#99611, and thanks for that.

Note: I had created the same PR and merged
(#113724), but reverted caused
by the merging issue. (The CI issue happened in 3 A.M. at my timezone.
So, I need to fall asleep again after I replied about why issue
happened.) So, I rebased to the latest main branch and recreate the PR
and hope I won't have the third time to create the same PR.

I hope @arsenm can help me review the code again. I’m sorry for that.

Kenji Mouri
smallp-o-p pushed a commit to smallp-o-p/llvm-project that referenced this pull request Nov 3, 2024
smallp-o-p pushed a commit to smallp-o-p/llvm-project that referenced this pull request Nov 3, 2024
This patch adds basic support for `hypot`. Constant folding support will
be submitted in a subsequent patch.

Related issue: llvm#113711

Note: It's my first time contributing to the LLVM with encouragement
from one of my friends, @fawdlstty. I learned a lot from
llvm#99611, and thanks for that.

Note: I had created the same PR and merged
(llvm#113724), but reverted caused
by the merging issue. (The CI issue happened in 3 A.M. at my timezone.
So, I need to fall asleep again after I replied about why issue
happened.) So, I rebased to the latest main branch and recreate the PR
and hope I won't have the third time to create the same PR.

I hope @arsenm can help me review the code again. I’m sorry for that.

Kenji Mouri
NoumanAmir657 pushed a commit to NoumanAmir657/llvm-project that referenced this pull request Nov 4, 2024
This patch adds basic support for `hypot`. Constant folding support will
be submitted in a subsequent patch.

Related issue: llvm#113711

Note: It's my first time contributing to the LLVM with encouragement
from one of my friends, @fawdlstty. I learned a lot from
llvm#99611, and thanks for that.

Kenji Mouri
NoumanAmir657 pushed a commit to NoumanAmir657/llvm-project that referenced this pull request Nov 4, 2024
NoumanAmir657 pushed a commit to NoumanAmir657/llvm-project that referenced this pull request Nov 4, 2024
This patch adds basic support for `hypot`. Constant folding support will
be submitted in a subsequent patch.

Related issue: llvm#113711

Note: It's my first time contributing to the LLVM with encouragement
from one of my friends, @fawdlstty. I learned a lot from
llvm#99611, and thanks for that.

Note: I had created the same PR and merged
(llvm#113724), but reverted caused
by the merging issue. (The CI issue happened in 3 A.M. at my timezone.
So, I need to fall asleep again after I replied about why issue
happened.) So, I rebased to the latest main branch and recreate the PR
and hope I won't have the third time to create the same PR.

I hope @arsenm can help me review the code again. I’m sorry for that.

Kenji Mouri
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
llvm:analysis Includes value tracking, cost tables and constant folding llvm:transforms
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants