Tool Comparison: Difference between revisions

Jump to navigation Jump to search
[unchecked revision][unchecked revision]
← Older editNewer edit →
Content deleted Content added
VisualWikitext
No edit summary
Cic (talk | contribs)
57 edits
Minor format improvements
Line 1: Line 1:
This is a comparison of various osdev tools
This is a comparison of various operating system development tools.


==x86 Assemblers==
==x86 Assemblers==
<!--I'll fix this later, this is just an example-->
{| {{wikitable}}
{| {{wikitable}}
|-
|-
Line 71: Line 70:
|}
|}


⚫
* {{note|1}} using the <code>.intel_syntax</code> directive. Several opcodes will still use the AT&T name.

⚫
* {{note|2}} While GAS normally writes only "pure" 32-bit i386 code, it has [http://sourceware.org/binutils/docs/as/i386_002d16bit.html#i386_002d16bit limited support] for writing code to run in real mode or in 16-bit protected mode code segments.
⚫
{{note|1}} using .intel_syntax directive. Several opcodes will still use the AT&T name.
⚫
* {{note|3}} You have to choose the instruction set at compile time. GAS can not assemble for more than one operating mode at a time.

⚫
* {{note|4}} 64-bit support is only available in NASM 2.x.
⚫
{{note|2}} While GAS normally writes only "pure" 32-bit i386 code, it has limited support for writing code to run in real mode or in 16-bit protected mode code segments. See [[http://sourceware.org/binutils/docs/as/i386_002d16bit.html#i386_002d16bit Here]]

⚫
{{note|3}} You have to choose the instruction set at compile time. GAS can not assemble for more than one operating mode at a time

⚫
{{note|4}} 64-bit support is only available in NASM 2.x.


==Compilers==
==Compilers==
Line 109: Line 104:
|}
|}


{{Note|4}} Visual Studio can emit .COM files
* {{Note|4}} Visual Studio can emit <code>.COM</code> files.


==Linkers==
==Linkers==
Retrieved from "https://osdev.wiki/wiki/Tool_Comparison"