[lldb] Add BytecodeSection class to formatter_bytecode.py (#183876)
Changes `formatter_bytecode.compile_file` to return a `BytecodeSection`
value. The `BytecodeSection` holds the data that needs to be emitted to
an `__lldbformatters` section.
The `BytecodeSection` currently provides `write_binary`, but will be
updated in a follow up commit to include `write_source` which will allow
the data to be emitted as C source code, or Swift source code. This will
make it easier to integrate into build systems, as it's easier to get
data into a binary via source code, than as a raw binary file.
Add boot environment based major version upgrade support
Implement full BE-based upgrade flow for major versionupgrades (ABI changes). The new BE is created, mounted, bootstrapped with pkg, then base and software packages are fetched and installed inside it before activating for next boot. Failed upgrades destroy the BE and leave the running system intact.
- Add backend functions: create_be, mount_be, bootstrap_pkg_in_be, fetch/upgrade_base/software_packages_in_be, umount/activate/ cleanup_failed_upgrade_be, get_current_version, get_version, fetch_base_packagelist, get_default_base_repo_url, cleanup_old_backups
- Add be_name and be_mount_path to Data for shared upgrade state
- Refactor InstallUpdate: split process_output into process_popen + process_output, rename read_output to process_upgrade, add major upgrade step methods
- Remove distro dependency, add explicit gi.require_version() calls
- Add .pylintrc configuration
security/clamtk: Update 6.18 => 6.19, take maintainership, switch upstream, improve port
Changelog:
https://github.com/piposeimandi/clamtk/blob/32cc526/CHANGES
Switch upstream to most active fork.
Improve port, fix warnings from portclippy.
Co-authored-by: Vladimir Druzenko <vvd at FreeBSD.org>
NAS-140024 / 26.0.0-BETA.1 / Need to reload systemd after we change a service state. (#18315)
### Problem
After calling service.update <service> '{"enable": true}', running
systemctl status <service> shows:
Warning: The unit file, source configuration file or drop-ins of
<service>.service
changed on disk. Run 'systemctl daemon-reload' to reload units.
### Root Cause
etc_files/systemd.py was previously implemented using systemctl
enable/systemctl disable subprocess calls. These commands create/remove
unit file symlinks and implicitly call daemon-reload to sync systemd's
in-memory state with disk.
The migration to the D-Bus interface replaced those subprocess calls
[15 lines not shown]
devel/reposilite: Update to 3.5.27
* Disable colors in logs and interaction in the daemon
Co-authored-by: Michael Osipov <michaelo at FreeBSD.org>
PR: 293486
bind920: update to BIND version 9.20.20:
Pkgsrc changes:
* Version bump + checksums.
Upstream changes:
Notes for BIND 9.20.20
----------------------
Security Fixes
~~~~~~~~~~~~~~
- Fix a use-after-free error in ``dns_client_resolve()`` triggered by a
DNAME response.
This issue only affected the :iscman:`delv` tool and it has now been
fixed.
[75 lines not shown]
[mlir][spirv] Fix crash when spirv.struct member type is not a SPIR-V type (#183942)
When parsing a spirv.struct type, any MLIR type was accepted as a member
type without validation. This caused a crash in TypeExtensionVisitor and
TypeCapabilityVisitor which unconditionally used cast<SPIRVType> on
struct element types, asserting when a non-SPIR-V type (e.g.,
vector<2x2xi1>) was encountered.
Fix the parser to reject non-SPIR-V member types with a proper error
message.
Fixes #179675
[flang][OpenMP] Fix counting generated nests
The code in `CountGeneratedNests` returned std::nullopt if the LOOPRANGE
clause was not present on a FUSE construct. That is incorrect, the answer
should be 1 instead, except in cases where the FUSE itself was invalid,
such as having no loops nested in it.
Returning std::nullopt will not cause any messages to be emitted. The case
of zero loops inside of FUSE will be diagnosed when analyzing the body of
the FUSE construct itself, not when checking a construct in which the FUSE
is nested.
This prevents error messages caused by the same problem from being emitted
for every enclosing loop construct.
[lldb][Process/FreeBSDKernelCore] Add riscv64 support (#180670)
This is LLDB version of
https://cgit.freebsd.org/ports/tree/devel/gdb/files/kgdb/riscv-fbsd-kern.c.
This enables selecting riscv64 and reading registers from PCB structure
on core dump and live kenrel debugging while trapframe unwinding support
will be implemented in future. Test files using core dump from riscv64
will be implemented once other kernel debugging improvements are done.
---------
Signed-off-by: Minsoo Choo <minsoochoo0122 at proton.me>
[ThinLTO] Reduce the number of renaming due to promotions (#183793)
Currently for thin-lto, the imported static global values (functions,
variables, etc) will be promoted/renamed from e.g., foo() to
foo.llvm.(). Such a renaming caused difficulties in live patching
since function name is changed ([1]).
It is possible that some global value names have to be promoted to avoid
name collision and linker failure. But in practice, majority of name
promotions can be avoided.
In [2], the suggestion is that thin-lto pre-link decides whether
a particular global value needs name promotion or not. If yes, later on
in thinBackend() the name will be promoted.
I compiled a particular linux kernel version (latest bpf-next tree)
and found 1216 global values with suffix .llvm.. With this patch,
the number of promoted functions is 2, 98% reduction from the
original kernel build.
[21 lines not shown]
Add test case for sockets and fifos through null mounts.
I would also add a test case of sending and receiving a datagram, but
nc(1) doesn't seem to have a way to send or receive _one_ datagram;
as far as I can tell, it just loops forever on datagram sockets, with
no stopping point because there's no concept of FIN/shutdown().
PR kern/51963: sockets in chroot sandbox via null-mounts don't work
[SLP]Recalculate dependencies for the buildvector schedule node, if they have copyable node
Need to recalculate the deps for all buildvector nodes with copyable
deps to prevent a compiler crash during scheduling of instructions
[lldb][lldb-server] Fix zip file lookup ignoring last entry in the zip file (#173966)
Command qModuleInfo (GDB server protocol) can be used to request
metadata of shared libraries stored in a ZIP archive on the target. This
is typically used for retrieving SO files bundled in a APK file on
Android.
Requesting the last entry in the ZIP file often fails because of a bug
in the entry search mechanism. This PR fixes this.
NOTES:
* The bug appears only if the entry in the zip file has no extra field
or comment
* This is part on an effort to get lldb working for debugging Swift on
Android: https://github.com/swiftlang/llvm-project/issues/10831
