[Lldb-commits] [clang] [libc] [libcxx] [lldb] [llvm] [doc] Add Discord invite link alongside channel links (PR #126352)

2025-02-13 Thread Alex Bradbury via lldb-commits
https://github.com/asb closed https://github.com/llvm/llvm-project/pull/126352 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [clang] [libc] [libcxx] [lldb] [llvm] [doc] Add Discord invite link alongside channel links (PR #126352)

2025-02-13 Thread Alex Bradbury via lldb-commits
https://github.com/asb updated https://github.com/llvm/llvm-project/pull/126352 >From 446b59bd47eb5356454665eeb82e75a77862350a Mon Sep 17 00:00:00 2001 From: Alex Bradbury Date: Sat, 8 Feb 2025 06:27:26 + Subject: [PATCH 1/2] [doc] Add Discord invite link alongside channel links By far the

[Lldb-commits] [clang] [libc] [libcxx] [lldb] [llvm] [doc] Add Discord invite link alongside channel links (PR #126352)

2025-02-09 Thread Alex Bradbury via lldb-commits
@@ -12,7 +12,8 @@ The LLVM C Library LLVM-libc is not fully complete right now. Some programs may fail to build due to missing functions. If you would like to help us finish LLVM-libc, check out "`Contributing to the libc project `__" in the sidebar - or ask on `discord

[Lldb-commits] [clang] [libc] [libcxx] [lldb] [llvm] [doc] Add Discord invite link alongside channel links (PR #126352)

2025-02-07 Thread Alex Bradbury via lldb-commits
https://github.com/asb edited https://github.com/llvm/llvm-project/pull/126352 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [clang] [libc] [libcxx] [lldb] [llvm] [doc] Add Discord invite link alongside channel links (PR #126352)

2025-02-07 Thread Alex Bradbury via lldb-commits
https://github.com/asb created https://github.com/llvm/llvm-project/pull/126352 By far the most important part of this patch is updating GettingInvolved.rst to include the invite link, but I've grepped for any other discord.com links. I'm no Discord expert, but from my experience (confirmed via

[Lldb-commits] [lldb] [lldb][test] elf-memory.test requires LLDB build with Python support (PR #111810)

2024-10-10 Thread Alex Bradbury via lldb-commits
https://github.com/asb created https://github.com/llvm/llvm-project/pull/111810 Otherwise it fails with "error: Embedded script interpreter unavailable. LLDB was built without scripting language support." >From 2aa842033dd91c7138dc8fe2c61a5f9fdaf2d8c0 Mon Sep 17 00:00:00 2001 From: Alex Bradbur

[Lldb-commits] [lldb] [mlir] [polly] [lld] [libcxx] [flang] [llvm] [clang] [compiler-rt] [openmp] [libc] [WebAssembly] Correctly consider signext/zext arg flags at function declaration (PR #77281)

2024-01-09 Thread Alex Bradbury via lldb-commits
asb wrote: In case anyone was wondering how this is handled in SelectionDAG, I believe it's covered by CallLoweringInfo ultimately determining if an arg is sext/zext through CallBase::paramHasAttr, which does indeed check both the callsite and the called function (if it's a direct call of cour