On Mon, Jul 16, 2001 at 02:03:30PM +0200, Maciej W. Rozycki wrote: > I didn't profile it very extensively, yet when stracing `ls /usr/lib' > (fileutils 4.1 linked against glibc 2.2.3) on my system once I yielded > ~4500 syscalls of which ~4000 were _test_and_set() (or MIPS_ATOMIC_SET, > depending on my kernel/glibc configuration) invocations. Yes, libpthread > appears to assume atomic operations are cheap, which is justifiable as > they are indeed, for almost every other CPU type. On a fast Indy those 4000 syscalls would cost about 3.2ms of CPU which is a noticable fraction of the total execution time. > Also I feel having ll and sc opcodes in a pure MIPS I binary is somewhat > ugly (e.g. `objdump' won't disassemble them unless a MIPS II+ CPU is > specified), but I could probably live with it if performance was not > worse. This behaviour of objdump sucks rocks anyway. There are MIPS I CPUs which have ll but no branch likely and many other MIPS ISA perversions. Objdump also will only hexdump anything that hasn't been marked as code with .type. Seems objdump's behaviour was choosen to be the most annoying possible. Ralf
