[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnugo-devel] Memory usage
From: |
Dave Denholm |
Subject: |
Re: [gnugo-devel] Memory usage |
Date: |
Thu, 30 Mar 2006 15:19:35 +0100 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2 (usg-unix-v) |
"Alexander Pruss" <address@hidden> writes:
> Hi!
>
> I'm thinking of porting GnuGo to PalmOS 5, but am wondering how
> feasible this is for devices most of which have less than 4mb of
> dynamic RAM available (without hacks to expand dynamic heap). To
> check for feasibility, I'd like to know a bit more information.
>
> 1. I am wondering what the code size is. Does anybody have an ARM
> Linux build? That would be the best test of code size, I guess. My
> cygwin x86 build is 4.8mb.
I do have cross-compilers around, but unfortunately the gnugo build
system expects to build and run mkpat on the host system as part of
the build. I think configure does support this kind of thing, but it
probably needs some extra work to support it.
I was able to build by just copying in the native mkpat etc manually.
The section sizes from objdump are
.text: 000b6a88
.rodata: 00069201
.data: 0013f0b0
.bss: 001a5f48
around 1Mb read-only and 3Mb writeable
Note that these are relatively old tools (for zaurus). gcc 4.x is
quite a lot better for arm.
Thumb would probably make it a bit smaller, if your target supports
that. But it's probably the ram size rather than the code size that's
more relavant.
> 2. How much dynamic memory is needed?
>
# cat /proc/15527/status
Name: gnugo
State: R (running)
Tgid: 15527
Pid: 15527
PPid: 12841
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 256
Groups: 0
VmSize: 14340 kB
VmLck: 0 kB
VmRSS: 11120 kB
VmData: 10352 kB
VmStk: 144 kB
VmExe: 1156 kB
VmLib: 1308 kB
SigPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 8000000000000000
SigCgt: 0000000000000000
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
# cat /proc/15527/maps
02000000-02121000 r-xp 00000000 00:09 11754047
/home/system/var/mnt/tfs/ddenholm/gnugo-arm/interface/gnugo
02128000-02268000 rw-p 00120000 00:09 11754047
/home/system/var/mnt/tfs/ddenholm/gnugo-arm/interface/gnugo
02268000-0247f000 rwxp 00000000 00:00 0
40000000-40019000 r-xp 00000000 1f:01 263 /lib/ld-2.2.2.so
40020000-40022000 rw-p 00018000 1f:01 263 /lib/ld-2.2.2.so
40022000-40047000 r-xp 00000000 1f:01 267 /lib/libm-2.2.2.so
40047000-4004a000 ---p 00025000 1f:01 267 /lib/libm-2.2.2.so
4004a000-40050000 rw-p 00020000 1f:01 267 /lib/libm-2.2.2.so
40050000-40159000 r-xp 00000000 1f:01 264 /lib/libc-2.2.2.so
40159000-40160000 ---p 00109000 1f:01 264 /lib/libc-2.2.2.so
40160000-40167000 rw-p 00108000 1f:01 264 /lib/libc-2.2.2.so
40167000-4096c000 rw-p 00000000 00:00 0
bffdc000-c0000000 rwxp fffdd000 00:00 0
- does this help ?
dd
--
Dave Denholm <address@hidden> http://www.esmertec.com
Re: [gnugo-devel] Memory usage, Aloril, 2006/03/30