[clang][ssaf] Implement TUSummaryBuilder with test infrastructure (#181220)
Also adds a ssaf::TestFixture to provide access to the private fields of
the SSAF object for introspection.
Assisted-By: claude
rdar://168773578
[clang][ssaf] Fix UB caused by missing virtual dtor of FormatInfoEntry (#181838)
In the `llvm::Registry` the `Add` will create a `unique_ptr` of the
desired derived type on the heap; then it puts it into the linked list
of base pointers.
Consequently, when destructing the registry, it needs to call the
matching dtor for the object, so that must be virtual.
In this patch, I fix it by marking it virtual, and also put a static
assert to prevent future mistakes of this kind.
FYI: The static assert must be in dependent context to ensure that `T`
is complete by the time hitting the static assert.
Fixes https://github.com/Quuxplusone/llvm-project/issues/51
x11-toolkits/libadwaita: update 1.7.7 to 1.7.11
Update to 1.7.11 (this version is for Gtk 4.18.x)
=============
Version 1.7.8
=============
- AdwComboRow
- Allow selecting items via touchscreen
- Improve accessibility
- AdwEntryRow
- Fix title ellipsizing too late
- Activate the row action when pressing enter
- AdwNavigationView
- Fix a build warning on some platforms
- AdwTabBar/AdwTabGrid
- Fix context menu alignment on RTL
- Docs
[70 lines not shown]
[Matrix][HLSL] Allow memory layout to change via flags (#181866)
fixes #181859
This also fixes an issue introduced in
https://github.com/llvm/llvm-project/pull/179861
where we were doing the array vector layout in row major as DXC would
define it.
[gsymutil] Verify output string table size and address info offsets do not exceed 32-bit max (#181458)
Previously, https://github.com/llvm/llvm-project/pull/165940 fixed
llvm-dwarfdump and llvm-gsymutil so that they can correctly **consume**
>4GB dSYM. However, if the dSYM is large enough, `llvm-gsymutil` can
still **produce** invalid gSYM.
This change add validation into gsymutil, so that it will fail when the
output string table or address info offsets will exceed 32-bit max.
Similar to https://github.com/llvm/llvm-project/pull/165940, it may be
difficult to auto-test this change. For manual testing, I cannot find a
large enough dSYM for which the gSYM would hit the limits (I have a 9GB
dSYM which produces a 1.7GB gSYM). I'm open to ideas if anyone has any.
php83-baikal: update to 0.11.1.
0.11.1
Fix upgrading when on mysql (by @ByteHamster)
Ships with sabre/dav 4.7.0
0.11.0
Optional CA certificate for MySQL connection via TLS (by @mestrode)
Fix typo in main page title (by @BombFoolGranny)
Upgrade dependencies (by @ByteHamster)
Drop support for php 8.1 ⚠️ you now need at least php 8.2 to run Baïkal
Ships with sabre/dav 4.7.0
NAS-139845 / 26.0.0-BETA.1 / Expand developer PAM-related documentation (#18231)
This commit expands developer documentation for people using the
internal truenas PAM modules for custom applications running on the
truenas host.
stellarsolver: Add version 2.7
- An Astrometric Plate Solver for Mac, Linux, and Windows, built on
Astrometry.net and SEP (sextractor)
- Meant to be an internal library for use in a program like KStars for internal
plate solving on all supported operating systems
- Python is not required for the library
- Netpbm is not required for the library
- Internal Library, so calls to external programs are not required
- No Astrometry.cfg file is needed, the settings are internal to the program
- Directly loads the image data into SEP and then takes the generated xy-list
internally from Sextractor into astrometry.net, so there is no need to save
any files.
- No temporary files need to be created for solving and no WCS file needs to be
created to read the solved information. Although astrometry.net does monitor
for the creation of 2 files indicating that a field is solved or a cancel was
made, so these are created for now.
- The Index Files are still required for solving images, but the program or the
user can specify the folder locations rather than putting them in the config
file.
[lldb] Add test for Swift syntax highligher plugin (#181879)
Check that if tree-sitter support is enabled, the tree-sitter-swift
plugin is used for eLanguageTypeSwift. This part of the test
accidentally got lost during a conflict resolution.
