[Lldb-commits] [lldb] [lldb][FreeBSD] Add dynamic loader handle class for FreeBSD Kernel (PR #67106)

@@ -0,0 +1,770 @@ +#include "lldb/Breakpoint/StoppointCallbackContext.h" +#include "lldb/Core/Debugger.h" +#include "lldb/Core/Module.h" +#include "lldb/Core/ModuleSpec.h" +#include "lldb/Core/PluginManager.h" +#include "lldb/Core/Section.h" +#include "lldb/Core/StreamFile.h" +#in

[Lldb-commits] [lldb] [lldb][DWARFASTParserClang] Resolve nested types when parsing structures (PR #66879)

clayborg wrote: > > I didn't see much explanation as to why this is needed in the bug report. > > The motivating example is something like: > > ``` > struct Info { > enum Mask : uintptr_t { > Enum > }; > } > ``` > > `expr Info::Mask::Enum`. > > > Is there a reason we need to complete

[Lldb-commits] [lldb] 3f0bddb - Use llvm::find (NFC)

Author: Kazu Hirata Date: 2023-09-23T16:27:02-07:00 New Revision: 3f0bddb56ac33389e0a02444c6f67c7a42855582 URL: https://github.com/llvm/llvm-project/commit/3f0bddb56ac33389e0a02444c6f67c7a42855582 DIFF: https://github.com/llvm/llvm-project/commit/3f0bddb56ac33389e0a02444c6f67c7a42855582.diff L

[Lldb-commits] [lldb] [libc++] Implement ranges::contains_subrange (PR #66963)

https://github.com/huixie90 edited https://github.com/llvm/llvm-project/pull/66963 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [libc++] Implement ranges::contains_subrange (PR #66963)

https://github.com/huixie90 edited https://github.com/llvm/llvm-project/pull/66963 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [libc++] Implement ranges::contains_subrange (PR #66963)

@@ -0,0 +1,145 @@ +//===--===// +// +// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions. +// See https://llvm.org/LICENSE.txt for license information. +// SPDX-License-Identifier: Apa

[Lldb-commits] [lldb] [libc++] Implement ranges::contains_subrange (PR #66963)

@@ -0,0 +1,145 @@ +//===--===// +// +// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions. +// See https://llvm.org/LICENSE.txt for license information. +// SPDX-License-Identifier: Apa

[Lldb-commits] [lldb] [libc++] Implement ranges::contains_subrange (PR #66963)

https://github.com/huixie90 requested changes to this pull request. Thank you for contributing! I have not looked at the tests yet. Please let me know if my comments on the header file is unclear. Thank you! https://github.com/llvm/llvm-project/pull/66963 ___

[Lldb-commits] [lldb] [llvm][tblgen] Add `SourcePath` for `emitSourceFileHeader` (PR #65744)

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 b8b4ee6b450766796b162b4811a6b3f723d07268 d07486764071679c8cbcd5e7c4905eb41b4770b3 --

[Lldb-commits] [lldb] [llvm][tblgen] Add `SourcePath` for `emitSourceFileHeader` (PR #65744)

llvmbot wrote: @llvm/pr-subscribers-mlir-llvm Changes I think this is very helpful for reading generated `.inc` files. --- Patch is 31.85 KiB, truncated to 20.00 KiB below, full version: https://github.com/llvm/llvm-project/pull/65744.diff 22 Files Affected: - (modified) clang/utils/T

[Lldb-commits] [lldb] [llvm][tblgen] Add `SourcePath` for `emitSourceFileHeader` (PR #65744)

https://github.com/sunshaoce updated https://github.com/llvm/llvm-project/pull/65744 >From 23d0b738bf40ea44e159f4f8d7355d4d6bc0688d Mon Sep 17 00:00:00 2001 From: Shao-Ce SUN Date: Sat, 23 Sep 2023 11:38:33 +0800 Subject: [PATCH 1/2] [llvm][tblgen] Add `SourcePath` for `emitSourceFileHeader`

[Lldb-commits] [lldb] [lldb][DWARFASTParserClang] Resolve nested types when parsing structures (PR #66879)

Michael137 wrote: > I didn't see much explanation as to why this is needed in the bug report. The motivating example is something like: ``` struct Info { enum Mask : uintptr_t { Enum }; } ``` `expr Info::Mask::Enum`. > Is there a reason we need to complete nested types within a type?