News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

Recent posts

#31
The Laboratory / Re: Invoke, call, jump. Simple...
Last post by LordAdef - June 28, 2025, 08:13:25 AM
Quote from: NoCforMe on June 28, 2025, 05:05:18 AM
Quote from: jj2007 on June 27, 2025, 10:42:23 PM
Quote from: NoCforMe on June 27, 2025, 06:06:57 AMYou don't seem to understand what invoke actually does.

I'm sure he does.

OK, but then why would he suppose there's any difference between INVOKE and CALL?

It's not as if the macro does any alignment or anything like that.

Because it doesn't matter.
Because I quickly tested pushing arguments, but left without it.
Because, if you read my first post, a new comer may have the misconception that call is always faster than invoke.
Because, you may try to use the test example and compare, if you like, an aligned invoke passing one arg, and try to beat an unaligned call. Whatever.

The point of this thread is alignment
#32
The Laboratory / Re: Invoke, call, jump. Simple...
Last post by NoCforMe - June 28, 2025, 05:05:18 AM
Quote from: jj2007 on June 27, 2025, 10:42:23 PM
Quote from: NoCforMe on June 27, 2025, 06:06:57 AMYou don't seem to understand what invoke actually does.

I'm sure he does.

OK, but then why would he suppose there's any difference between INVOKE and CALL?

It's not as if the macro does any alignment or anything like that.
#33
The Laboratory / Re: Invoke, call, jump. Simple...
Last post by LordAdef - June 28, 2025, 01:25:46 AM
Quote from: TimoVJL on June 27, 2025, 07:11:52 PMCPU cache suffers long jumps too ?
Also call flush cache ?
good questions
#34
The Laboratory / Re: Invoke, call, jump. Simple...
Last post by LordAdef - June 28, 2025, 01:25:10 AM
Quote from: jj2007 on June 27, 2025, 10:42:23 PM
Quote from: NoCforMe on June 27, 2025, 06:06:57 AMYou don't seem to understand what invoke actually does.

I'm sure he does.
Yep!
#35
The Laboratory / Re: Invoke, call, jump. Simple...
Last post by jj2007 - June 27, 2025, 10:42:23 PM
Quote from: NoCforMe on June 27, 2025, 06:06:57 AMYou don't seem to understand what invoke actually does.

I'm sure he does.
#36
The Laboratory / Re: Invoke, call, jump. Simple...
Last post by TimoVJL - June 27, 2025, 07:11:52 PM
CPU cache suffers long jumps too ?
Also call flush cache ?
#37
UASM Assembler Development / Re: Linux users, please
Last post by LordAdef - June 27, 2025, 12:38:21 PM
Quote from: mabdelouahab on June 22, 2025, 05:28:53 AMhi LordAdef
I'm excited about the project, even if my time is limited. Where do you suggest we begin?
welcome aboard mabdelouahab!! I will PM you.

Alex
#38
The Campus / Re: Way besides ExitProcess to...
Last post by NoCforMe - June 27, 2025, 09:34:25 AM
Looks like you answered a question nobody asked.
#39
The Campus / Re: Way besides ExitProcess to...
Last post by Vortex - June 27, 2025, 06:09:01 AM
Hi Quan,

ExitThread : Ends only current thread.
#40
The Laboratory / Re: Invoke, call, jump. Simple...
Last post by NoCforMe - June 27, 2025, 06:06:57 AM
Quote from: LordAdef on June 27, 2025, 05:04:23 AMWhile writing the test prog, I was moving routines around and sometimes I got "invoke" faster than "call"

You don't seem to understand what invoke actually does.
It's a macro which behaves differently depending on whether the thing being invoked has parameters or not:
  • If the subroutine has parameters (and if there is a PROTOtype defined for that routine), invoke pushes the parameters from the "outside in", then does a CALL.
  • If the subroutine has no parameters, then invoke simply does a CALL.

So in the latter case there's no difference between invoke and CALL.

invoke is not a processor opcode.