[llvm-branch-commits] [clang-tools-extra] release/19.x: [clang-tidy] Avoid capturing a local variable in a static lambda in UseRangesCheck (#111282) (PR #111318)

https://github.com/tru closed https://github.com/llvm/llvm-project/pull/111318 ___ 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] [AArch64][PAC] Move emission of LR checks in tail calls to AsmPrinter (PR #110705)

atrosinenko wrote: @kovdan01 Considering incorrectly choosing the scratch register, I doubt I can implement a test that is reliable: with my particular fix, it would require crafting an example that is *likely* to be emitted as an `AUTH_TCRETURN*` with AddrDisc operand being x16. I cannot simp

[llvm-branch-commits] [llvm] [AArch64][PAC] Move emission of LR checks in tail calls to AsmPrinter (PR #110705)

@@ -107,6 +107,19 @@ unsigned AArch64InstrInfo::getInstSizeInBytes(const MachineInstr &MI) const { unsigned NumBytes = 0; const MCInstrDesc &Desc = MI.getDesc(); + if (!MI.isBundle() && isTailCallReturnInst(MI)) { +NumBytes = Desc.getSize() ? Desc.getSize() : 4; + +

[llvm-branch-commits] [clang] [flang] [lld] [llvm] [Flang] LLVM_ENABLE_RUNTIMES=FortranRuntime (PR #110217)

@@ -0,0 +1,161 @@ +#===-- CMakeLists.txt --===# ldionne wrote: [not attached to this line] I don't think we have an official policy for naming top-level subdirectories, but we have consistently been using low

[llvm-branch-commits] [clang] [flang] [lld] [llvm] [Flang] LLVM_ENABLE_RUNTIMES=FortranRuntime (PR #110217)

@@ -34,6 +34,8 @@ endfunction() # llvm_ExternalProject_Add(name source_dir ... +# ENABLE_FORTRAN +# External project requires the Flang compiler ldionne wrote: I don't fully understand why you need that, but the fact that we don't need `ENABLE_CPLUSPL

[llvm-branch-commits] [clang] [flang] [lld] [llvm] [Flang] LLVM_ENABLE_RUNTIMES=FortranRuntime (PR #110217)

@@ -503,17 +513,9 @@ if(build_runtimes) endif() if("openmp" IN_LIST LLVM_ENABLE_RUNTIMES) -if (${LLVM_TOOL_FLANG_BUILD}) - message(STATUS "Configuring build of omp_lib.mod and omp_lib_kinds.mod via flang-new") - set(LIBOMP_FORTRAN_MODULES_COMPILER "${CMAKE_B

[llvm-branch-commits] [clang] [flang] [lld] [llvm] [Flang] LLVM_ENABLE_RUNTIMES=FortranRuntime (PR #110217)

https://github.com/ldionne requested changes to this pull request. https://github.com/llvm/llvm-project/pull/110217 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-comm

[llvm-branch-commits] [llvm] AMDGPU: Custom expand flat cmpxchg which may access private (PR #109410)

https://github.com/arsenm updated https://github.com/llvm/llvm-project/pull/109410 >From d281cf9a6f7c67fdcb86ca2eb3af843f0297e457 Mon Sep 17 00:00:00 2001 From: Matt Arsenault Date: Wed, 14 Aug 2024 13:57:14 +0400 Subject: [PATCH 1/2] AMDGPU: Custom expand flat cmpxchg which may access private

[llvm-branch-commits] [llvm] AMDGPU: Add baseline tests for cmpxchg custom expansion (PR #109408)

https://github.com/arsenm updated https://github.com/llvm/llvm-project/pull/109408 >From 899877cef75cfe8818c2cb773d78dd165474e863 Mon Sep 17 00:00:00 2001 From: Matt Arsenault Date: Thu, 12 Sep 2024 12:44:04 +0400 Subject: [PATCH] AMDGPU: Add baseline tests for cmpxchg custom expansion We need

[llvm-branch-commits] [llvm] release/19.x: [VectorCombine] Do not try to operate on OperandBundles. (#111635) (PR #111796)

https://github.com/davemgreen updated https://github.com/llvm/llvm-project/pull/111796 >From b64f2902d1b01234f57888fcf78282bc7cddb293 Mon Sep 17 00:00:00 2001 From: David Green Date: Wed, 9 Oct 2024 16:20:03 +0100 Subject: [PATCH 1/2] [VectorCombine] Do not try to operate on OperandBundles. (#

[llvm-branch-commits] [llvm] release/19.x: [VectorCombine] Do not try to operate on OperandBundles. (#111635) (PR #111796)

https://github.com/davemgreen updated https://github.com/llvm/llvm-project/pull/111796 >From b64f2902d1b01234f57888fcf78282bc7cddb293 Mon Sep 17 00:00:00 2001 From: David Green Date: Wed, 9 Oct 2024 16:20:03 +0100 Subject: [PATCH 1/2] [VectorCombine] Do not try to operate on OperandBundles. (#

[llvm-branch-commits] [llvm] release/19.x: [VectorCombine] Do not try to operate on OperandBundles. (#111635) (PR #111796)

davemgreen wrote: It did look like the abs/shuffle was being optimized differently in the rest of vector combine. https://github.com/llvm/llvm-project/pull/111796 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.ll

[llvm-branch-commits] [clang] [clang] Implement TTP P0522 pack matching for deduced function template calls. (PR #111457)

@@ -3172,10 +3172,11 @@ static TemplateDeductionResult ConvertDeducedTemplateArguments( } // Check whether we can actually use the default argument. -if (S.CheckTemplateArgument( -Param, DefArg, TD, TD->getLocation(), TD->getSourceRange().getEnd(), -

[llvm-branch-commits] [clang] [clang] Implement TTP P0522 pack matching for deduced function template calls. (PR #111457)

@@ -925,6 +925,8 @@ class Sema; bool TookAddressOfOverload : 1; +bool HasMatchedPackOnParmToNonPackOnArg : 1; cor3ntin wrote: Can you add a comment? https://github.com/llvm/llvm-project/pull/111457 ___ llv

[llvm-branch-commits] [clang] [clang] Implement TTP P0522 pack matching for deduced function template calls. (PR #111457)

https://github.com/cor3ntin edited https://github.com/llvm/llvm-project/pull/111457 ___ 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] [clang] Implement TTP P0522 pack matching for deduced function template calls. (PR #111457)

https://github.com/cor3ntin approved this pull request. LGTM. I don't think we need a changelog, the one from P0522 ought to be enough (we can add details to it once everything is merged) https://github.com/llvm/llvm-project/pull/111457 ___ llvm-branc

[llvm-branch-commits] [llvm] release/19.x: [VectorCombine] Do not try to operate on OperandBundles. (#111635) (PR #111796)

davemgreen wrote: I must admit OperandBundles are a new one for me. It has apparently been around for a while, and I had assumed from https://github.com/JuliaPackaging/Yggdrasil/pull/9204 that this was related to pulling clang-19 into Julia. I will have to have a look at what is behaving diff

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

https://github.com/ritter-x2a updated https://github.com/llvm/llvm-project/pull/106965 >From 58e48285971bedaa3d2cb878ddd290569b936e10 Mon Sep 17 00:00:00 2001 From: Fabian Ritter Date: Mon, 2 Sep 2024 05:37:33 -0400 Subject: [PATCH] [X86] Avoid generating nested CALLSEQ for TLS pointer functio

[llvm-branch-commits] [llvm] GlobalISel: Fix combine duplicating atomic loads (PR #111730)

https://github.com/arsenm updated https://github.com/llvm/llvm-project/pull/111730 >From 8c604131e334429111df841f00e810a3084a9956 Mon Sep 17 00:00:00 2001 From: Matt Arsenault Date: Wed, 9 Oct 2024 22:05:48 +0400 Subject: [PATCH] GlobalISel: Fix combine duplicating atomic loads The sext_inreg

[llvm-branch-commits] [llvm] [RISCV] Add initial support of memcmp expansion (PR #107548)

https://github.com/wangpc-pp updated https://github.com/llvm/llvm-project/pull/107548 >From f21cfcfc90330ee3856746b6315a81a00313b0e0 Mon Sep 17 00:00:00 2001 From: Wang Pengcheng Date: Fri, 6 Sep 2024 17:20:51 +0800 Subject: [PATCH 1/5] =?UTF-8?q?[=F0=9D=98=80=F0=9D=97=BD=F0=9D=97=BF]=20in?= =

[llvm-branch-commits] [llvm] [RISCV] Add initial support of memcmp expansion (PR #107548)

@@ -1144,42 +2872,116 @@ entry: define i32 @memcmp_size_4(ptr %s1, ptr %s2) nounwind { ; CHECK-ALIGNED-RV32-LABEL: memcmp_size_4: ; CHECK-ALIGNED-RV32: # %bb.0: # %entry -; CHECK-ALIGNED-RV32-NEXT:addi sp, sp, -16 -; CHECK-ALIGNED-RV32-NEXT:sw ra, 12(sp) # 4-byte

[llvm-branch-commits] [llvm] [RISCV] Add initial support of memcmp expansion (PR #107548)

https://github.com/wangpc-pp edited https://github.com/llvm/llvm-project/pull/107548 ___ 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: [VectorCombine] Do not try to operate on OperandBundles. (#111635) (PR #111796)

RKSimon wrote: @davemgreen The CI build failure is confusing - do OperandBundles occur in 19.x? https://github.com/llvm/llvm-project/pull/111796 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/ma

[llvm-branch-commits] [llvm] [RISCV] Add initial support of memcmp expansion (PR #107548)

https://github.com/wangpc-pp updated https://github.com/llvm/llvm-project/pull/107548 >From f21cfcfc90330ee3856746b6315a81a00313b0e0 Mon Sep 17 00:00:00 2001 From: Wang Pengcheng Date: Fri, 6 Sep 2024 17:20:51 +0800 Subject: [PATCH 1/5] =?UTF-8?q?[=F0=9D=98=80=F0=9D=97=BD=F0=9D=97=BF]=20in?= =

[llvm-branch-commits] [flang] [llvm] [Flang] Move runtime library files to FortranRuntime. NFC (PR #110298)

Meinersbur wrote: > A Fortran compiler and its runtime are tightly coupled; the compiler can only > work with this runtime, this runtime can only be used by this compiler, and > they share common API definitions and data structures. So is c C/C++ compiler and its runtime(s). There is still a n

[llvm-branch-commits] [llvm] GlobalISel: Fix combine duplicating atomic loads (PR #111730)

https://github.com/arsenm updated https://github.com/llvm/llvm-project/pull/111730 >From 90a347159e1e6494bf95bcaf87e897e553ecc0f5 Mon Sep 17 00:00:00 2001 From: Matt Arsenault Date: Wed, 9 Oct 2024 22:05:48 +0400 Subject: [PATCH 1/2] GlobalISel: Fix combine duplicating atomic loads The sext_in

[llvm-branch-commits] [llvm] GlobalISel: Fix combine duplicating atomic loads (PR #111730)

https://github.com/arsenm updated https://github.com/llvm/llvm-project/pull/111730 >From 90a347159e1e6494bf95bcaf87e897e553ecc0f5 Mon Sep 17 00:00:00 2001 From: Matt Arsenault Date: Wed, 9 Oct 2024 22:05:48 +0400 Subject: [PATCH 1/2] GlobalISel: Fix combine duplicating atomic loads The sext_in

[llvm-branch-commits] [llvm] AtomicExpand: Copy metadata from atomicrmw to cmpxchg (PR #109409)

arsenm wrote: > Did you address [#109409 > (review)](https://github.com/llvm/llvm-project/pull/109409#pullrequestreview-2332197449) > ? I switched this over to copyMetadataForAtomic but I guess I never uploaded the change https://github.com/llvm/llvm-project/pull/109409

[llvm-branch-commits] [llvm] ecf019e - Revert "[LTO] Run Argument Promotion before IPSCCP (#111163)"

Author: Hari Limaye Date: 2024-10-10T15:01:50+01:00 New Revision: ecf019eb29dafbe4c649f2fb4d34d3d238419e40 URL: https://github.com/llvm/llvm-project/commit/ecf019eb29dafbe4c649f2fb4d34d3d238419e40 DIFF: https://github.com/llvm/llvm-project/commit/ecf019eb29dafbe4c649f2fb4d34d3d238419e40.diff L

[llvm-branch-commits] [flang] [llvm] [Flang] Move runtime library files to FortranRuntime. NFC (PR #110298)

klausler wrote: > > A Fortran compiler and its runtime are tightly coupled; the compiler can > > only work with this runtime, this runtime can only be used by this > > compiler, and they share common API definitions and data structures. > > So is c C/C++ compiler and its runtime(s). There is s

[llvm-branch-commits] [flang] 7931f2b - Revert "[flang] correctly deal with bind(c) derived type result ABI (#111678)"

Author: jeanPerier Date: 2024-10-10T17:24:23+02:00 New Revision: 7931f2ba5d2412af22b63318a941c9e3c4dbd8c5 URL: https://github.com/llvm/llvm-project/commit/7931f2ba5d2412af22b63318a941c9e3c4dbd8c5 DIFF: https://github.com/llvm/llvm-project/commit/7931f2ba5d2412af22b63318a941c9e3c4dbd8c5.diff LO

[llvm-branch-commits] [llvm] [RISCV] Add initial support of memcmp expansion (PR #107548)

@@ -1144,42 +2872,116 @@ entry: define i32 @memcmp_size_4(ptr %s1, ptr %s2) nounwind { ; CHECK-ALIGNED-RV32-LABEL: memcmp_size_4: ; CHECK-ALIGNED-RV32: # %bb.0: # %entry -; CHECK-ALIGNED-RV32-NEXT:addi sp, sp, -16 -; CHECK-ALIGNED-RV32-NEXT:sw ra, 12(sp) # 4-byte

[llvm-branch-commits] [llvm] [SCEV] Add option to request use-specific SCEV for a GEP expr (WIP). (PR #91964)

https://github.com/fhahn updated https://github.com/llvm/llvm-project/pull/91964 >From fc6e2c85ff5dfdbae304cf05368d139096a6bd1f Mon Sep 17 00:00:00 2001 From: Florian Hahn Date: Sun, 12 May 2024 09:57:54 +0100 Subject: [PATCH] [SCEV] Add option to request use-specific SCEV for a GEP expr (WIP).

[llvm-branch-commits] [llvm] [RISCV] Add initial support of memcmp expansion (PR #107548)

@@ -112,42 +104,46 @@ entry: define i32 @bcmp_size_2(ptr %s1, ptr %s2) nounwind optsize { ; CHECK-ALIGNED-RV32-LABEL: bcmp_size_2: ; CHECK-ALIGNED-RV32: # %bb.0: # %entry -; CHECK-ALIGNED-RV32-NEXT:addi sp, sp, -16 -; CHECK-ALIGNED-RV32-NEXT:sw ra, 12(sp) # 4-byte

[llvm-branch-commits] [llvm] [RISCV] Add initial support of memcmp expansion (PR #107548)

@@ -112,42 +104,46 @@ entry: define i32 @bcmp_size_2(ptr %s1, ptr %s2) nounwind optsize { ; CHECK-ALIGNED-RV32-LABEL: bcmp_size_2: ; CHECK-ALIGNED-RV32: # %bb.0: # %entry -; CHECK-ALIGNED-RV32-NEXT:addi sp, sp, -16 -; CHECK-ALIGNED-RV32-NEXT:sw ra, 12(sp) # 4-byte

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

@@ -35971,6 +35971,15 @@ X86TargetLowering::EmitLoweredTLSAddr(MachineInstr &MI, // inside MC, therefore without the two markers shrink-wrapping // may push the prologue/epilogue pass them. const TargetInstrInfo &TII = *Subtarget.getInstrInfo(); + arsenm

[llvm-branch-commits] [libcxx] [libcxxabi] release/19.x: [libc++] Avoid re-exporting a few specific symbols from libc++abi (#109054) (PR #110677)

var-const wrote: @tru Thanks a lot for considering the patch! I just wanted to follow up to close the loop here -- would be awesome to either merge or close this patch, so that we can proceed with fixing our downstream issues according to the resolution. Thanks! https://github.com/llvm/llvm-p

[llvm-branch-commits] [sanitizer] VReport thread status for failed PTRACE_ATTACH (PR #111901)

@@ -148,6 +148,14 @@ bool ThreadSuspender::SuspendThread(tid_t tid) { // Log this event and move on. VReport(1, "Could not attach to thread %zu (errno %d).\n", (uptr)tid, pterrno); +if (common_flags()->verbosity >= 2) { + InternalScopedString path;

[llvm-branch-commits] [sanitizer] VReport thread status for failed PTRACE_ATTACH (PR #111901)

https://github.com/fmayer approved this pull request. https://github.com/llvm/llvm-project/pull/111901 ___ 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] [sanitizer] VReport BeforeFork/AfterFork (PR #111900)

https://github.com/fmayer approved this pull request. https://github.com/llvm/llvm-project/pull/111900 ___ 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] [sanitizer] VReport BeforeFork/AfterFork (PR #111900)

https://github.com/vitalybuka updated https://github.com/llvm/llvm-project/pull/111900 ___ 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] [sanitizer] VReport BeforeFork/AfterFork (PR #111900)

https://github.com/vitalybuka updated https://github.com/llvm/llvm-project/pull/111900 ___ 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] [sanitizer] VReport thread status for failed PTRACE_ATTACH (PR #111901)

https://github.com/vitalybuka updated https://github.com/llvm/llvm-project/pull/111901 ___ 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] [sanitizer] VReport thread status for failed PTRACE_ATTACH (PR #111901)

https://github.com/vitalybuka updated https://github.com/llvm/llvm-project/pull/111901 ___ 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] [clang] Implement TTP P0522 pack matching for deduced function template calls. (PR #111457)

https://github.com/mizvekov updated https://github.com/llvm/llvm-project/pull/111457 >From 6d20ed898e7e96c0e989b37718294a878d87797c Mon Sep 17 00:00:00 2001 From: Matheus Izvekov Date: Sat, 5 Oct 2024 21:56:51 -0300 Subject: [PATCH] [clang] Implement TTP 'reversed' pack matching for deduced fu

[llvm-branch-commits] [clang] [clang] Implement TTP P0522 pack matching for deduced function template calls. (PR #111457)

https://github.com/mizvekov updated https://github.com/llvm/llvm-project/pull/111457 >From e48304b91b42f4aeb1940d34b906242e6e46c8a3 Mon Sep 17 00:00:00 2001 From: Matheus Izvekov Date: Sat, 5 Oct 2024 21:56:51 -0300 Subject: [PATCH] [clang] Implement TTP 'reversed' pack matching for deduced fu

[llvm-branch-commits] [clang] [clang] Implement TTP P0522 pack matching for deduced function template calls. (PR #111457)

https://github.com/mizvekov updated https://github.com/llvm/llvm-project/pull/111457 >From 118ca96aeeb8871a932ed48dd72ea03efa7364e4 Mon Sep 17 00:00:00 2001 From: Matheus Izvekov Date: Sat, 5 Oct 2024 21:56:51 -0300 Subject: [PATCH] [clang] Implement TTP 'reversed' pack matching for deduced fu

[llvm-branch-commits] [clang] [clang] Implement TTP P0522 pack matching for deduced function template calls. (PR #111457)

mizvekov wrote: @zmodem FIY this will fix https://github.com/llvm/llvm-project/pull/96023#issuecomment-2393228464 https://github.com/llvm/llvm-project/pull/111457 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.ll

[llvm-branch-commits] [llvm] [RISCV] Add initial support of memcmp expansion (PR #107548)

wangpc-pp wrote: > > Ping. > > And some updates on vector support: currently, `ExpandMemCmp` will only > > generate integer types (`i128`, `i256` and so on). So, if we simply add > > `128`, `256`, `vlen` to `LoadSizes`, the LLVM IR will use `i128`/`i256`/... > > and then they are expanded to l

<    1   2