Index
> Windows > Learning fasm from masmGoto page Previous 1, 2, 3, 4, 5, 6 |
| Author |
|
|
randall 10 Oct 2012, 18:12
What you described is switching overhead
 |
|||
10 Oct 2012, 18:12 |
|
|
nmake 10 Oct 2012, 20:30
Overhead deals with the obvious code needed to switch threads. Cache pollution is not detectable and has no overhead it is just a side effect and is not always the case, pollution doesnt always happen so it can't be part of any overhead. It is just magic bads.
|
|||
|
10 Oct 2012, 20:30 |
|
|
nmake 11 Oct 2012, 14:26
I would be pleased to know where I can find include files for GDI+.. I really don't want to be stuck with GDI32 all the time
Never mind I found them in that package I mentioned in an earlier post. |
|||
|
11 Oct 2012, 14:26 |
|
|
nmake 11 Oct 2012, 23:08
I wonder if it pays off to create threads one time and keep them for the entire duration of the program or if it pays off to create them as needed and exitthread when it's done.
|
|||
|
11 Oct 2012, 23:08 |
|
|
nmake 12 Oct 2012, 02:49
Can anyone teach me how I can declare global data from within a macro, without using any of the global macros already created, I want to learn to do it myself. How can I put something in my .data section from within a macro?
|
|||
|
12 Oct 2012, 02:49 |
|
|
revolution 12 Oct 2012, 03:30
nmake wrote: Can anyone teach me how I can declare global data from within a macro, without using any of the global macros already created, I want to learn to do it myself. How can I put something in my .data section from within a macro? http://board.flatassembler.net/topic.php?t=12012 |
|||
|
12 Oct 2012, 03:30 |
|
|
revolution 12 Oct 2012, 03:31
nmake wrote: I wonder if it pays off to create threads one time and keep them for the entire duration of the program or if it pays off to create them as needed and exitthread when it's done. Last edited by revolution on 12 Oct 2012, 12:30; edited 1 time in total |
|||
|
12 Oct 2012, 03:31 |
|
|
nmake 12 Oct 2012, 12:16
Using data definition in macros is something I am familiar with, but if you combine code and data in the macro, how would you go about defining global data in the macro? If you use the macro only in the code section, how can you move any data defined in the macro to the .data section
|
|||
|
12 Oct 2012, 12:16 |
|
|
revolution 12 Oct 2012, 12:27
nmake wrote: Using data definition in macros is something I am familiar with, but if you combine code and data in the macro, how would you go about defining global data in the macro? If you use the macro only in the code section, how can you move any data defined in the macro to the .data section http://board.flatassembler.net/topic.php?t=12012 |
|||
|
12 Oct 2012, 12:27 |
|
|
nmake 13 Oct 2012, 01:26
Those macros are a bit complex because I have barely begun using fasm macros. Could you teach me in extremely simple and readable terms how to declare global data from within a macro. Could you simplify it as much as possible and make it as readable as possible and comment each line to tell me what it does?
|
|||
|
13 Oct 2012, 01:26 |
|
|
revolution 13 Oct 2012, 01:32
|
|||
|
13 Oct 2012, 01:32 |
|
|
nmake 13 Oct 2012, 14:11
What are double backslashes used for? Is it to produce a single backslash?
|
|||
|
13 Oct 2012, 14:11 |
|
|
revolution 13 Oct 2012, 14:24
nmake wrote: What are double backslashes used for? Is it to produce a single backslash? |
|||
|
13 Oct 2012, 14:24 |
|
|
nmake 13 Oct 2012, 15:11
How can I watch what the preprocessor produces after compiling? I need to see what it actually does with my macros.
|
|||
|
13 Oct 2012, 15:11 |
|
|
mindcooler 13 Oct 2012, 15:48
Compile with TOOLS\WIN32\PREPSRC.ASM
|
|||
|
13 Oct 2012, 15:48 |
|
|
nmake 13 Oct 2012, 16:02
Does SignalAndWait actually sleep the calling thread after it has signalled the other object?
|
|||
|
13 Oct 2012, 16:02 |
|
|
revolution 13 Oct 2012, 16:15
nmake wrote: Does SignalAndWait actually sleep the calling thread after it has signalled the other object? http://msdn.microsoft.com/en-us/library/system.threading.waithandle.signalandwait.aspx |
|||
|
13 Oct 2012, 16:15 |
|
|
nmake 13 Oct 2012, 17:19
I meant SignalObjectAndWait of course
The one you refer to is a .NET function which is not exactly that useful for assembly programmers. But it is okay. I've read it dozen of times before but ms docs is not very complete that is why I ask here. I use msdn every day. http://msdn.microsoft.com/en-us/library/windows/desktop/ms686293(v=vs.85).aspx |
|||
|
13 Oct 2012, 17:19 |
|
| Goto page Previous 1, 2, 3, 4, 5, 6 < Last Thread | Next Thread > |
Forum Rules:
|