/bin/sh option list, don't include dotglob in SMALL shells
dotglob is only (currently) used for file completion via libedit.
None of that is included in SMALL shells, so the new dotglob option
is pointless there (just occupies space), just exclude it.
gotosocial: upstream/codeberg version tracking enhancement
Functionnal and cosmetic change. This WIP package should be held back until next gotosocial upstream update.
Add a codeberg tag tracking variable in the Makefile, like many packages pulled from Github for consistency,
easier upstream version changes tracking, and make this package maintenance easier too.
- pkglint
- build using pkgsrc-trunk and bob
- deployed in production
Only match "." and ".." if the filename is non-empty & starts with '.',
regardless of the state of MATCH_HIDDEN_FILES. That's the way bash
actually works, and makes sense.
Also, while here, don't allow calling the completion function to
alter the "match_hidden_files" setting set by EL_MATCH_HIDDEN_FILES
(or not permanently, only for the current match process).
Also, have fn_complete() call fn_complete2() using MATCH_HIDDEN_FILES
if EL_MATCH_HIDDEN_FILES has been set. This gives some purpose to
the global setting, which was otherwise doing nothing at all.
And make the default be to match hidden files (the way libedit used to
work) which seems likely to have been the intent.
[CIR] Mark bit-field access units as their own member kinds
A bit-field access unit is as wide as the compiler decides, which can be
narrower than the declared type of the bit-fields in it, and the member marks
say nothing about that: a unit with a named occupant is `data` and one with only
unnamed occupants is `empty`, the same marks a declared field gets. So a member
holding a 32-bit bit-field of `long long` looks exactly like an `unsigned`
field, and the two are not the same to the ABI. `BitsContainNoUserData`
recurses on the declared type, finds user data past bit 32 in the first and none
in the second, and classic CodeGen coerces the enclosing records to `i64` and
`i32`.
Split the unit cases out as `bitfield` and `empty_bitfield`. A unit holds data
exactly when a named bit-field lands in it, so `isEmptyForABI` answers the same
for every record once it asks `holdsDataForABI` instead of testing for `data`
alone, and padding is untouched. Nothing classifies on the new marks yet, so no
ABI treatment changes. What needs them is pad-aware eightbyte classification,
which cannot tell a record's declared extents from its access units without
them.
[2 lines not shown]
yazi: update to 26.8.15.
Added
Drag and drop (#4005, #4225)
Trash bin (#4144, #4204, #4212)
Bulk create (#3793)
Make help menu a command palette (#4074)
Input history (#4104)
Automatic dark/light theme switching (#4196)
Experimental %y, %Y, %t, %T, %yN, %YN, %tN, %TN shell formatting parameters (#4108)
Custom VFS provider (#4118)
Make visual mode support wraparound scrolling (#4101)
H/M/L Vim-like motion for moving cursor relative to viewport (#3970)
Context-aware icons for inputs (#4080)
Show file icons in trash/delete/overwrite confirmations (#4096)
Dynamic keymap Lua API (#4031)
Dynamic Lua API for preloader, spotter, fetcher (#4235)
Configurable border for the which component (#4189)
[42 lines not shown]
[APFloat][SelectionDAG] Support Float8E5M3FNU in convert.{to,from}.arbitrary.fp
Float8E5M3FNU was already accepted by the IR verifier, because
isValidArbitraryFPFormat is defined in terms of
getArbitraryFPFormatSizeInBits and that table covers it. It was missing
from getArbitraryFPSemantics, so SelectionDAGBuilder rejected
it with "not implemented format" and the verifier-clean IR failed to
compile. Add the mapping and the corresponding entries in the
expandCONVERT_{TO,FROM}_ARBITRARY_FP format allowlists.
Unlike every other format the expansions handle so far, Float8E5M3FNU is
unsigned: it has no sign bit, so all 8 bits go to a 5-bit exponent and a
3-bit significand.
Since an unsigned format cannot represent a negative value, a negative
input now saturates to zero when the saturate flag is set, and is poison
otherwise. -0.0 is excluded from that and still converts to +0, and the
check is ordered before the NaN case so a negative NaN still produces the
NaN encoding. APFloat treats constructing a negative value in an unsigned
[3 lines not shown]
[APFloat][NFC] Add unit test coverage for getArbitraryFPSemantics
isValidArbitraryFPFormat and getArbitraryFPFormatSizeInBits have unit
tests, but getArbitraryFPSemantics, the mapping the conversion
intrinsics actually lower through, had none. Cover the formats it
supports, the valid formats it does not support yet, and invalid format
strings, and check that the two tables agree on the size of every
format with lowerable semantics.
Also add the missing Float8E5M3FNU case to the
getArbitraryFPFormatSizeInBits test.
Change-Id: I8fa9580ca6f03fd5e7b1de5354b71283cebb0f95
linuxkpi: Include <linux/page-flags.h> from <linux/mm.h>
This reproduces the same namespace pollution as Linux.
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D58761
linuxkpi: Create empty <linux/sprintf.h>
The DRM drivers generic code started to include this header in Linux
6.15, though nothing from it is used apparently.
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D58253
linuxkpi: Fix return type of `kobject_uevent_env()`
The function returns an int on Linux. Let's return 0 (success).
Sponsored by: The FreeBSD Foundation
Differential Revision: reviews.freebsd.org/D58252
linuxkpi: Define `PCI_CLASS_BRIDGE_HOST`
The i915 DRM driver started to use it in Linux 6.15.
Sponsored by: The FreeBSD Foundation
Differential Revision: reviews.freebsd.org/D58250
linuxkpi: Add `kunit_fail_current_test()`
This is part of some unit testing framework.
The DRM drivers generic code started to use it in Linux 6.15.
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D58249
compiledb-go: update to 1.7.0.
feat: update existing compilation database by @fcying in #14
fix: merge legacy compilation database paths by @fcying in #15
refactor: harden command parsing and make wrapping by @fcying in #16
feat: add compiler argument option by @fcying in #17
feat: add predefined compiler macros by @fcying in #18
fix: record source commands without -c by @fcying in #19
fix: align Python compatibility details by @fcying in #20
dev by @fcying in #21
fix: harden compiler command detection by @fcying in #22
feat: improve make integration by @fcying in #23
feat: embed POSIX shell interpreter by @fcying in #24
feat: improve platform compatibility by @fcying in #25
refactor: clarify path handling domains by @fcying in #26
test: add build log memory benchmarks by @fcying in #27
refactor: parse shell commands with AST by @fcying in #28
feat: expand GNU compiler response files by @fcying in #29
fix: track recursive Make directories by @fcying in #31
docs: rewrite README by @fcying in #32
linuxkpi: Define `__GFP_HIGH` in <linux/gfp.h>
The DRM drivers TTM memory manager started to use it in Linux 6.15.
Reviewed by: emaste
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D58760
linuxkpi: Include <linux/notifier.h> and <linux/device.h> from <linux/pm_qos.h>
The i915 DRM driver started to depend on the `bool` type implicitly
imported through these headers in Linux 6.13.
The previous fix committed in 67df313015906d84d90df8e37795885e81cf8da5
did not reproduce the same includes as Linux. This may have led to other
missing implicit definitions later.
To prevent another missing include in the future, we already include
<linux/plist.h> from <linux/pm_qos.h> and add it as a dummy header. This
will be easier to add a proper implementation in the future once we
actually need it.
Reviewed by: bz, emaste
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D57570
