Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As others have pointed out, system calls and interrupts are different. I can think of another few differences.</p> <p>The instruction set is the same across all OSes on a given processor, but the executable file format might not be. For example, on the x86, Windows uses the PE format, Linux uses ELF, and MacOS uses Mach-O. That means that assemblers on those platforms must produce their output in those formats, which is a difference.</p> <p>Relatedly, the calling convention could also be different across different OSes. That probably only matters where you are writing assembly code that calls or is called by compiled-code routines, or perhaps where you are writing inline assembler in some compiled code. The calling convention governs which registers are used for what purposes during a function call, so different conventions require different use of registers by calling and called code. They also put constraints on the position of the stack pointer, and various other things. As it happens, calling conventions have historically been a rare example of consistency across OSes in many cases: i believe the Windows and UNIX calling conventions are the same on the x86 (and are all based on the venerable UNIX System V ABI specification), and are consistent across OSes on most other architectures. However, the conventions are now different between Windows and UNIX on the x86_64.</p> <p>In addition, there may be differences in the syntax used by the assembly language. Again on the x86, the Windows and Linux assemblers used to use different syntax, with the Windows assembler using a syntax invented by Intel, and the Linux assembler (really, the GNU assembler) using a traditional UNIX syntax invented by AT&amp;T. These syntaxes describe the same instruction set, but are written differently. Nowadays, the GNU assembler can also understand the Intel syntax, so there is less of a difference.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do assembly languages depend on operating systems?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTom Anderson
    1. USTom Anderson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do assembly languages depend on operating systems?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI thought about adding a section on executable formats too, but AFAIK assemblers take care of that themselves without the programmer caring about the format used. Either way, great answer, +1
      singulars
      1. PO
      1. This table or related slice is empty.
    2. CO@delnan: Yes, you're right, the assembler will take care of the output format. Do the different formats introduce differences in the way you declare data sections on so on, or the lengths of symbols you can use? If not, then indeed, there are no user-visible differences.
      singulars
      1. PO
      1. USTom Anderson
    3. COHonestly, I don't know. Symbol length *shouldn't* be an issue as long as they don't get insanely long (thousands of characters), and assemblers should be able to abstract section details away, but then again, I've never really written significant assembly code.
      singulars
      1. PO
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload