devel/cpprestsdk: allow consumers to find_package(cpprestsdk)
With sufficiently-new CMake settings, the CMake .config file for
cpprestsdk can't find Boost::system (because it no longer exists)
and then it fails. But cpprestsdk doesn't need it -- so patch
it out.
Upstream PR: https://github.com/microsoft/cpprestsdk/pull/1838
PR: 291874
devfs: add bpf example
Add an example for allowing members of the network group to read from
bpf devices. In particular, this allows members of the network group
to monitor traffic without running with root privileges.
Reviewed by: markj, glebius
Sponsored by: Netflix, Inc.
Differential Revision: https://reviews.freebsd.org/D56742
[VPlan] Set parent early in createReplicateRegion (NFC). (#195156)
Set the parent for a newly create replciate region early after creation.
This brings the region in to a valid state earlier on.
[flang][OpenMP] Implement better GetOmpObjectList, NFC
The current implementation lists all clauses that contain an
OmpObjectList, together with the means of extracting it. For a
clause that is not listed, it returns nullptr.
The new implementation traverses an AST node until it finds an
OmpObjectList, and when one isn't found, returns nullptr. This
is actually simpler and is independent of any changes to the AST.
[NFC][LLDB][Part 2] Support enabling/disabling InstrumentationRuntime plugins in an debug session (#193331)
This patch is the second part in a patch series that will allow
enabling/disabling InstrumentationRuntime plugins in a running debug
session.
This patch contains a set of NFC changes that will be needed when
implementing support for enabling/disabling InstrumentationRuntime
plugins in the `debugger` and `target` domains.
In particular
* In several places the `PluginManager` was modified to get access to
information about disabled plugins. Previously interfaces would only
return information about enabled plugins.
* `InstrumentationRuntimeInstances` is now struct rather than a typedef
so it can contain a helper method that allows looking up a
`InstrumentationRuntimeGetType` callback based on the plugin name. This
is very similar to the existing `PluginsInstances::GetCallbackForName`
[2 lines not shown]
[LLDB][Part 1] Support enabling/disabling InstrumentationRuntime plugins in an debug session (#193328)
This patch is the first part in a patch series that will allow
enabling/disabling InstrumentationRuntime plugins in a running debug
session.
This part adds the `--domain` flag to the `enable`, `disable`, `list`
sub commands of `plugin` shell command and plumbs the value of this flag
to where it will be needed in a subsequent patch. From the user
perspective the flag does nothing useful yet because all values passed
to the flag except `global` (the default and what represents LLDB's
existing behavior) are rejected. Subsequent patches will allow the flag
to do something useful.
The `--domain` flag adds a notion of "domain" to plugins with respect to
their enablement. Previously all plugins were treated as global and have
their enablement stored globally. This is despite the fact that some
plugins clearly are not global. For example the
`instrumentation-runtime` plugins clearly exist on a per-target basis
[74 lines not shown]
devel/ctags-lsp: Add port
This is an LSP that uses universal-ctags, making it both
language-agnostic and compatible with the vast array of languages
that uctags can parse.
However, that also means that it's limited to the data in a tags file,
meaning things like tracking references is off the table. But, it is,
as the author notes, "better than nothing."
Instructions for enabling the LSP in Neovim and Helix can be found
at the WWW: https://github.com/netmute/ctags-lsp
Revert "[dsymutil] Fix ODR type uniquing for -gsimple-template-names" (#195162)
Reverts llvm/llvm-project#194501 as this is triggering an assert in CI:
```
Assertion failed: ((!HasTemplateParamsInName || Tag != dwarf::DW_TAG_subprogram) && "subprogram with template-like name should have a linkage name"), function getChildDeclContext, file DWARFLinkerDeclContext.cpp, line 114.
```
Document __FreeBSD_version bumps: 1600018 + 1500505-1500509
I only authored the bumps to 1600018 and 1500509, not the previous ones.
Hopefully the description of these previous bumps is accurate.
Sponsored by: The FreeBSD Foundation
