aboutsummaryrefslogtreecommitdiff
path: root/core
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #3725 from laytan/add-forced-shutdown-to-test-runnergingerBill2024-06-101-1/+8
|\ | | | | add forced shutdown to new test runner
| * add forced shutdown to new test runnerLaytan Laats2024-06-101-1/+8
| | | | | | | | | | | | | | | | Currently, a Ctrl+c starts a graceful shutdown of the tests and runner. Sometimes tests get stuck and this would never complete. This simply adds an extra step, if Ctrl+c is given for the second time, just `os.exit` right away.
* | Fix #3726gingerBill2024-06-101-3/+3
| |
* | Improve parsing for `label: #reverse for` and `label: #partial switch`gingerBill2024-06-101-1/+36
| |
* | Merge pull request #3718 from Feoramund/add-missing-big-atoi-aliasJeroen van Rijn2024-06-101-0/+1
|\ \ | | | | | | Add missing `string_to_int` alias in `core:math/big`
| * | Add missing `string_to_int` alias in `core:math/big`Feoramund2024-06-091-0/+1
| | |
* | | Add permutation & combination procedures to `core:math/big`Feoramund2024-06-091-0/+60
|/ /
* / Add `slice.permute`Feoramund2024-06-091-0/+105
|/
* Clean up PNG code.Jeroen van Rijn2024-06-091-26/+20
|
* Merge branch 'master' into png_cleanupJeroen van Rijn2024-06-093-0/+930
|\
| * Merge branch 'master' into tlsf-allocatorJeroen van Rijn2024-06-0926-54/+1020
| |\
| * | Add `core:mem` tests.Jeroen van Rijn2024-06-061-8/+6
| | |
| * | Fix `fls_uint`Jeroen van Rijn2024-06-061-4/+8
| | |
| * | Add original LICENSEJeroen van Rijn2024-06-061-0/+36
| | |
| * | Change to `init` from `create`gingerBill2024-06-052-30/+30
| | |
| * | `core:mem/tlsf` - "Two-Level Segregated Fit" memory allocatorgingerBill2024-06-052-0/+892
| | |
* | | Use new blend helperJeroen van Rijn2024-06-092-28/+41
| | |
* | | Image: Add improved blending method and test it.Jeroen van Rijn2024-06-092-11/+26
| |/ |/|
* | Update dir_windows.odinJeroen van Rijn2024-06-081-2/+2
| |
* | Fixed error handling in read_dir on WindowsJohn Leidegren2024-06-081-1/+5
| |
* | Fix `%p` pointers not printing leading `0x`Feoramund2024-06-071-1/+1
| |
* | core/thread: fix a deadlock situation on unixLaytan Laats2024-06-071-11/+12
| |
* | core/sync: fix wrong timeout calculation, `time.Duration` is ns alreadyLaytan Laats2024-06-071-1/+1
| |
* | add MacOS 14.5 to 'core:sys/info' and 'odin report'Laytan Laats2024-06-071-0/+1
| |
* | add error message for unknown test log levelLaytan Laats2024-06-071-0/+3
| | | | | | | | | | It would previously just be a compilation error about a missing return statement.
* | Add saving of 24 and 32-bit images to BMP format.Jeroen van Rijn2024-06-062-1/+110
| |
* | Rebased.Jeroen van Rijn2024-06-064-0/+801
| |
* | Add `@(rodata)` and `@(static, rodata)` where appropriategingerBill2024-06-0612-30/+41
| |
* | Merge pull request #3690 from laytan/orcasgingerBill2024-06-062-0/+25
|\ \ | | | | | | Runtime support for orca
| * | improve orca targetLaytan Laats2024-06-052-0/+25
| |/
* | Merge pull request #3675 from Feoramund/fix-partial-infinitygingerBill2024-06-051-6/+9
|\ \ | | | | | | Fix partial parsing of `infinity`
| * | Permit parsing of incomplete `infinity` but do not return trueFeoramund2024-06-041-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | To clarify, `parse_f64` will indeed take `infi` to mean `+Inf` and return that as the value, but it will not return `ok = true`. It treats it as `inf` followed by any other trailing character. `parse_f64_prefix` is the lenient one which will return true so long as it finds some meaningful value.
| * | Fix partial parsing of "infinity" in `parse_f64_prefix`Feoramund2024-06-041-6/+3
| | | | | | | | | | | | | | | It was previously reporting an invalid number of characters parsed for any string other than "inf", "+inf", or "-inf".
* | | Merge pull request #3681 from andreas-jonsson/netbsd-lwp-selfgingerBill2024-06-052-4/+12
|\ \ \ | |_|/ |/| | Proper thread identification on NetBSD
| * | Fixed broken importAndreas T Jonsson2024-06-051-1/+0
| | |
| * | Propper thread identification on NetBSDAndreas T Jonsson2024-06-052-3/+12
| | |
* | | Merge pull request #3679 from Feoramund/fix-typosJeroen van Rijn2024-06-052-1/+1
|\ \ \ | |/ / |/| | Fix some typos
| * | Fix some typosFeoramund2024-06-042-1/+1
| |/
* | Merge pull request #3678 from Feoramund/fix-p-f64-p-docJeroen van Rijn2024-06-051-1/+5
|\ \ | | | | | | Strike incorrect note from `parse_f64_prefix` doc
| * | Strike incorrect note from `parse_f64_prefix` docFeoramund2024-06-041-1/+5
| |/
* / Add `parse_complex/quaternion*` to `core:strconv`Feoramund2024-06-041-0/+269
|/
* Merge branch 'master' into fix-fmt-compquat-signJeroen van Rijn2024-06-0436-593/+2379
|\
| * Merge pull request #3646 from Feoramund/multi-testJeroen van Rijn2024-06-0435-592/+2378
| |\ | | | | | | Refactor the test runner
| | * Fix ad hoc `printf` in test runner signal handlerFeoramund2024-06-021-1/+1
| | |
| | * Use `Warning` log level for reporting memory leaksFeoramund2024-06-021-2/+4
| | | | | | | | | | | | Works well with `-define:ODIN_TEST_LOG_LEVEL=warning`.
| | * Prevent test runner deadlock on NetBSDFeoramund2024-06-022-0/+14
| | | | | | | | | | | | Add `pthread_testcancel` to `core:sys/unix`
| | * Fix wrong `PTHREAD_CANCEL_ASYNCHRONOUS` on FreeBSD and OpenBSDFeoramund2024-06-022-4/+4
| | | | | | | | | | | | | | | | | | | | | The test runner was deadlocking when a test raised a signal on FreeBSD. This is untested on OpenBSD, but I have referenced this file: https://github.com/openbsd/src/blob/master/include/pthread.h
| | * Fix `STDIN`, `STDOUT`, `STDERR` handles for BSDsFeoramund2024-06-021-6/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tested on FreeBSD 14.0 and NetBSD 10.0 OpenBSD is untested, but link names were sourced from: https://github.com/openbsd/src/blob/master/include/stdio.h According to this, OpenBSD shares the same layout as NetBSD. FreeBSD has the same as Darwin in this regard.
| | * Be pedantic about not overwriting Odin errorsFeoramund2024-06-021-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I was encountering bounds-check error messages being overwritten during a test, if the test failed for another reason and sent a log message. The original intent of having this check inside of the above `if` block was that if a test sent an error message, then it was assumed an overwrite would be safe, but it's completely possible for a test to fail for a legitimate reason, then do an unrelated bounds check somewhere else that would be buried under the animation. This change will make sure that, no matter what, the progress display will not trigger a clear if a signal was raised. There's still no guarantee that bounds-check messages will be printed properly, and it's best to redirect STDERR. The only way that can be fixed is if they get a similar hook to `context.assertion_failure_proc`.
| | * Tell user about `ODIN_TEST_RANDOM_SEED` optionFeoramund2024-06-021-1/+5
| | |