Re: How the FreeBSD developers solve problems that are not r
Maybe I'm not much of a low level developer, but I don't see any "binary" coding there. I see some C code which defines five single lines of assembly. The assembly uses the ".move" instruction to assign a hex value to a variable.
Im sure you'll find many places in FreeBSD source code where the move assembly instruction is used to assign a hex value to a variable.
"Writing binary code" would require authoring a non-ascii file using a hex editor, and directly entering a sequence of instruction codes (basically writing an executable directly by hand). You would not be able to view this code in anything other than a hex editor.
I'm not aware of anything in FreeBSD (and probably other OS's) that requires directly creating binary executables by hand. However, If there was a function that absolutely couldn't be done any other way, I am certain the FreeBSD devs would create the binary code, just like any other developers implementing that function would have to.
Almost all operating systems are written in C. Some small things are written in assembly either bacause they can't be done in C, or they need to be extremely high performance. There may even be situations where certain values are put into certain registers using assembly, in order to call features not exposed through normal instructions. I wouldn't call that binary coding though, it's still just assembly.
What interests me is why the question even came up in the first place or why it matters to you? What difference does it make if FreeBSD developers write any "binary code". They will implement whatever is required to make the OS do what it needs to.
