misc/far2l: update the port to version 2.7.0 (step over)
- Removed PCRE library dependency (was used by multiarc plugin)
- New hex editor plugin (ported from Far3) + preliminary support
for viewing and editing UTF-8 characters
- Do not try to compile find_plt_entry_for_symbol() and commented
out patch_plt() functions as it is currently 64-bit-only, Linux-
specific code which parses hardcoded `/proc/self/maps' file
- Provide separate icons for WX versions of far2l and far2ledit
- Drop the list of working plugins in the port description which
is becoming hard to keep accurate as the project develops
Reported by: portscout
NAS-138657 / 26.04 / Properly handle the temporarily disabled remote controller audit export. (#17686)
We've temporarily disabled the ability to export the remote controller
audit database.
This PR updates the associated CI test.
NAS-138650 / 26.04 / Fix docstring in SMB share docs (#17682)
This commit fixes a merge that didn't include the now mandatory
continuation character for the python docstring for an API field.
[NFC][LLDB] Make it possible to detect if the compiler used in tests supports -fbounds-safety (#169112)
This patch makes it possible to detect in LLDB shell and API tests if
`-fbounds-safety` is supported by the compiler used for testing. The
motivation behind this is to allow upstreaming
https://github.com/swiftlang/llvm-project/pull/11835 but with the tests
disabled in upstream because the full implementation of -fbounds-safety
isn't available in Clang yet.
For shell tests when -fbounds-safety is available the
`clang-bounds-safety` feature is available which means tests can be
annotated with `# REQUIRES: clang-bounds-safety`.
API tests that need -fbounds-safety support in the compiler can use the
new `@skipUnlessBoundsSafety` decorator.
rdar://165225507
[lld:MachO] Allow independent override of weak symbols aliased via .set (#167825)
Currently, if multiple external weak symbols are defined at the same
address in an object file (e.g., by using the .set assembler directive
to alias them to a single weak variable), ld64.lld treats them as a
single unit. When any one of these symbols is overridden by a strong
definition, all of the original weak symbols resolve to the strong
definition.
This patch changes the behavior in `transplantSymbolsAtOffset`. When a
weak symbol is being replaced by a strong one, only non-external (local)
symbols at the same offset are moved to the new symbol's section. Other
*external* symbols are no longer transplanted.
This allows each external weak symbol to be overridden independently.
This behavior is consistent with Apple's ld-classic, but diverges from
ld-prime in one case, as noted on
https://github.com/llvm/llvm-project/issues/167262 (this discrepancy has
recently been reported to Apple).
[18 lines not shown]
[CI] Make Premerge only Comment if Tests Failed (#169102)
Before, we were unconditionally writing a message. After this patch, we
only write a message when the tests failed, or there is already an
existing comment. This is how this workflow was intended to work
originally, but is not how it ended up working, mostly due to my
misconceptions around how the existing code formatter pass handled this
case (we need to actually not write out any comments, not write out a
specific message).
