man: Link mgb.4 to if_mgb.4
For consistency, create a symbolic link from mgb.4 to also
if_mgb.4
Reviewed by: #manpages, ziaee, emaste
Differential Revision: https://reviews.freebsd.org/D60551
MFC after: 3 days
man: Link mgb.4 to if_mgb.4
For consistency, create a symbolic link from mgb.4 to also
if_mgb.4
Reviewed by: #manpages, ziaee, emaste
Differential Revision: https://reviews.freebsd.org/D60551
MFC after: 3 days
[orc-rt] Add SymbolLookupSet-based lookup to SimpleSymbolTable (#230761)
SimpleSymbolTable::lookup(const SymbolLookupSet&) looks up the given
linker-level names in the table and returns a SymbolLookupResult with
one entry per element of the set, in the same order. Missing
weakly-referenced symbols are reported as null addresses; missing
required symbols are reported as empty optionals, matching
NativeDylibManager::lookup.
graphics/appleseed: prepare the port for upcoming CMake versions
Rewrite the build logic to not rely on obsolete policies CMP0026
and CMP0043. While at it, limit two macros' action to an active
CMAKE_BUILD_TYPE by removing needless set_property(...) calls.
graphics/appleseed: prepare the port for upcoming CMake versions
Rewrite the build logic to not rely on obsolete policies CMP0026
and CMP0043. While at it, limit two macros' action to an active
CMAKE_BUILD_TYPE by removing needless set_property(...) calls.
Reapply "[clang-repl] Fix crashing on unusable top-level declarations" (#230054) (#230742)
Drop the previously failing test lines:
```c
printf("not crashed\n");
// CHECK-NEXT: not crashed
```
A bare `return;` is sufficient for detecting the regression.
Reverts #230734.
[MLIR][CAPI][Python] Add C API and Python bindings for the remark engine (#229094)
Expose the optimization remark engine (`mlir/IR/Remarks.h`) through the
C API and the Python bindings, so clients outside C++ can enable it,
receive the reported remarks and emit their own.
### C API (`mlir-c/Remarks.h`)
- `mlirContextEnableOptimizationRemarks{,ToFile,WithCallback}` select
the categories (one regex per kind plus `all`), the emitting policy
(`all` or `final`) and the sink: MLIR remark diagnostics, a
YAML/bitstream file, or a callback invoked with an opaque `MlirRemark`.
- `mlirContextFinalizeOptimizationRemarks` flushes postponed remarks,
writes the file and drops the engine; `mlirContextHasRemarkEngine`
queries it.
- `MlirRemark` accessors (kind, remark/category/function names,
location, id, key/value arguments, print), valid for the duration of the
callback.
- `mlirEmitOptimizationRemark` emits a remark at a location through the
engine of its context.
[24 lines not shown]
ibus-hangul: updated to 1.5.5
1.5.5
Change default dist file format to xz
xz file format is much smaller than gz.
Update the rule to generate the ChangeLog
In order to generate the ChangeLog during out-of-tree builds,
$(top_srcdir) is used.
libhangul: updated to 0.2.0
0.2.0
Load both builtin and external keyboards
Previously, external keyboards replaced builtin ones, which caused
problems when external files were missing. Now both are loaded to
ensure better fallback.
Note: This results in duplicate entries for identical layouts.
[LAA] Add tests for a set of miscompiles. (NFC) (#230773)
Add tests for the following issues:
* interleaved-accesses-retry-runtime-checks.ll: when LAA retries with
runtime checks, the store of an interleave group is moved past a load
from the same address.
* is-safe-dep-distance-narrow-btc.ll: accesses with a real backward
dependence are reported as safe if the byte stride does not fit in a
narrow backedge-taken count type or MaxBTC * MaxStride wraps in it.
* is-safe-dep-distance-partial-overlap.ll: accesses are reported as
independent if |Dist| > MaxBTC * MaxStride, even if the distance is not
a multiple of the access size and the accesses partially overlap.
* different-access-types-rt-checks.ll: the runtime check bounds of a
pointer loaded as i32 and stored as i8 only account for the i8 store, so
the tail of the loaded range is not checked.
* runtime-check-grouping-wrapping-bounds.ll: pointers whose bounds can
wrap relative to each other are grouped, so the group's Low can be above
its High and the runtime checks never detect a conflict.
[VPlan] Re-use LCSSA phis when expanding AddRecs of other loops. (#230772)
Don't re-use IR values defined in loops that do not contain the plan's
entry in VPSCEVExpander::tryToReuseIRValue, as such uses outside the
loop break LCSSA. Instead, match SCEVExpander behavior and re-use an
existing LCSSA phi, reusing SCEVExpander::findReusableLCSSAPhi.
Pull up following revision(s) (requested by tls in ticket #516):
tools/Makefile.gnuhost: revision 1.58
build.sh: revision 1.406
Protect against autoconf/Xcode mishegas on macOS.
This seems to strike periodically, confuse a developer or two for a little
while, and then go away. Why? Because it happens in the interval between
Apple issuing a version of Xcode that supports a newer OS, and newer APIs,
and a given developer's system being upgraded (Apple typically ships Xcode
supporting a new version of macOS a little prior to the OS itself).
The symptom is that autoconf detects symbols that are weakly available with
the new Xcode but which will cause built executables to dump core if called
on the old host OS. This is evidently being addressed in newer versions of
autoconf but who knows when we'll get those across our tree. The fix is to
tell Xcode to use an older SDK if the potential for this condition is detected.
Pull up following revision(s) (requested by tls in ticket #516):
tools/Makefile.gnuhost: revision 1.58
build.sh: revision 1.406
Protect against autoconf/Xcode mishegas on macOS.
This seems to strike periodically, confuse a developer or two for a little
while, and then go away. Why? Because it happens in the interval between
Apple issuing a version of Xcode that supports a newer OS, and newer APIs,
and a given developer's system being upgraded (Apple typically ships Xcode
supporting a new version of macOS a little prior to the OS itself).
The symptom is that autoconf detects symbols that are weakly available with
the new Xcode but which will cause built executables to dump core if called
on the old host OS. This is evidently being addressed in newer versions of
autoconf but who knows when we'll get those across our tree. The fix is to
tell Xcode to use an older SDK if the potential for this condition is detected.
