[llvm-branch-commits] [clang] [llvm] release/19.x: workflows/release-binaries: Enable flang builds on Windows (#101344) (PR #106480)

2024-09-02 Thread Tobias Hieta via llvm-branch-commits
tru wrote: @tstellar several of the builds fail even after a rebase. Some of them seem related (especially the macOS ones, so I won't merge this until you had some time to look at it. https://github.com/llvm/llvm-project/pull/106480 ___ llvm-branch-c

[llvm-branch-commits] [llvm] release/19.x: [AVR] Fix parsing & emitting relative jumps (#106722) (PR #106729)

2024-09-02 Thread Tobias Hieta via llvm-branch-commits
tru wrote: You can just close this PR and open a new one with both commits by running the cherry-pick comment command again with both sha's listed. https://github.com/llvm/llvm-project/pull/106729 ___ llvm-branch-commits mailing list llvm-branch-commi

[llvm-branch-commits] [llvm] release/19.x: [MIPS] Optimize sortRelocs for o32 (PR #106008)

2024-09-02 Thread Tobias Hieta via llvm-branch-commits
tru wrote: Yeah I tend to agree that this is a seemingly nice to have thing, but it's not really qualifying for a bugfix or a regression. https://github.com/llvm/llvm-project/pull/106008 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.

[llvm-branch-commits] [compiler-rt] release/19.x: [builtins] Fix divtc3.c etc. compilation on Solaris/SPARC with gcc (#101662) (PR #101847)

2024-09-02 Thread Tobias Hieta via llvm-branch-commits
tru wrote: That does sound like it should be acceptable to merge if it's only blocking a out-of-tree implementation, since we don't officially support that config in that case. There is also the question as if we need to backport this - since if the main complaint for it not going into main is

[llvm-branch-commits] [llvm] [X86] Avoid generating nested CALLSEQ for TLS pointer function arguments (PR #106965)

2024-09-02 Thread Phoebe Wang via llvm-branch-commits
@@ -0,0 +1,17 @@ +; RUN: llc -verify-machineinstrs < %s -relocation-model=pic + +target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128" phoebewang wrote: Do not need this. https://github.com/llvm/llvm-project/pull/106965 __

[llvm-branch-commits] [llvm] [X86] Avoid generating nested CALLSEQ for TLS pointer function arguments (PR #106965)

2024-09-02 Thread Phoebe Wang via llvm-branch-commits
@@ -0,0 +1,17 @@ +; RUN: llc -verify-machineinstrs < %s -relocation-model=pic + +target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128" +target triple = "x86_64-unknown-linux-gnu" + +; Passing a pointer to thread-local storage to a function c

[llvm-branch-commits] [llvm] [X86] Avoid generating nested CALLSEQ for TLS pointer function arguments (PR #106965)

2024-09-02 Thread Phoebe Wang via llvm-branch-commits
@@ -0,0 +1,17 @@ +; RUN: llc -verify-machineinstrs < %s -relocation-model=pic + +target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128" +target triple = "x86_64-unknown-linux-gnu" phoebewang wrote: This can put in the RUN li

[llvm-branch-commits] [llvm] [X86] Avoid generating nested CALLSEQ for TLS pointer function arguments (PR #106965)

2024-09-02 Thread Shilei Tian via llvm-branch-commits
@@ -0,0 +1,17 @@ +; RUN: llc -verify-machineinstrs < %s -relocation-model=pic + +target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128" +target triple = "x86_64-unknown-linux-gnu" + +; Passing a pointer to thread-local storage to a function c

[llvm-branch-commits] [llvm] release/19.x: [MIPS] Optimize sortRelocs for o32 (PR #106008)

2024-09-02 Thread YunQiang Su via llvm-branch-commits
wzssyqa wrote: I don't think that it is a bugfix, thus not need to be backported. https://github.com/llvm/llvm-project/pull/106008 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/l

[llvm-branch-commits] [clang] [Serialization] Code cleanups and polish 83233 (PR #83237)

2024-09-02 Thread Ilya Biryukov via llvm-branch-commits
ilya-biryukov wrote: Thanks for fixing the problem. @alexfh and another person who was running these investigations before is on vacation until next week. I will ask if someone else can do this for them, but I wouldn't be surprised that it's involved enough that we may need to wait until next

[llvm-branch-commits] [llvm] release/19.x: [MIPS] Optimize sortRelocs for o32 (PR #106008)

2024-09-02 Thread Alex Rønne Petersen via llvm-branch-commits
alexrp wrote: @MaskRay @topperc @wzssyqa @yingopq sorry for the pings, but I assume today is the last chance to get this in, so I would love to hear your thoughts on whether you think that's a good idea. :slightly_smiling_face: https://github.com/llvm/llvm-project/pull/106008 _

[llvm-branch-commits] [clang-tools-extra] release/19.x: [clangd] Update TidyFastChecks for release/19.x (#106354) (PR #106989)

2024-09-02 Thread Nathan Ridge via llvm-branch-commits
https://github.com/HighCommander4 approved this pull request. +1 from me https://github.com/llvm/llvm-project/pull/106989 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branc

[llvm-branch-commits] [llvm] release/19.x: [AVR] Fix 16-bit LDDs with immediate overflows (#104923) (PR #106993)

2024-09-02 Thread via llvm-branch-commits
https://github.com/llvmbot created https://github.com/llvm/llvm-project/pull/106993 Backport c7a4efa Requested by: @EugeneZelenko >From 2e14b75913fb4e90c7b833b351aee99dc9b0bdbd Mon Sep 17 00:00:00 2001 From: Patryk Wychowaniec Date: Thu, 29 Aug 2024 09:28:17 +0200 Subject: [PATCH] [AVR] Fix 1

[llvm-branch-commits] [llvm] release/19.x: [AVR] Fix 16-bit LDDs with immediate overflows (#104923) (PR #106993)

2024-09-02 Thread via llvm-branch-commits
https://github.com/llvmbot milestoned https://github.com/llvm/llvm-project/pull/106993 ___ 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] release/19.x: [builtins] Fix divtc3.c etc. compilation on Solaris/SPARC with gcc (#101662) (PR #101847)

2024-09-02 Thread Rainer Orth via llvm-branch-commits
rorth wrote: It's difficult: on one hand it fixes a Solaris/SPARC build failure. On the other, it's said to cause problems for an out-of-tree z/OS port. Unfortunately, the developers refuse to publish their code, so it's almost impossible to reason about that code. https://github.com/llvm/l

[llvm-branch-commits] [clang-tools-extra] release/19.x: [clangd] Update TidyFastChecks for release/19.x (#106354) (PR #106989)

2024-09-02 Thread via llvm-branch-commits
llvmbot wrote: @llvm/pr-subscribers-clang-tools-extra Author: None (llvmbot) Changes Backport b47d7ce8121b1cb1923e879d58eaa1d63aeaaae2 Requested by: @kadircet --- Patch is 30.06 KiB, truncated to 20.00 KiB below, full version: https://github.com/llvm/llvm-project/pull/106989.diff 1 F

[llvm-branch-commits] [clang-tools-extra] release/19.x: [clangd] Update TidyFastChecks for release/19.x (#106354) (PR #106989)

2024-09-02 Thread via llvm-branch-commits
llvmbot wrote: @llvm/pr-subscribers-clangd Author: None (llvmbot) Changes Backport b47d7ce8121b1cb1923e879d58eaa1d63aeaaae2 Requested by: @kadircet --- Patch is 30.06 KiB, truncated to 20.00 KiB below, full version: https://github.com/llvm/llvm-project/pull/106989.diff 1 Files Affect

[llvm-branch-commits] [clang-tools-extra] release/19.x: [clangd] Update TidyFastChecks for release/19.x (#106354) (PR #106989)

2024-09-02 Thread via llvm-branch-commits
llvmbot wrote: @HighCommander4 What do you think about merging this PR to the release branch? https://github.com/llvm/llvm-project/pull/106989 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailma

[llvm-branch-commits] [clang-tools-extra] release/19.x: [clangd] Update TidyFastChecks for release/19.x (#106354) (PR #106989)

2024-09-02 Thread via llvm-branch-commits
https://github.com/llvmbot milestoned https://github.com/llvm/llvm-project/pull/106989 ___ 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] [clang-tools-extra] release/19.x: [clangd] Update TidyFastChecks for release/19.x (#106354) (PR #106989)

2024-09-02 Thread via llvm-branch-commits
https://github.com/llvmbot created https://github.com/llvm/llvm-project/pull/106989 Backport b47d7ce8121b1cb1923e879d58eaa1d63aeaaae2 Requested by: @kadircet >From 0de791716d55892ea1872abfec078e4e07bccb19 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?kadir=20=C3=A7etinkaya?= Date: Mon, 2 Sep 2024

[llvm-branch-commits] [llvm] release/19.x: Win release packaging: Don't try to use rpmalloc for 32-bit x86 (#106969) (PR #106985)

2024-09-02 Thread Alexandre Ganea via llvm-branch-commits
https://github.com/aganea approved this pull request. https://github.com/llvm/llvm-project/pull/106985 ___ 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] release/19.x: Win release packaging: Don't try to use rpmalloc for 32-bit x86 (#106969) (PR #106985)

2024-09-02 Thread via llvm-branch-commits
llvmbot wrote: @aganea What do you think about merging this PR to the release branch? https://github.com/llvm/llvm-project/pull/106985 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listin

[llvm-branch-commits] [llvm] release/19.x: Win release packaging: Don't try to use rpmalloc for 32-bit x86 (#106969) (PR #106985)

2024-09-02 Thread via llvm-branch-commits
https://github.com/llvmbot milestoned https://github.com/llvm/llvm-project/pull/106985 ___ 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] release/19.x: Win release packaging: Don't try to use rpmalloc for 32-bit x86 (#106969) (PR #106985)

2024-09-02 Thread via llvm-branch-commits
https://github.com/llvmbot created https://github.com/llvm/llvm-project/pull/106985 Backport ef26afcb88dcb5f2de79bfc3cf88a8ea10f230ec Requested by: @zmodem >From ca30c4312e13edb54fa2f4288f7e430854671d19 Mon Sep 17 00:00:00 2001 From: Hans Date: Mon, 2 Sep 2024 15:04:13 +0200 Subject: [PATCH]

[llvm-branch-commits] [compiler-rt] release/19.x: [compiler-rt][fuzzer] SetThreadName build fix for Mingw… (PR #106908)

2024-09-02 Thread David CARLIER via llvm-branch-commits
https://github.com/devnexen closed https://github.com/llvm/llvm-project/pull/106908 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[compiler-rt] release/19.x: [compiler-rt][fuzzer] SetThreadName build fix for Mingw… (PR #106908)

2024-09-02 Thread Martin Storsjö via llvm-branch-commits
https://github.com/mstorsjo requested changes to this pull request. Do not backport this. This breaks builds in mingw environments that don't use winpthreads! https://github.com/llvm/llvm-project/pull/106908 ___ llvm-branch-commits mailing list llvm-b

[llvm-branch-commits] [llvm] [AMDGPU] Fix sign confusion in performMulLoHiCombine (PR #106977)

2024-09-02 Thread via llvm-branch-commits
llvmbot wrote: @llvm/pr-subscribers-backend-amdgpu Author: Jay Foad (jayfoad) Changes SMUL_LOHI and UMUL_LOHI are different operations because the high part of the result is different, so it is not OK to optimize the signed version to MUL_U24/MULHI_U24 or the unsigned version to MUL_I24/

[llvm-branch-commits] [llvm] [AMDGPU] Fix sign confusion in performMulLoHiCombine (PR #106977)

2024-09-02 Thread Jay Foad via llvm-branch-commits
https://github.com/jayfoad edited https://github.com/llvm/llvm-project/pull/106977 ___ 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] Fix sign confusion in performMulLoHiCombine (PR #106977)

2024-09-02 Thread Jay Foad via llvm-branch-commits
jayfoad wrote: This is a backport of #105831. https://github.com/llvm/llvm-project/pull/106977 ___ 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] Fix sign confusion in performMulLoHiCombine (PR #106977)

2024-09-02 Thread Jay Foad via llvm-branch-commits
https://github.com/jayfoad created https://github.com/llvm/llvm-project/pull/106977 SMUL_LOHI and UMUL_LOHI are different operations because the high part of the result is different, so it is not OK to optimize the signed version to MUL_U24/MULHI_U24 or the unsigned version to MUL_I24/MULHI_I2

[llvm-branch-commits] [llvm] [AMDGPU] Fix sign confusion in performMulLoHiCombine (PR #106977)

2024-09-02 Thread Jay Foad via llvm-branch-commits
https://github.com/jayfoad milestoned https://github.com/llvm/llvm-project/pull/106977 ___ 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] release/19.x: Restrict LLVM_TARGETS_TO_BUILD in Windows release packaging (#106059) (PR #106546)

2024-09-02 Thread via llvm-branch-commits
zmodem wrote: > @zmodem (or anyone else). If you would like to add a note about this fix in > the release notes (completely optional). Please reply to this comment with a > one or two sentence description of the fix. When you are done, please add the > release:note label to this PR. How about

[llvm-branch-commits] [llvm] release/19.x: [AVR] Fix parsing & emitting relative jumps (#106722) (PR #106729)

2024-09-02 Thread Patryk Wychowaniec via llvm-branch-commits
Patryk27 wrote: Can I somehow help here? Usually I'd cherry-pick changes from https://github.com/llvm/llvm-project/pull/106739 into here myself, but since I'm not the author of the pull request, I can't modify it 👀 (and we'd probably like to avoid having two separate backport pull requests to

[llvm-branch-commits] [llvm] [X86] Avoid generating nested CALLSEQ for TLS pointer function arguments (PR #106965)

2024-09-02 Thread via llvm-branch-commits
llvmbot wrote: @llvm/pr-subscribers-backend-x86 Author: Fabian Ritter (ritter-x2a) Changes When a pointer to thread-local storage is passed in a function call, ISel first lowers the call and wraps the resulting code in CALLSEQ markers. Afterwards, to compute the pointer to TLS, a call to r

[llvm-branch-commits] [llvm] [X86] Avoid generating nested CALLSEQ for TLS pointer function arguments (PR #106965)

2024-09-02 Thread Fabian Ritter via llvm-branch-commits
https://github.com/ritter-x2a ready_for_review https://github.com/llvm/llvm-project/pull/106965 ___ 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] [X86] Avoid generating nested CALLSEQ for TLS pointer function arguments (PR #106965)

2024-09-02 Thread Fabian Ritter via llvm-branch-commits
ritter-x2a 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/106965?utm_source=stack-comment-downstack-mergeability-warnin

[llvm-branch-commits] [llvm] [X86] Avoid generating nested CALLSEQ for TLS pointer function arguments (PR #106965)

2024-09-02 Thread Fabian Ritter via llvm-branch-commits
https://github.com/ritter-x2a created https://github.com/llvm/llvm-project/pull/106965 When a pointer to thread-local storage is passed in a function call, ISel first lowers the call and wraps the resulting code in CALLSEQ markers. Afterwards, to compute the pointer to TLS, a call to retrieve th

[llvm-branch-commits] [llvm] [LoongArch] Add TTI support for cpop with LSX (PR #106961)

2024-09-02 Thread via llvm-branch-commits
https://github.com/wangleiat updated https://github.com/llvm/llvm-project/pull/106961 >From 456935df7a65147dce6fbb8da8e60094ed647161 Mon Sep 17 00:00:00 2001 From: wanglei Date: Mon, 2 Sep 2024 17:59:38 +0800 Subject: [PATCH] remove debug msg Created using spr 1.3.5-bogner --- llvm/lib/Target

[llvm-branch-commits] [LoongArch] Add TTI support for cpop with LSX (PR #106961)

2024-09-02 Thread via llvm-branch-commits
llvmbot wrote: @llvm/pr-subscribers-backend-loongarch Author: wanglei (wangleiat) Changes --- Full diff: https://github.com/llvm/llvm-project/pull/106961.diff 4 Files Affected: - (modified) llvm/lib/Target/LoongArch/LoongArchTargetTransformInfo.cpp (+7) - (modified) llvm/lib/Target/L

[llvm-branch-commits] [LoongArch] Add TTI support for cpop with LSX (PR #106961)

2024-09-02 Thread via llvm-branch-commits
https://github.com/wangleiat created https://github.com/llvm/llvm-project/pull/106961 None ___ 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] c0f53ea - Revert "[RuntimeDyld][Windows] Allocate space for dllimport things. (#102586)"

2024-09-02 Thread via llvm-branch-commits
Author: Alastair Houghton Date: 2024-09-02T10:24:44+01:00 New Revision: c0f53ea70d7886b6504aa787b834b8216a4b3367 URL: https://github.com/llvm/llvm-project/commit/c0f53ea70d7886b6504aa787b834b8216a4b3367 DIFF: https://github.com/llvm/llvm-project/commit/c0f53ea70d7886b6504aa787b834b8216a4b3367.d

[llvm-branch-commits] [llvm] release/19.x: [RemoveDIs] Fix spliceDebugInfo splice-to-end edge case (#105671, #106723) (PR #106952)

2024-09-02 Thread Orlando Cazalet-Hyams via llvm-branch-commits
https://github.com/OCHyams edited https://github.com/llvm/llvm-project/pull/106952 ___ 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] release/19.x: [RemoveDIs] Fix spliceDebugInfo splice-to-end edge case (#105671) (PR #106691)

2024-09-02 Thread Orlando Cazalet-Hyams via llvm-branch-commits
https://github.com/OCHyams closed https://github.com/llvm/llvm-project/pull/106691 ___ 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] release/19.x: [RemoveDIs] Fix spliceDebugInfo splice-to-end edge case (#105671) (PR #106691)

2024-09-02 Thread Orlando Cazalet-Hyams via llvm-branch-commits
OCHyams wrote: Re-opened backport request with the fix too - #106952 https://github.com/llvm/llvm-project/pull/106691 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-c

[llvm-branch-commits] [llvm] release/19.x: [RemoveDIs] Fix spliceDebugInfo splice-to-end edge case (#105671, #106723) (PR #106952)

2024-09-02 Thread via llvm-branch-commits
llvmbot wrote: @llvm/pr-subscribers-llvm-ir Author: Orlando Cazalet-Hyams (OCHyams) Changes Please can we backport 43661a1214353ea1773a711f403f8d1118e9ca0f (and 7ffe67c17c524c2d3056c0721a33c7012dce3061) into the next dot release. Replaces #106691 - this one includes a follow-up fix in 7

[llvm-branch-commits] [llvm] release/19.x: [RemoveDIs] Fix spliceDebugInfo splice-to-end edge case (#105671, #106723) (PR #106952)

2024-09-02 Thread Orlando Cazalet-Hyams via llvm-branch-commits
https://github.com/OCHyams created https://github.com/llvm/llvm-project/pull/106952 Please can we backport 43661a1214353ea1773a711f403f8d1118e9ca0f (and 7ffe67c17c524c2d3056c0721a33c7012dce3061) into the next dot release. Replaces #106691 - this one includes a follow-up fix in 7ffe67c17c524c2