Date: Mon, 13 Oct 2014 09:50:45 -0300 From: =?UTF-8?Q?fran=C3=A7ai_s?= <romapera15@gmail.com> To: freebsd-drivers@freebsd.org Subject: How the FreeBSD developers solve problems that are not resolved by Assembly? Message-ID: <CAK_6RwcXLDFfDMWn%2BA%2Bjcap3C8jV=G7ZWfY9cr-9mv5h3z4=og@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I think that the only case where you have to resort to writing binary code manually is when the assembler cannot output the desired code for some reason. If I recall correctly, there is only one such case in the HelenOS sources: http://trac.helenos.org/browser/mainline/kernel/arch/mips32/include/debug.h?rev=mainline%2C1446.3.1 Here they manually encode the opcodes of five special debugging instructions for the MSIM MIPS simulator (these instructions are not part of the standard MIPS ISA, thus the assembler does not know them). But the developers of FreeBSD not write binary code manually. How the FreeBSD developers solve problems that are not resolved by Assembly?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAK_6RwcXLDFfDMWn%2BA%2Bjcap3C8jV=G7ZWfY9cr-9mv5h3z4=og>