[llvm-branch-commits] [llvm] [AMDGPU] Serialize WWM_REG vreg flag (PR #110229)

https://github.com/Akshat-Oke updated https://github.com/llvm/llvm-project/pull/110229 >From 80207b7bd00d4b0889918d9a7df627f7c304bd7d Mon Sep 17 00:00:00 2001 From: Akshat Oke Date: Fri, 27 Sep 2024 08:58:39 + Subject: [PATCH 1/3] [AMDGPU] Serialize WWM_REG vreg flag --- llvm/lib/Target/A

[llvm-branch-commits] [flang] [flang] Lower omp.workshare to other omp constructs (PR #101446)

ivanradanov wrote: > My concern with the TODO message is that some code that previously compiled > using the lowering of WORKSHARE as SINGLE will now hit this TODO. This is > okay with me so long as it is fixed soon (before LLVM 20). Otherwise, could > these cases continued to be lowered as SI

[llvm-branch-commits] [flang] [flang] Lower omp.workshare to other omp constructs (PR #101446)

https://github.com/ivanradanov updated https://github.com/llvm/llvm-project/pull/101446 >From e56dbd6a0625890fd9a3d6a62675e864ca94a8f5 Mon Sep 17 00:00:00 2001 From: Ivan Radanov Ivanov Date: Sun, 4 Aug 2024 22:06:55 +0900 Subject: [PATCH 1/9] [flang] Lower omp.workshare to other omp constructs

[llvm-branch-commits] [flang] [WIP][flang] Introduce HLFIR lowerings to omp.workshare_loop_nest (PR #104748)

https://github.com/ivanradanov updated https://github.com/llvm/llvm-project/pull/104748 >From 4c207b5c8e44d83eea08d283b8e3811585137744 Mon Sep 17 00:00:00 2001 From: Ivan Radanov Ivanov Date: Fri, 4 Oct 2024 15:28:07 +0900 Subject: [PATCH 1/6] Different warning --- flang/lib/Optimizer/OpenMP/

[llvm-branch-commits] [llvm] [AMDGPU] Serialize WWM_REG vreg flag (PR #110229)

@@ -0,0 +1,16 @@ +# RUN: llc -mtriple=amdgcn -run-pass=none -o - %s | FileCheck %s Akshat-Oke wrote: Negative test is now in MIR/Generic. https://github.com/llvm/llvm-project/pull/110229 ___ llvm-branch-commits mailing

[llvm-branch-commits] [flang] [WIP][flang] Introduce HLFIR lowerings to omp.workshare_loop_nest (PR #104748)

ivanradanov wrote: @Thirumalai-Shaktivel Fixed, it was a very stupid mistake with the argument order of the copyprivate copy function. Thank you. https://github.com/llvm/llvm-project/pull/104748 ___ llvm-branch-commits mailing list llvm-branch-commits

[llvm-branch-commits] [flang] [flang] Lower omp.workshare to other omp constructs (PR #101446)

https://github.com/ivanradanov updated https://github.com/llvm/llvm-project/pull/101446 >From e56dbd6a0625890fd9a3d6a62675e864ca94a8f5 Mon Sep 17 00:00:00 2001 From: Ivan Radanov Ivanov Date: Sun, 4 Aug 2024 22:06:55 +0900 Subject: [PATCH 1/8] [flang] Lower omp.workshare to other omp constructs

[llvm-branch-commits] [flang] [WIP][flang] Introduce HLFIR lowerings to omp.workshare_loop_nest (PR #104748)

https://github.com/ivanradanov updated https://github.com/llvm/llvm-project/pull/104748 >From 07a9eb3581f480c47ce4de3de00c7cef15df3cdc Mon Sep 17 00:00:00 2001 From: Ivan Radanov Ivanov Date: Fri, 4 Oct 2024 14:21:14 +0900 Subject: [PATCH 1/7] Fix dst src in copy function --- flang/lib/Optimi

[llvm-branch-commits] [clang] 3217472 - Revert "[RISCV][FMV] Support target_version (#99040)"

Author: Piyou Chen Date: 2024-10-04T11:55:45+08:00 New Revision: 32174720649068de7c4ef97a484d777dba72e65c URL: https://github.com/llvm/llvm-project/commit/32174720649068de7c4ef97a484d777dba72e65c DIFF: https://github.com/llvm/llvm-project/commit/32174720649068de7c4ef97a484d777dba72e65c.diff LO

[llvm-branch-commits] [BOLT] Support perf2bolt-N in the driver (PR #111072)

llvmbot wrote: @llvm/pr-subscribers-bolt Author: Amir Ayupov (aaupov) Changes Check invoked tool with `starts_with` --- Full diff: https://github.com/llvm/llvm-project/pull/111072.diff 1 Files Affected: - (modified) bolt/tools/driver/llvm-bolt.cpp (+2-2) ``diff diff --git a

[llvm-branch-commits] [BOLT] Support perf2bolt-N in the driver (PR #111072)

https://github.com/aaupov created https://github.com/llvm/llvm-project/pull/111072 Check invoked tool with `starts_with` ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bra

[llvm-branch-commits] [compiler-rt] [llvm] [Coverage] Make SingleByteCoverage work consistent to merging (PR #110972)

@@ -952,7 +952,7 @@ void InstrProfRecord::merge(InstrProfRecord &Other, uint64_t Weight, Value = getInstrMaxCountValue(); Overflowed = true; } -Counts[I] = Value; ellishg wrote: I think that makes sense for frontend coverage since we aren'

[llvm-branch-commits] [compiler-rt] [llvm] [Coverage] Make SingleByteCoverage work consistent to merging (PR #110972)

@@ -952,7 +952,7 @@ void InstrProfRecord::merge(InstrProfRecord &Other, uint64_t Weight, Value = getInstrMaxCountValue(); Overflowed = true; } -Counts[I] = Value; chapuni wrote: I didn't imagine use cases in PGO. I'll leave it unchanged.

[llvm-branch-commits] [BOLT] Support --show-density for fdata and YAML profiles (PR #110567)

https://github.com/aaupov closed https://github.com/llvm/llvm-project/pull/110567 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-branch-commits] [compiler-rt] [llvm] [Coverage] Make SingleByteCoverage work consistent to merging (PR #110972)

@@ -952,7 +952,7 @@ void InstrProfRecord::merge(InstrProfRecord &Other, uint64_t Weight, Value = getInstrMaxCountValue(); Overflowed = true; } -Counts[I] = Value; ellishg wrote: This is deliberate. Even though we only record boolean covera

[llvm-branch-commits] [llvm] AMDGPU: Do not tail call if an inreg argument requires waterfalling (PR #111002)

https://github.com/arsenm updated https://github.com/llvm/llvm-project/pull/111002 >From ac0b62834e39264a02656301515c8023b350b33d Mon Sep 17 00:00:00 2001 From: Matt Arsenault Date: Thu, 3 Oct 2024 16:06:49 +0400 Subject: [PATCH] AMDGPU: Do not tail call if an inreg argument requires waterfall

[llvm-branch-commits] [llvm] AMDGPU: Do not tail call if an inreg argument requires waterfalling (PR #111002)

llvmbot wrote: @llvm/pr-subscribers-backend-amdgpu Author: Matt Arsenault (arsenm) Changes If we have a divergent value passed to an outgoing inreg argument, the call needs to be executed in a waterfall loop and thus cannot be tail called. The waterfall handling of arbitrary calls is brok

[llvm-branch-commits] [llvm] AMDGPU: Do not tail call if an inreg argument requires waterfalling (PR #111002)

arsenm wrote: > [!WARNING] > This pull request is not mergeable via GitHub because a downstack PR is > open. Once all requirements are satisfied, merge this PR as a stack href="https://app.graphite.dev/github/pr/llvm/llvm-project/111002?utm_source=stack-comment-downstack-mergeability-warning";

[llvm-branch-commits] [llvm] AMDGPU: Do not tail call if an inreg argument requires waterfalling (PR #111002)

https://github.com/arsenm ready_for_review https://github.com/llvm/llvm-project/pull/111002 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-branch-commits] [llvm] AMDGPU: Do not tail call if an inreg argument requires waterfalling (PR #111002)

https://github.com/arsenm created https://github.com/llvm/llvm-project/pull/111002 If we have a divergent value passed to an outgoing inreg argument, the call needs to be executed in a waterfall loop and thus cannot be tail called. The waterfall handling of arbitrary calls is broken on the sele

[llvm-branch-commits] [flang] [WIP][flang] Introduce HLFIR lowerings to omp.workshare_loop_nest (PR #104748)

ivanradanov wrote: Thank you very much - it seems to only happen with `-O0`, I am trying to find the root cause now... https://github.com/llvm/llvm-project/pull/104748 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lis

[llvm-branch-commits] [lldb] 3983d73 - Revert "[lldb][test] TestDataFormatterLibcxxStringSimulator.py: add new paddi…"

Author: Michael Buch Date: 2024-10-03T14:57:40+01:00 New Revision: 3983d73e32a793b42a3955a34a0662daafa1355f URL: https://github.com/llvm/llvm-project/commit/3983d73e32a793b42a3955a34a0662daafa1355f DIFF: https://github.com/llvm/llvm-project/commit/3983d73e32a793b42a3955a34a0662daafa1355f.diff

[llvm-branch-commits] [llvm] [MergeFunctions] Add support to run the pass over a set of function pointers (PR #110996)

github-actions[bot] wrote: This repository does not accept pull requests. Please follow http://llvm.org/docs/Contributing.html#how-to-submit-a-patch for contribution to LLVM. https://github.com/llvm/llvm-project/pull/110996 ___ llvm-branch-commits ma

[llvm-branch-commits] [llvm] [MergeFunctions] Add support to run the pass over a set of function pointers (PR #110996)

https://github.com/github-actions[bot] closed https://github.com/llvm/llvm-project/pull/110996 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-branch-commits] [llvm] [MergeFunctions] Add support to run the pass over a set of function pointers (PR #110996)

https://github.com/github-actions[bot] locked https://github.com/llvm/llvm-project/pull/110996 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-branch-commits] [llvm] [MergeFunctions] Add support to run the pass over a set of function pointers (PR #110996)

https://github.com/Casperento created https://github.com/llvm/llvm-project/pull/110996 This modification will enable the usage of `MergeFunctions` as a standalone library. Currently, `MergeFunctions` can only be applied to an entire module. By adopting this change, developers will gain the fle

[llvm-branch-commits] [libcxx] [release/19.x][libc++] Follow-up to "Poison Pills are Too Toxic" (PR #109291)

https://github.com/ldionne updated https://github.com/llvm/llvm-project/pull/109291 >From 094cc808ded9b00a50e26b91898323e17cc4840f Mon Sep 17 00:00:00 2001 From: Jakub Mazurkiewicz Date: Wed, 10 Apr 2024 23:12:22 +0200 Subject: [PATCH 1/2] [libc++] Follow-up to "Poison Pills are Too Toxic" * U

[llvm-branch-commits] [llvm] [RISCV][CFI] add function epilogue cfi information (PR #110810)

https://github.com/dlav-sc edited https://github.com/llvm/llvm-project/pull/110810 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-branch-commits] [flang] [WIP][flang] Introduce HLFIR lowerings to omp.workshare_loop_nest (PR #104748)

Thirumalai-Shaktivel wrote: Hi @ivanradanov, thanks for the PR! I tried building and testing this PR. And came across a case where it seg faults. Can you please check it? ```fortran program test real :: arr_01(10) !$omp parallel workshare arr_01 = arr_01*2 !$

[llvm-branch-commits] [compiler-rt] [llvm] [Coverage] Make SingleByteCoverage work consistent to merging (PR #110972)

llvmbot wrote: @llvm/pr-subscribers-pgo Author: NAKAMURA Takumi (chapuni) Changes - Round `Counts` as 1/0 - Confirm both `ExecutionCount` and `AltExecutionCount` are in range. --- Full diff: https://github.com/llvm/llvm-project/pull/110972.diff 6 Files Affected: - (modified) compiler-r

[llvm-branch-commits] [compiler-rt] [llvm] [Coverage] Make SingleByteCoverage work consistent to merging (PR #110972)

https://github.com/chapuni created https://github.com/llvm/llvm-project/pull/110972 - Round `Counts` as 1/0 - Confirm both `ExecutionCount` and `AltExecutionCount` are in range. >From aacb50ddf87d96b4a0644c7ef5d0a86dc94f069b Mon Sep 17 00:00:00 2001 From: NAKAMURA Takumi Date: Wed, 2 Oct 2024