[llvm-branch-commits] [llvm] Store GUIDs in metadata (PR #133682)

2025-03-30 Thread Owen Rodley via llvm-branch-commits
https://github.com/orodley updated https://github.com/llvm/llvm-project/pull/133682 >From dd0751618d4eac29a6af13b2e747ed505ec9b321 Mon Sep 17 00:00:00 2001 From: Owen Rodley Date: Mon, 31 Mar 2025 16:16:35 +1100 Subject: [PATCH] Store GUIDs in metadata This takes the existing AssignGUID pass f

[llvm-branch-commits] [llvm] Store GUIDs in metadata (PR #133682)

2025-03-30 Thread Owen Rodley via llvm-branch-commits
https://github.com/orodley created https://github.com/llvm/llvm-project/pull/133682 This takes the existing AssignGUID pass from CtxProfAnalysis, and runs it by default, at the appropriate stages of the LTO pipeline. It also changes GlobalValue::getGUID() to retrieve the GUID from the metadata i

[llvm-branch-commits] [llvm] Store GUIDs in metadata (PR #133682)

2025-03-30 Thread via llvm-branch-commits
github-actions[bot] wrote: :warning: C/C++ code formatter, clang-format found issues in your code. :warning: You can test this locally with the following command: ``bash git-clang-format --diff 8ef355aa433a44220eaf0062039b53770ebb9835 1379952ca664e04c4aa6806a724bcda1b0fc1a48 --e

[llvm-branch-commits] [llvm] Store GUIDs in metadata (PR #133682)

2025-03-30 Thread Owen Rodley via llvm-branch-commits
orodley 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/133682?utm_source=stack-comment-downstack-mergeability-warning";

[llvm-branch-commits] [clang] [clang-tools-extra] [libcxx] [clang] improved preservation of template keyword (PR #133610)

2025-03-30 Thread Matheus Izvekov via llvm-branch-commits
https://github.com/mizvekov edited https://github.com/llvm/llvm-project/pull/133610 ___ 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] llvm-reduce: Reduce with early return of arguments (PR #133627)

2025-03-30 Thread John Regehr via llvm-branch-commits
regehr wrote: yeah I don't feel like we'll get interesting variants out of this one very often, but who knows. at some point it would be interesting to get a global view of which passes are providing interesting variants in practice and which ones aren't. anyhow-- LGTM, this shouldn't slow re

[llvm-branch-commits] [llvm] [LoopInterchange] Improve profitability check for vectorization (PR #133672)

2025-03-30 Thread via llvm-branch-commits
llvmbot wrote: @llvm/pr-subscribers-llvm-transforms Author: Ryotaro Kasuga (kasuga-fj) Changes The vectorization profitability has a process to check whether a given loop can be vectorized or not. Since the process is conservative, a loop that can be vectorized may be deemed not to be po

[llvm-branch-commits] [llvm] [LoopInterchange] Improve profitability check for vectorization (PR #133672)

2025-03-30 Thread Ryotaro Kasuga via llvm-branch-commits
https://github.com/kasuga-fj created https://github.com/llvm/llvm-project/pull/133672 The vectorization profitability has a process to check whether a given loop can be vectorized or not. Since the process is conservative, a loop that can be vectorized may be deemed not to be possible. This ca

[llvm-branch-commits] [llvm] [LoopInterchange] Add tests for the vectorization profitability (NFC) (PR #133665)

2025-03-30 Thread via llvm-branch-commits
llvmbot wrote: @llvm/pr-subscribers-llvm-transforms Author: Ryotaro Kasuga (kasuga-fj) Changes There is a problem with the current profitability check for vectorization in LoopInterchange. There are both false positives and false negatives. The former means that the heuristic may say tha

[llvm-branch-commits] [llvm] [LoopInterchange] Add tests for the vectorization profitability (NFC) (PR #133665)

2025-03-30 Thread Ryotaro Kasuga via llvm-branch-commits
https://github.com/kasuga-fj created https://github.com/llvm/llvm-project/pull/133665 There is a problem with the current profitability check for vectorization in LoopInterchange. There are both false positives and false negatives. The former means that the heuristic may say that "an exchange

[llvm-branch-commits] [llvm] [SDAG] Introduce inbounds flag for pointer arithmetic (PR #131862)

2025-03-30 Thread Fabian Ritter via llvm-branch-commits
https://github.com/ritter-x2a updated https://github.com/llvm/llvm-project/pull/131862 >From 42481628ec10fe863bc9bca94efa84cd414d385b Mon Sep 17 00:00:00 2001 From: Fabian Ritter Date: Mon, 17 Mar 2025 06:51:16 -0400 Subject: [PATCH] [SDAG] Introduce inbounds flag for pointer arithmetic This p

[llvm-branch-commits] [llvm] [Metadata] Preserve MD_prof when merging instructions when one is missing. (PR #132433)

2025-03-30 Thread Snehasish Kumar via llvm-branch-commits
@@ -0,0 +1,62 @@ +; NOTE: Assertions have been autogenerated by utils/update_test_checks.py UTC_ARGS: --check-globals --version 2 +; RUN: opt < %s -passes='simplifycfg' -simplifycfg-require-and-preserve-domtree=1 -S | FileCheck %s --check-prefix=HOIST + +; Test case based on C+

[llvm-branch-commits] [llvm] [Metadata] Preserve MD_prof when merging instructions when one is missing. (PR #132433)

2025-03-30 Thread Snehasish Kumar via llvm-branch-commits
@@ -3436,6 +3433,16 @@ static void combineMetadata(Instruction *K, const Instruction *J, K->setMetadata(LLVMContext::MD_callsite, MDNode::getMergedCallsiteMetadata(KCallSite, JCallSite)); } + + // Merge prof metadata. + // Handle separately to suppor

[llvm-branch-commits] [llvm] [Metadata] Preserve MD_prof when merging instructions when one is missing. (PR #132433)

2025-03-30 Thread Snehasish Kumar via llvm-branch-commits
https://github.com/snehasish updated https://github.com/llvm/llvm-project/pull/132433 >From 42a9972571f8c8872e7d71def2236be400428606 Mon Sep 17 00:00:00 2001 From: Snehasish Kumar Date: Fri, 21 Mar 2025 17:00:38 + Subject: [PATCH] Update tests, apply clang-tidy suggestions --- llvm/lib/Tr

[llvm-branch-commits] [llvm] [Metadata] Preserve MD_prof when merging instructions when one is missing. (PR #132433)

2025-03-30 Thread Snehasish Kumar via llvm-branch-commits
https://github.com/snehasish updated https://github.com/llvm/llvm-project/pull/132433 >From 42a9972571f8c8872e7d71def2236be400428606 Mon Sep 17 00:00:00 2001 From: Snehasish Kumar Date: Fri, 21 Mar 2025 17:00:38 + Subject: [PATCH] Update tests, apply clang-tidy suggestions --- llvm/lib/Tr

[llvm-branch-commits] [clang] [clang] Track final substitution for Subst* AST nodes (PR #132748)

2025-03-30 Thread Matheus Izvekov via llvm-branch-commits
https://github.com/mizvekov updated https://github.com/llvm/llvm-project/pull/132748 >From 2d4717492599f445975019339024e2d1bc02128f Mon Sep 17 00:00:00 2001 From: Matheus Izvekov Date: Sat, 22 Mar 2025 16:03:04 -0300 Subject: [PATCH 1/4] [clang] Track final substitution for SubstTemplateTempla

[llvm-branch-commits] [llvm] release/20.x: [TailDuplicator] Determine if computed gotos using `blockaddress` (#132536) (PR #133082)

2025-03-30 Thread Matt Arsenault via llvm-branch-commits
https://github.com/arsenm approved this pull request. I can't say I know much about the feature but this should strictly move in a more conservative direction https://github.com/llvm/llvm-project/pull/133082 ___ llvm-branch-commits mailing list llvm-

[llvm-branch-commits] [llvm] release/20.x: [TailDuplicator] Determine if computed gotos using `blockaddress` (#132536) (PR #133082)

2025-03-30 Thread via llvm-branch-commits
https://github.com/dianqk updated https://github.com/llvm/llvm-project/pull/133082 >From a78eb0808e553ac933c39e41164bb530ce025a0e Mon Sep 17 00:00:00 2001 From: dianqk Date: Wed, 26 Mar 2025 21:27:43 +0800 Subject: [PATCH] [TailDuplicator] Determine if computed gotos using `blockaddress` (#132

[llvm-branch-commits] [llvm] llvm-reduce: Defer a shouldKeep call in operand reduction (PR #133387)

2025-03-30 Thread Matt Arsenault via llvm-branch-commits
https://github.com/arsenm updated https://github.com/llvm/llvm-project/pull/133387 >From fa597dd4161693813a3566fd1d4a3c7df1d00746 Mon Sep 17 00:00:00 2001 From: Matt Arsenault Date: Fri, 28 Mar 2025 12:58:20 +0700 Subject: [PATCH] llvm-reduce: Defer a shouldKeep call in operand reduction Ideal

[llvm-branch-commits] [llvm] llvm-reduce: Reduce with early return of arguments (PR #133627)

2025-03-30 Thread via llvm-branch-commits
llvmbot wrote: @llvm/pr-subscribers-llvm-ir Author: Matt Arsenault (arsenm) Changes Extend the instruction -> return reduction with one that inserts return of function arguments. Not sure how useful this really is. This has more freedom since we could insert the return anywhere in the func

[llvm-branch-commits] [llvm] llvm-reduce: Reduce with early return of arguments (PR #133627)

2025-03-30 Thread Matt Arsenault via llvm-branch-commits
https://github.com/arsenm ready_for_review https://github.com/llvm/llvm-project/pull/133627 ___ 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] llvm-reduce: Reduce with early return of arguments (PR #133627)

2025-03-30 Thread Matt Arsenault via llvm-branch-commits
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/133627?utm_source=stack-comment-downstack-mergeability-warning";

[llvm-branch-commits] [llvm] llvm-reduce: Reduce with early return of arguments (PR #133627)

2025-03-30 Thread Matt Arsenault via llvm-branch-commits
https://github.com/arsenm created https://github.com/llvm/llvm-project/pull/133627 Extend the instruction -> return reduction with one that inserts return of function arguments. Not sure how useful this really is. This has more freedom since we could insert the return anywhere in the function, b