hernanponcedeleon.bsky.social
@hernanponcedeleon.bsky.social
Research engineer @ Huawei.

Interested in concurrency, PL, and formal methods.

https://hernanponcedeleon.github.io/
Argentina had 5 in 11 days 🤪
October 10, 2025 at 10:26 AM
We presented a generalization of recurrence sets to concurrent programs having execution-based semantics.

Despite the name, this works not only for weak memory models, but also for unfair schedulers (aka weak progress guarantees).

Preprint coming soon. Stay tuned!
October 6, 2025 at 9:22 AM
The talk ended with "promises" about future work on how CXL interacts with weak memory. Looking forward to that 😍
April 3, 2025 at 6:39 AM
Despite our efforts over the years to make the tool scalable and practical, I am still surprised to see that while our focus is on weak memory models, we are still competitive against SOTA tools specialized for Sequential Consistency.
March 25, 2025 at 12:27 PM
This project is a key component in libvsync (github.com/open-s4c/lib...), a verified library of synchronization primitives and concurrent data structures.
GitHub - open-s4c/libvsync: A verified library of synchronization primitives and concurrent data structures
A verified library of synchronization primitives and concurrent data structures - GitHub - open-s4c/libvsync: A verified library of synchronization primitives and concurrent data structures
github.com
March 13, 2025 at 7:01 PM
The memory ordering guarantees provided by the atomic interface are formally described in the VSync Memory Model. Users can use it to verify the correctness of their algorithms with a model checker such as dartagnan (github.com/hernanponced...) or vsyncer (github.com/open-s4c/vsy...).
GitHub - hernanponcedeleon/Dat3M: A verification tool for many memory models
A verification tool for many memory models. Contribute to hernanponcedeleon/Dat3M development by creating an account on GitHub.
github.com
March 13, 2025 at 7:01 PM
One of my regrets from my time as a master student is that I never attended RIO.

Enjoy!
March 6, 2025 at 12:50 PM
I remember a situation we faced where some verified code using futexes ended up hanging on the real system. The problem was that the abstraction we chose for the futex was sound for safety, but unsound for liveness. A solution for the later resulted in the verification being 10x slower
January 21, 2025 at 7:57 AM
👍 ... DM
January 2, 2025 at 7:00 AM
Only in the states?
January 1, 2025 at 9:04 AM