| |
| |
| |
|
Comments:
<0> segment .code USE32 ;just tells w/e the following code will be 32bit?
<0> is that pseudocode correct?
<1> ownagesbot|meh2: for what ***embler?
<0> nasm
<1> i always use 'bits 32'
<0> oh okay :) but im basically correct? ive just started asm :)
<1> USE32 is just to specify bits individually for different sections
<1> unless you do 16-bit realmode stuff i'd use the term 'section' and not 'segment' :)
<0> oh ok, thanks
<1> but they are synonyms in nasm anyway
<0> :)
<0> Any idea why 0 is pushed onto the stack at just before messagebox is called?
<1> messagebox?
<0> Sorry,
<0> MessageBoxA (user32.dll)
<1> no windows here
<0> Ah np :)
<0> ty anyway
<0> One last thing, when I call a function, does it pop the operands on the stack? (like the ones it uses for parameters I mean)
<1> depends on calling convention
<0> oh?
<0> asm is confusing imo
<2> it'll pop it backwards
<2> well, no
<2> you send it backwards
<2> and it pops it normally
<2> Last in First out
<0> I understand that,
<0> I was just wondering if every call would pop the top operand(s)
<2> depends on calling convention :P
<2> if it has arguments, it'll pop them and then do stuff with them
<3> Does flat***embler compete with the other popular ***emblers?
<4> archivist: i swear you are in every channel there is..
<5> can anyone recommend a simple tute/example to get a directx surface ?
<5> i am new to win asm, but can handle A000h vga :)
<6> A win asm is like a lost asm...
<7> Does anybody in here have Easy Lover by Phil Collins?
<7> Or Studio?
<8> I have just have in the air tonight like everyone :P
<1> w
<1> whoops :)
<9> 'lo
<9> anyone alive?
<10> about 6 billion people, i was told some time ago
<9> Ah yes, me too unfortunately
<9> But what can ya do...
<9> Yes indeed what can ye do...
<9> Trying to learn at&t syntax
<10> i'm still quite a noobie to asm, let's hope someone else is hearing also
<9> I'm just here for the beer
<11> qubits, you'd be quicker with less gaga ;)
<9> meh
<11> it worked! :D
<12> Stormbreaker, look at #hasbeen :)
<13> hey, i am trying to compile few vmx instructions, but when i run the vmxoff instruction i get ( in the linux kernel log messages ) "Feb 1 04:28:16 Dual invalid opcode: 0000 [1] SMP" , it is weird due to the fact that vmxon run perfectly... and vmxoff shouldnt get any value and not even depened in anything but the vmxon...
<13> when i want to send paramater to instruction such as vmxon i do it like this: vmxon (%%rax) right? ( in at&t )
<14> hi
<14> sparc arch: why bother having a bn?
<14> branch never
<15> niles: to have orthogonal encoding.
<15> it IS pointless, it's just an artifact of the way instructions are encoded in binary
<15> in the same way you have mov eax, eax on x86
<15> or loads of other do-nothing instructions
<15> actually... iirc bn,a would skip the following instruction, which would be marginally useful if next instruction is a target for another branch
<16> I have 'yMul: dw 25,129,66,0' in my code, and I'd like to replace it with an immediate value (eg use '0x????????' directly in the code)
<16> it's x86/x86_64, how do I need to convert it? will it become 0x00?????? or 0x??????00?
<16> and is there any significant difference between having the variable in the .rodata section or use the immediate value?
<1> hmm
<1> wereHamster: bit more context might help
<1> and there are no variables in ***embler :)
<16> I'm trying to make my code PIC-conform, and while in x86_64 I can simply use '[yMul wrt rip]', I couldn't find such easy way for x86.
<16> yMul is not a variable, but merely points to a location in memory, right?
<1> nasm supports that kind of syntax on _64? interesting
<16> yasm..
<15> lindi-: nah, nasm doesn't even support 64-bit.
<1> wereHamster: ah, i don't know about it then
<15> some nasm mutation
Return to
#asm
or
Go to some related
logs:
difference y2pmsh installation_sources
session qcodo
squirrelmail login without full email address
remote desktop process rdp
#oe
mplayer FT_GlyphSlot_Embolden
ubuntu gui service
gentoo lsdev
sata longer than 2m
marvell gigabit genkernel
|
|