"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "README.md" between
Hoard-3.12.tar.gz and Hoard-3.13.tar.gz

About: The Hoard memory allocator is a drop-in replacement for malloc() that can improve application performance, especially for multithreaded programs running on multiprocessors (hint: newer releases now part of the HeapLayers package).

README.md  (Hoard-3.12):README.md  (Hoard-3.13)
[The Hoard Memory Allocator](http://www.hoard.org) [The Hoard Memory Allocator](http://www.hoard.org)
-------------------------- --------------------------
Copyright (C) 1998-2015 by [Emery Berger](http://www.emeryberger.org) [![Build Status](https://travis-ci.org/emeryberger/Hoard.svg?branch=master)](htt
ps://travis-ci.org/emeryberger/Hoard)
Copyright (C) 1998-2019 by [Emery Berger](http://www.emeryberger.org)
The Hoard memory allocator is a fast, scalable, and memory-efficient The Hoard memory allocator is a fast, scalable, and memory-efficient
memory allocator that works on a range of platforms, memory allocator that works on a range of platforms, including Linux,
including Linux, Solaris, Mac OS X, and Windows. Mac OS X, and Windows.
Hoard is a drop-in replacement for malloc that can dramatically Hoard is a drop-in replacement for malloc that can dramatically
improve application performance, especially for multithreaded programs improve application performance, especially for multithreaded programs
running on multiprocessors and multicore CPUs. No source code changes running on multiprocessors and multicore CPUs. No source code changes
necessary: just link it in or set one environment variable (see necessary: just link it in or set one environment variable (see
[Building Hoard](#building-hoard-unixmac), below). [Building Hoard](#building-hoard-unixmac), below).
Press Press
----- -----
skipping to change at line 125 skipping to change at line 127
### Blowup ### ### Blowup ###
Multithreaded programs can also lead the allocator to blowup memory Multithreaded programs can also lead the allocator to blowup memory
consumption. This effect can multiply the amount of memory needed to consumption. This effect can multiply the amount of memory needed to
run your application by the number of CPUs on your machine: four CPUs run your application by the number of CPUs on your machine: four CPUs
could mean that you need four times as much memory. Hoard is guaranteed (provabl y!) to bound memory consumption. could mean that you need four times as much memory. Hoard is guaranteed (provabl y!) to bound memory consumption.
Building Hoard (Unix/Mac) Building Hoard (Unix/Mac)
------------------------- -------------------------
**NOTE: Make sure to invoke git as follows:**
% git clone --recursive https://github.com/emeryberger/Hoard.git
To build Hoard on non-Windows platforms, change into the `src/` To build Hoard on non-Windows platforms, change into the `src/`
directory and run `make` followed by the appropriate target. If you directory and run `make` (or `gmake`) followed by the appropriate
type `make`, it will present a list of available targets. These target. It should automatically detect your system and build
include `linux-gcc-x86`, `solaris-sunw-sparc`, `macos`, `windows`, and appropriately.
more.
% make linux-gcc-x86-64 % make
You can then use Hoard by linking it with your executable, or You can then use Hoard by linking it with your executable, or
by setting the `LD_PRELOAD` environment variable, as in by setting the `LD_PRELOAD` environment variable, as in
% export LD_PRELOAD=/path/to/libhoard.so % export LD_PRELOAD=/path/to/libhoard.so
in Solaris:
% make solaris-sunw-sparc
% export LD_PRELOAD="/path/to/libhoard_32.so:/usr/lib/libCrun.so.1"
(32-bit version)
% export LD_PRELOAD="/path/to/libhoard_64.so:/usr/lib/64/libCrun.so.1"
(64-bit version)
or, in Mac OS X: or, in Mac OS X:
% make macos
% export DYLD_INSERT_LIBRARIES=/path/to/libhoard.dylib % export DYLD_INSERT_LIBRARIES=/path/to/libhoard.dylib
Building Hoard (Windows) Building Hoard (Windows)
------------------------ ------------------------
Change into the `src` directory and build the Windows version: Change into the `src` directory and build the Windows version:
C:\hoard\src> nmake windows C:\hoard\src> nmake
To use Hoard, link your executable with `source\uselibhoard.cpp` and `libhoard.l ib`. To use Hoard, link your executable with `source\uselibhoard.cpp` and `libhoard.l ib`.
You *must* use the `/MD` flag. You *must* use the `/MD` flag.
Example: Example:
C:\hoard\src> cl /Ox /MD yourapp.cpp source\uselibhoard.cpp libhoard.lib C:\hoard\src> cl /Ox /MD yourapp.cpp source\uselibhoard.cpp libhoard.lib
To run `yourapp.exe`, you will need to have `libhoard.dll` in your path. To run `yourapp.exe`, you will need to have `libhoard.dll` in your path.
 End of changes. 8 change blocks. 
24 lines changed or deleted 11 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)