This is the mail archive of the
mailing list for the GCC project.
Call for testers: libiberty/physmem.c
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- To: gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Fri, 21 Feb 2003 09:28:52 -0500 (EST)
- Subject: Call for testers: libiberty/physmem.c
Now that the libiberty bits are installed, I'd like to see how many
systems physmem.c works on.
So far these are my results:
I've already worked out something with the *utils maintainer for
irix6 which I'll import from upstream.
Given that x86-linux-gnu works, I'm assuming all linux-gnu does and
probably all glibc systems in general. But you never know.
If people would please link the code below against the most recent
libiberty.a from the trunk and/or 3.3 and tell me the results I would
appreciate it. (Zeros are bad.)
I'm especially interested in the evaluation platforms listed in here.
E.g. *bsd, aix, cygwin,
plus alpha-osf, hpux10, darwin and anywhere else you host gcc.
If your favorite platform yields zero, don't panic, the GC heuristics
will simply back down to the old default values. But if you can
provide suggestions on how to improve physmem.c for your platform I'd
very much appreciate it. Note physmem.c must run as non-root, so
peeking into /dev/kmem etc. is not appropriate.
extern double physmem_total(void);
extern double physmem_available(void);
printf ("total=%fMb avail=%fMb\n",
physmem_total() / (1024 * 1024),
physmem_available() / (1024 * 1024));