Re: Fastcode MM Rule

From: "Atle Smelvær" <atle@xxxxxxxxxxxxxx>
Date: Thu, 28 Apr 2005 15:20:33 +0200

If all allocations end at 4 byte aligned address, then it is possible to
create more optimized functions when dealing with read / write streams in
memory where length is not know in advance to the function (like PChar
handling).

-Atle

.

Follow-Ups:
- Re: Fastcode MM Rule
  - From: Joe Bain

References:
- Fastcode MM Rule
  - From: Dennis
- Re: Fastcode MM Rule
  - From: Aleksandr Sharahov

Prev by Date: Re: MM B&V "ManyShortLivedThreads" lock up
Next by Date: Re: Fastcode MM B&V 0.33
Previous by thread: Re: Fastcode MM Rule
Next by thread: Re: Fastcode MM Rule
Index(es):
- Date
- Thread

Relevant Pages

Re: Fastcode MM Rule
... Atle Smelvfr wrote: ... > If all allocations end at 4 byte aligned address, ... > to create more optimized functions when dealing with read / write ...
(borland.public.delphi.language.basm)
Re: SUM(IF..... in Visual basic
... both speed and memory. ... XL's built-in compiled and optimized functions. ... There is a speed advantage to using SUMPRODUCT() rather than SUM), ...
(microsoft.public.excel)