| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
to bucket and free fiber allocations
|
|
1. a fiber can't put itself on a queue that allows it to be rescheduled
2. allow the idle fiber to unlock a mutex held by another fiber by
ignoring reschedule requests originating from the idle fiber
|
|
|
|
|
|
and no timer
|
|
|
|
data races on deinit tho
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
How silly of me to forget that the kernel doesn't implement its own API.
The scheduling is not great, but at least doesn't deadlock or hammer.
|
|
Something is horribly wrong with scheduling, as can be seen in the
debug output, but at least it somehow manages to exit cleanly...
|
|
|
|
|
|
|
|
This avoids needing to store more sizes and alignments. Only the result
alignment needs to be stored, because `Fiber` is at a fixed zero offset.
|
|
When the previous fiber did not request to be registered as an awaiter,
it may not have actually been a full blown `Fiber`, so only create the
`Fiber` pointer when needed.
|
|
sorry, something still not working correctly
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
which is planned to have all I/O operations in the interface, but for
now has only async and await.
|
|
Document that `remove` of Singly/DoublyLinkedList relies on the node being in the list
|
|
|
|
|
|
|
|
The logic for computing reference traces was unintentionally finding the
*longest* possible trace (approximately). I think I already tried to fix
this before, but misunderstood how my own code works. Here, we fix it
properly: by slightly reworking the logic to use one ArrayHashMap for
both the result and the traversal queue, we trivially get a proper
breadth-first traversal so that we can find the shortest possible
reference trace for every referenced unit.
|
|
Fixed a relatively small outdated doc string, referring to the bucket linked list.
|
|
|
|
feat: init x86_16 arch via CBE
|
|
Co-authored-by: Alex Rønne Petersen <alex@alexrp.com>
|
|
There is no straightforward way for the Zig team to access the Solaris system
headers; to do this, one has to create an Oracle account, accept their EULA to
download the installer ISO, and finally install it on a machine or VM. We do not
have to jump through hoops like this for any other OS that we support, and no
one on the team has expressed willingness to do it.
As a result, we cannot audit any Solaris contributions to std.c or other
similarly sensitive parts of the standard library. The best we would be able to
do is assume that Solaris and illumos are 100% compatible with no way to verify
that assumption. But at that point, the solaris and illumos OS tags would be
functionally identical anyway.
For Solaris especially, any contributions that involve APIs introduced after the
OS was made closed-source would also be inherently more risky than equivalent
contributions for other proprietary OSs due to the case of Google LLC v. Oracle
America, Inc., wherein Oracle clearly demonstrated its willingness to pursue
legal action against entities that merely copy API declarations.
Finally, Oracle laid off most of the Solaris team in 2017; the OS has been in
maintenance mode since, presumably to be retired completely sometime in the 2030s.
For these reasons, this commit removes all Oracle Solaris support.
Anyone who still wishes to use Zig on Solaris can try their luck by simply using
illumos instead of solaris in target triples - chances are it'll work. But there
will be no effort from the Zig team to support this use case; we recommend that
people move to illumos instead.
|
|
|
|
|
|
|
|
|
|
This reverts commit c55e83eab1369373fe6db5072802c2fc1c4d7ebc.
This was a misreading of XtensaFeatures.td on my part.
|
|
|