updated macros
fix a bug in bigmsg.c0 making libi0 failed to be compiled
Merge branch 'rc' of github.com:layerzero/libi0 into rc
compiled libcrt.o
add random.c src
add stdint.c0 src
bugfix in stdint.c0
stdint.c0: change endian
stdint.c0: make names of variables easier to read
add grep function to libi0
add comment for grep() to explain its usage and semantic
bugfix: non-rep pmem size fixed with correct size
sync libcrt.0 @ 20141113
use SPACE(I) format spece specifiers
All app to specify PPM size
add macros on old PPM_*
add back PPM_*
Revert changes in b3e7d1cf1fe1d3506f7ebb6cfd9312eab274b830

The changes are not a good idea at least at current.

Simply adding the PLS_PPM_SIZE will cause non-expected or error behaviors.

The reason is as follows.

1) D-thinker memory system should have a consistent view of the memory
space layout as the Puc programs. The macro here only reflects what the Puc
program will consider the memory layout but not what the D-thinker memory considers.
Non-consistency in the views of memory layout will cause non-expected behaviors.

2) D-thinker's memory should not be modified after it is set. If it is changed,
what if some non-persistent memory turns to persistent memory? Where is the data?
what if some non-replicated memory range turns to replicated memory range? Where is
the replicated pages? The metadata structures will need to be changed? How to change it?
How long will it take? and lots more problems.

For now, the added macro does not work as expected. Hence, I revert the changes.

The reverting is as a commit (this one). So when we want to add them back,
we can re-do what is undo here.
keep PPM_START/BEGIN/END/SIZE as old behavior; programmers are encouraged to use more specific macros: http://tab.d-thinker.org/showthread.php?tid=2720