- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Yesterday
Mon, Oct 20
Fri, Oct 17
Thu, Oct 16
- allwinner -> Arm
- Attach the Makefile to std.arm
The best names I can come up with for a workaround for a missing feature is feat_foo_missing or feat_foo_workaround
Wed, Oct 15
Mon, Oct 13
Thu, Oct 9
Tue, Oct 7
Mon, Oct 6
Thu, Oct 2
Wed, Oct 1
Tue, Sep 30
Mon, Sep 29
In D52744#1205716, @alc wrote:In D52744#1205060, @andrew wrote:Note that the llsc instructions have some subtly when implementing fully sequentially consistent semantics. As the acquire and release are on different instructions this means memory operations may move into the sequence & be swapped. As we don't implement them in atomic(9) this shouldn't be an issue, however will be if we latter add them.
I vaguely recall Linux having an issue with the aforementioned behavior about 8-10 years ago in the implementation of a synchronization primitive.
Fri, Sep 26
On arm64 atomics with an acquire then later memory operations can move before the store, however the store needs to succeed as if it doesn't then we will execute the load-acquire again.
Sep 23 2025
Won't that cause problems for stable/15 when stable/16 is branched?
Sep 22 2025
Sep 19 2025
Sep 18 2025
Rebase + update comments
I'm just trying to keep things out of early boot if they don't need to be there.