summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* xspawn: Refactor $PATH resolutionTavian Barnes2024-03-271-81/+240
| | | | | | | | | Technically, we should be resolving executables *after* applying the file actions. It's only safe to resolve earlier if $PATH contains no relative entries, or if there are no fchdir() actions. The new implementation resolves as early as possible, deferring to posix_spawnp() if necessary for correctness.
* xspawn: Implement bfs_spawn_addopen()Tavian Barnes2024-03-272-3/+67
|
* bfstd: Escape ASCII tildesTavian Barnes2024-03-262-1/+3
| | | | | | | | The POSIX spec [1] lists some characters that may need to be escaped. Unfortunately, the document uses ˜ (U+02DC SMALL TILDE) instead of ~ (U+007E TILDE), and I copy-pasted from it. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_02
* xtime: Don't update tm if xtimegm() overflowsTavian Barnes2024-03-262-41/+55
|
* completions: Add -jTavian Barnes2024-03-253-4/+7
|
* trie: Calculate representative indices branchlesslyTavian Barnes2024-03-231-3/+4
|
* bftw: Use a signed integer for dir_limitTavian Barnes2024-03-221-25/+8
|
* Fix some -Wpedantic warningsTavian Barnes2024-03-222-10/+8
|
* bfstd: Add an ASCII fast path to xstrwidth()Tavian Barnes2024-03-211-1/+10
|
* bfstd: New asciilen() functionTavian Barnes2024-03-213-25/+73
|
* bit: Check __BYTE_ORDER__ for the native endianTavian Barnes2024-03-212-2/+15
| | | | __ORDER_NATIVE_ENDIAN__ is not a thing.
* bfstd: Check that wcwidth() is positiveTavian Barnes2024-03-202-2/+9
| | | | | wcwidth() returns -1 for non-printable characters, but terminals typically don't print anything for them, so treat them as 0.
* ioq: Fix some allocation failure pathsTavian Barnes2024-03-201-2/+4
|
* Implement -limit NTavian Barnes2024-03-2015-3/+103
| | | | Closes: https://github.com/tavianator/bfs/issues/133
* ci: Work around https://github.com/actions/runner-images/issues/9491Tavian Barnes2024-03-191-0/+2
| | | | | | Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430 Link: https://github.com/llvm/llvm-project/issues/78354 Link: https://zolutal.github.io/aslrnt/
* config: Don't mix [[attr]] and __attribute__((attr))Tavian Barnes2024-03-191-6/+2
| | | | | GCC and Clang don't support combining the two attribute syntaxes in arbitrary order. For now, just use the GNU style.
* Re-run include-what-you-useTavian Barnes2024-03-1128-32/+33
|
* tests/xtime: Add tests for integer overflowTavian Barnes2024-03-102-1/+31
|
* xtime: Call tzset() from main() instead of lazilyTavian Barnes2024-03-0710-79/+32
| | | | | | | | | | | | | POSIX specifies[1] that If a thread accesses tzname, daylight, or timezone directly while another thread is in a call to tzset(), or to any function that is required or allowed to set timezone information as if by calling tzset(), the behavior is undefined. So calling it lazily from arbitrary threads is risky. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/functions/tzset.html
* tests: Change the timezone for -daystart testsTavian Barnes2024-03-072-2/+2
| | | | | | | Otherwise, if the test files are created just before midnight, and the test runs just after midnight, -daystart will consider them one day old. Fixes #132
* Release 3.1.33.1.3Tavian Barnes2024-03-063-2/+14
|
* ioq: Copy ring_ops from the previous threadTavian Barnes2024-03-061-1/+4
| | | | | | Otherwise threads 2-N won't use io_uring at all! Oops. Fixes: 8bc72d6c ("ioq: Probe for supported io_uring operations")
* eval: Tweak status bar punctuationTavian Barnes2024-03-061-1/+1
|
* tests/ioq: Check that we push and pop the same number of timesTavian Barnes2024-03-021-3/+5
|
* Release 3.1.23.1.2Tavian Barnes2024-02-293-5/+21
|
* tests: New bfs_check() macroTavian Barnes2024-02-296-234/+247
| | | | | We now report failures and continue, rather than aborting after the first failure.
* diag: New bfs_diag() macroTavian Barnes2024-02-292-3/+27
|
* tests: Add more datetime parsing integration testsTavian Barnes2024-02-292-4/+6
|
* xtime: Fix some xgetdate() bugsTavian Barnes2024-02-282-18/+117
| | | | And add some more test cases.
* stat: Use errno_is_like(ENOSYS) for EPERM kludgeTavian Barnes2024-02-282-3/+5
|
* tests/ioq: New unit testTavian Barnes2024-02-284-0/+78
|
* tests/bfs/D_opt: Don't rely on directory link countsTavian Barnes2024-02-282-12/+1
| | | | Fixes: https://github.com/tavianator/bfs/issues/131
* ioq: Probe for supported io_uring operationsTavian Barnes2024-02-281-18/+67
|
* ioq: Remove some branches from ioq_slot_{push,pop}()Tavian Barnes2024-02-181-12/+21
|
* tests: Redirect stdin in bfs_pty()Tavian Barnes2024-02-171-1/+1
| | | | Otherwise bfs will think it's interactive.
* ioq: Ensure ioq_ent is sufficiently alignedTavian Barnes2024-02-162-2/+9
| | | | | | | The natural alignment of struct ioq_ent is only 2 on m68k, so over-align it to at least 4 bytes on all platforms. Link: https://buildd.debian.org/status/fetch.php?pkg=bfs&arch=m68k&ver=3.1-1&stamp=1707699583
* Release 3.1.13.1.1Tavian Barnes2024-02-163-2/+14
|
* ioq: Add batched ioqq_push/pop operationsTavian Barnes2024-02-151-49/+127
|
* ioq: Don't push immediately in ioq_check_cancel()Tavian Barnes2024-02-151-10/+6
|
* ioq: Add a missing close() if bfs_opendir() failsTavian Barnes2024-02-151-0/+2
|
* ioq: Don't use the symbolic IO_WQ_[UN]BOUND indicesTavian Barnes2024-02-141-2/+2
| | | | They are only available since liburing 2.2, which is newer than CI.
* ioq: Factor out io_uring initializationTavian Barnes2024-02-141-37/+73
|
* ioq: Make -j also limit the io_uring worker threadsTavian Barnes2024-02-141-0/+9
|
* ioq: Replay IOQ_STOP messages rather than spam themTavian Barnes2024-02-141-4/+5
|
* ioq: Pack ioq_ent args structsTavian Barnes2024-02-141-3/+3
|
* bftw: Document which bftw_file nodes go with which listsTavian Barnes2024-02-141-3/+17
|
* expr: Pack struct bfs_expr a bitTavian Barnes2024-02-141-15/+9
|
* stat: Pack struct bfs_stat a bitTavian Barnes2024-02-142-28/+24
|
* eval: Add thousands separators to -statusTavian Barnes2024-02-121-2/+2
|
* sanity: Don't use self-init for uninit()Tavian Barnes2024-02-123-7/+7
| | | | | | | | | | | Self-initialization like bool ret = ret; is a GCC trick to suppress uninitialized variable warnings, but it's not actually well-defined, and will trip a recent enough MemorySanitizer: src/eval.c:1088:13: runtime error: load of value 128, which is not a valid value for type 'bool'
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 00:13:31 +0000