I also would never use src_buf / dest_buf. I used to do src/dst, but now I vastly prefer to just use register names.
Conversation
(Because when I go back to edit it, it's a royal pain to figure out what registers are available for scratch or which names are actually the same register. So now I use the register name for everything and put a decoder ring at each main label.)
2
2
does there exist tooling to help people like you? one can imagine all sorts of great assembly-assist things, but the market would be so small it would be hard to justify producing it
2
4
I wanted a register-allocating, macro assembler for A64 with pluggable scheduler backends and couldn't find one so I wrote "sketchy" a few years ago
2
14
On top of there being few people wanting this tool, those few people can also all write their own instead of taking time to learn someone else's
1
3
Joe y would I use yr Perl script when i can write as good a perl script of my own??? it will do register allocation using 13 regexes.
1
2
7
Have you seen Samsung's kernel CFI implementation from before they gave up and moved to Google's upstream Clang CFI?
It's the most horrifying thing and by that I mean they pass compiled kernel code through a Python script using objdump to add CFI instrumentation as a total hack.
2
1
17
"Samsung" and "kernel" are two flavors that go together like orange juice and toothpaste, see also lwn.net/Articles/52939 (they had more than one of those, FWIW)
2
14
Look, I was upset enough about the whole thing with two different cacheline sizes in a package. I'm not reading anything else.
3
6
