x11-themes/mate-themes: switch to GitHub release asset
Minor versions are no longer published to the MATE mirror and are only
available on GitHub. Use USE_GITHUB=nodefault with a release tarball
instead of the auto-generated one, as recommended by the porter's
handbook.
[libc++] Disable mistakenly enabled `optional<T&>` constructors for `optional<T>` (#194446)
Resolves #194415
- A constructor specifically meant for `optional<T&>` was left enabled
for `optional<T>`
- Fix it, and add a test to check for regression.
- This patch also corrects the constraints for `optional(optional<U>&)`
and `optional(const optional<U>&)` , as they were incorrectly
disallowing [valid conversions](https://godbolt.org/z/1r5Ea7z5M)
- Also, correct the `noexcept` specification.
- Add tests for both corrections.
(cherry picked from commit 239189ca28847aa4797368827107c22c32080509)
[LLVM] Fix vprintf modular format with constant format string (#203422)
The vprintf family of functions cannot readily have their arguments
scanned for type, but this isn't an obstacle when the format string is a
known constant. This change only requires argument examination as a
fallback when the format string is unknown.
Generated by Gemini; edited and reviewed by hand.
15.1: Installation note -> Upgrading note
The installation note does not contain installation instructions, and
has not since FreeBSD 6.0. Rename it to the upgrading note to avoid
confusion with the installation guide. Consolidate all release upgrading
information here.
Rewrite the introduction to the release note to separate these out more.
Remove information that is not needed to introduce this release.
The release installation notes do not actually contain instructions on
installing FreeBSD, so rename it to the Upgrading Note.
Reviewed by: carlavilla (previous), cperciva
Discussed with: cperciva, dch, emaste, fuz, michaelo
Co-authored-by: Vladlen Popolitov <vladlen at FreeBSD.org>
Differential Revision: https://reviews.freebsd.org/D57517
devel/sem: Update to 0.11.1
Sem now ships with opt-out telemetry that sends which sem subcommand and
which flags are used. It does not send filename or file contents.
For FreeBSD, I'm changing it to opt-in. While I appreciate that telemetry
contains minimal end-user data, a notice about telemetry is shown only
once and never again. Data are sent to a private, opaque fly.io container.
I find all of the above insufficient.
Discussed with: portmgr (mat)
[libc][math][c23] Implement higher math function `cbrtf16` in LLVM libc (#132484)
This PR implements `cbrtf16` for half precision float (`float16`).
Closes #132199.
---------
Signed-off-by: Krishna Pandey <kpandey81930 at gmail.com>
[lldb] Enforce that ArchDefaultUnwindPlans declare other regs unfetch (#203684)
I noticed a few of the ABI plugins were not setting
UnspecifiedRegistersAreUndefined()==true in their UnwindPlan rows. This
prevents the unwind engine from trying to fetch registers from any newer
stack frames.
The arch default unwind plans are used by lldb when it doesn't have any
accurate information about the registers a function has spilled to
stack, or where -- it only knows enough to continue walking the stack,
assuming all the functions have stored the caller's pc & fp to stack. It
is the last-ditch fallback when we backtrace through no-symbol /
no-unwind info code.
Normally when the unwind engine does not see a non-volatile aka
callee-preserved register mentioned in an UnwindPlan, that means this
function did not save the register to stack, it left the reg contents
unmodified. So if we are looking for x12 in frame 3, and frame 2 doesn't
mention x12 in its UnwindPlan, we will look in frame 1 to see if it
[11 lines not shown]
[mlir][affine] Fix crash in `SplitDelinearizeSpanningLastLinearizeArg` (#201879)
`SplitDelinearizeSpanningLastLinearizeArg` reads the last element of the
source `affine.linearize_index`'s static basis via
`linearizeOp.getStaticBasis().back()` without checking that the basis is
non-empty.
Other canonicalization patterns can legitimately create an
`affine.linearize_index` with no inputs (and therefore an empty basis):
`CancelDelinearizeOfLinearizeDisjointExactTail` peels the matched
trailing
basis off both the linearize and the delinearize, and when every
linearize
input is part of the matched tail the rewritten linearize is left with
no
inputs. When the resulting delinearize is then visited by
`SplitDelinearizeSpanningLastLinearizeArg`, `.back()` is called on an
empty
`ArrayRef`, tripping the `assert(!empty())` in `ArrayRef::back()` (or
[16 lines not shown]
(geography/R-osmdata) Updated 0.2.5 to 0.3.0, fix build against R 4.6.0
# osmdata 0.3.0
## Breaking changes
- Remove `magrittr` from imports. User code relaying on reexported pipe `%>%`
from `osmdata` must explicitly load it with `library(magrittr)`.
Code examples, tests and vignettes now use the pipe from base (`|>`) available since R 4.1 (#361)
- `getbb(..., format_out = "polygon")` return polygons following [https://www.ogc.org/standards/sfa/].
Polygons are defined by a list of matrices of coordinates. The first ring defines the exterior boundary, and the following rings define holes if present.
Also fix `getbb(..., format_out = "sf_polygon")` returning each (multi)polygon as a row in an `sf` object.
Before, every ring was an independent polygon, even for holes or multipolygons,
and for `format_out = "sf_polygon"`, the features were split in a list with polygons in one item and multipolygons in another (#378).
## Major changes
- Implemented `c.osmdata_sc` method to join `osmdata_sc` objects (#333)
- Depends on R >= 4.1 to use the base pipe (`|>`) in examples and vignettes (#371)
[22 lines not shown]
x11-themes/mate-icon-theme: switch to GitHub release asset
Minor versions of 1.28.x are no longer published to the MATE mirror
and are only available on GitHub. Use USE_GITHUB=nodefault with a
release tarball instead of the auto-generated one, as recommended
by the porter's handbook.
[llvm] Add floating point exception status for APFloat's exp function. (#203066)
- Add extra Status return parameter for possible float point exceptions.
- Use `LIBC_NAMESPACE::shared::check::exp_exceptions(x, rm)` to test for
floating point exceptions.
- Change `exp` return type to `std::optional<APFloat>` to avoid
`llvm_unreachable` and be able to tell other callers like clang's
`ExprConstant` about currently unsupported types and rounding modes.
x11-themes/mate-backgrounds: switch to GitHub release asset
Minor versions of 1.28.x are no longer published to the MATE mirror
and are only available on GitHub. Use USE_GITHUB=nodefault with a
release tarball instead of the auto-generated one, as recommended
by the porter's handbook.
x11-fm/caja: switch to GitHub release asset
Minor versions of 1.28.x are no longer published to the MATE mirror
and are only available on GitHub. Use USE_GITHUB=nodefault with a
release tarball instead of the auto-generated one, as recommended
by the porter's handbook.
[lldb] Decouple LLDB_EXPORT_ALL_SYMBOLS from dynamic interpreters (#203997)
With #201392, we generate a minimal export list when LLDB_ENABLE_
DYNAMIC_SCRIPTINTERPRETERS is set. We therefore no longer need to force
LLDB_EXPORT_ALL_SYMBOLS.
This PR makes the two options independent again. LLDB_EXPORT_ALL_SYMBOLS
now defaults to OFF and, when set, is honored regardless of whether the
script interpreters are built as static or dynamic libraries. otherwise,
when disabled, liblldb exports the generated subset if dynamic
interpreters are enabled, otherwise only the public lldb namespace.
[AMDGPU] Guard against opsel selection in V_PK_*64 (#203986)
These instructions do not have OPSEL or ABS so bail on selection.
This does not affect any tests now because v2f64/v2i64 are not legal
for BUILD_VECTOR and alike, but if it is legal it will silently
produce incorrect code. GlobalISel already has this guard.
Be more strict about what names and titles we allow and reject them
immediately when possible, but allow # again for those directly set by
commands (but not escape sequences). From Barrett Ruth in GitHub issue
5175.
[Hexagon] Skip CRT start files for relocatable (-r) links on musl (#201262)
Guard the dynamic-linker, crt1.o, and crti.o additions with OPT_r,
consistent with Gnu.cpp and the existing -pie suppression in this file.
CRT start files must not appear in partial links (-r) as they define
_start, causing duplicate-symbol errors when the output is later linked
into an executable.
[ACCRecipeMaterialization] add tests for private/firstprivate destroy (#203990)
While working on #203935, I noticed that private and firstprivate
recipes with destroy regions were not tested. Add these tests and fix a
bug from the previous commit that would have been caught had these tests
been fixed by generating the destroy region at the correct insertion
point
[AArch64] Add scalable i128 costmodel test coverage. NFC (#203996)
This also adds some basic sub costs, similar to the others, and sorts
the
operations into a more standard order.
[SLP] Fix insert point for insertvalue buildvector with copyable operands
Use the last insertvalue as the insert point (like insertelement) so the
vec2struct store/load are not emitted before the vectorized operand.
Reviewers:
Pull Request: https://github.com/llvm/llvm-project/pull/203994
[docs] Enforce unambiguous toctree in llvm/docs
It seems like using a non-`hidden` `toctree` for page navigation is a
bit of a trap, in that every doc must have a single unique path through
the global toctree to the root doc, and it is very easy to end up with
multiple.
This patch tries to address the warnings (actually infos, hence why it
does not fail the build) in llvm/docs/, namely:
$ sphinx-build -b html -jauto llvm/docs/ /tmp/sphinx-out
checking consistency...
llvm/docs/AMDGPUDwarfExtensionAllowLocationDescriptionOnTheDwarfExpressionStack/AMDGPUDwarfExtensionAllowLocationDescriptionOnTheDwarfExpressionStack.md: document is referenced in multiple toctrees: ['UserGuides', 'AMDGPUUsage'], selecting: UserGuides <- AMDGPUDwarfExtensionAllowLocationDescriptionOnTheDwarfExpressionStack/AMDGPUDwarfExtensionAllowLocationDescriptionOnTheDwarfExpressionStack
llvm/docs/AMDGPUDwarfExtensionsForHeterogeneousDebugging.rst: document is referenced in multiple toctrees: ['UserGuides', 'AMDGPUUsage'], selecting: UserGuides <- AMDGPUDwarfExtensionsForHeterogeneousDebugging
llvm/docs/CommandGuide/llvm-reduce.rst: document is referenced in multiple toctrees: ['CommandGuide/index', 'CommandGuide/index', 'Reference'], selecting: Reference <- CommandGuide/llvm-reduce
llvm/docs/GitHub.rst: document is referenced in multiple toctrees: ['GettingInvolved', 'UserGuides'], selecting: UserGuides <- GitHub
llvm/docs/GlobalISel/IRTranslator.rst: document is referenced in multiple toctrees: ['GlobalISel/index', 'GlobalISel/Pipeline'], selecting: GlobalISel/index <- GlobalISel/IRTranslator
llvm/docs/GlobalISel/InstructionSelect.rst: document is referenced in multiple toctrees: ['GlobalISel/index', 'GlobalISel/Pipeline'], selecting: GlobalISel/index <- GlobalISel/InstructionSelect
llvm/docs/GlobalISel/Legalizer.rst: document is referenced in multiple toctrees: ['GlobalISel/index', 'GlobalISel/Pipeline'], selecting: GlobalISel/index <- GlobalISel/Legalizer
[35 lines not shown]
