![]() |
04-18-2015
|
64 | |||
Brogrammer
Join Date: Apr 2015
Posts: 28
|
http://pivotallabs.com/all-evidence-...eing-bull****/ OOP is garbage.
|
|||
04-18-2015
|
68 |
Registered User
Join Date: Nov 2012
Posts: 121
|
I can't remember which arch (I think MIPS) or the specific instructions, but there was something about inconsistent arrangement for a couple of opcodes where the corresponding instructions in assembly looked consistent. I think glossing over that is some level above writing pure opcodes. From what I recall, a lot of assemblers give you convenience macros/pseudo-instructions, which assemble into several machine instructions. I think, however, it's such a small level above machine code that making a big fuss over the distinction is perhaps pedantic. |
04-18-2015
|
70 |
Registered User
Join Date: Nov 2012
Posts: 121
|
There is some level of text processing to assemble into object files. I imagine it wasn't a stretch to include built-in and user-defined macros on top of that. It's still architecture dependent because it is so close to machine code as you say but I think there is a bit of wiggle room for convenience features. If you notice, assemblers have varying syntax from assembler to assembler. Code written for gas is different from nasm, etc. With some assemblers, the difference is minimal but enough to catch you out, such as literals, referencing memory, etc. I think with GNU in particular it uses at&t syntax by default (though accepts Intel too). With that, the order of operands are reversed so typically, with Intel as common, you have: PHP Code:
PHP Code:
|