News for hackers. Stuff that matters.
Re:Branchless Coding in Go by slimsag on Wednesday May 05, 2021 @05:37AM (#27047929)
You could perhaps just have the Go compiler generate the assembler for your code:

go tool compile -S file.go > file_amd64.s

Then you could verify it doesn't change over time, and choose to begin maintaining by hand if it makes sense.

If you do want to go the route of rolling it yourself, I'd suggest looking into something like Avo: https://github.com/mmcloughlin/avo

Re:Branchless Coding in Go by ericbarrett on Wednesday May 05, 2021 @01:33PM (#27052977)
avo looks like would be a great route for this, though I haven't personally used it.