Re: Fastcode MM Rule

Hi

> Let us vote on this rule
>
> A memory manager must not use the 0-3 bytes in the end of allocation
> blocks
> ......
>
> after somebody has helped me write it ;-)


A memory manager must allocate a number of dwords.


This rule sounds better and corresponds with two others:
Allocations must be at least 4 byte aligned.
All allocations must end at a 4 byte aligned address.

--
regards
Aleksandr


.

Relevant Pages

  • Re: java versus C or C++ for number crunching
    ... Because C#'s advantage comes primarily from the implementation of its garbage collection system, I had just assumed that Java had a similar garbage collection implementation and thus shared a similar advantage over C++ in that respect. ... C# incurs some extra overhead relative to C++ memory management when it eventually has to clean up objects, but this rarely impacts performance, as the collection only happens when there's memory pressure and/or idle moments. ... The net is that code that does a lot of allocations usually performs better in C# than C++. ... That would imply that it's got the worst of both worlds: the reclaiming overhead of a garbage collecting memory manager, ...
    (comp.lang.java.programmer)
  • Re: java versus C or C++ for number crunching
    ... Because C#'s advantage comes primarily from the implementation of its garbage collection system, I had just assumed that Java had a similar garbage collection implementation and thus shared a similar advantage over C++ in that respect. ... C# incurs some extra overhead relative to C++ memory management when it eventually has to clean up objects, but this rarely impacts performance, as the collection only happens when there's memory pressure and/or idle moments. ... The net is that code that does a lot of allocations usually performs better in C# than C++. ... That would imply that it's got the worst of both worlds: the reclaiming overhead of a garbage collecting memory manager, ...
    (comp.lang.java.programmer)
  • Re: String that can grow with capacity
    ... at least not without a radically different and new design ... I have spent a lot of time fine tuning the handling of small blocks (< 2.5K, ... not possible for a general purpose memory manager: ... all allocations of a specific size will lie sequentially in memory, ...
    (borland.public.delphi.language.basm)
  • Re: FC Challenge proposal (Per & Patrick reply)
    ... I have been thinking about a memory manager lately, ... of the allocations would be 4K ... globally accessible object would allocate and de-allocate the memory. ... using a callback mechanism from libraries (but then the libraries are ...
    (borland.public.delphi.language.basm)
  • Re: String that can grow with capacity
    ... that all allocations of a specific size will lie sequentially in memory, ... the overheads that a global memory manager can assume, ... function FastFreeMem(APointer: Pointer): Integer; ... The extra implied Self parameters of the record methods would also cause a ...
    (borland.public.delphi.language.basm)