Re: hwcap supporting architectures?
On Sat, Jan 15, 2005 at 10:14:15PM +0900, GOTO Masanori wrote:
> > occurs when you have for example an ev56 library in lib/ev56, and a
> > ev67 CPU. Then the loader looks in lib/ev67 and then falls back to
> > lib. Since glibc is very carefully undocumented in this area , I
> > didn't want to try to change this, but rather assumed one could add
> > a symlink.
> Yes, and if ev67 is instruction upper compatible with ev56 (I guess
> so), I think it's acceptable to add a symlink "ln -sf
> lib/ev67/libfoo.so lib/ev56/libfoo.so".
Ugh... that pushes the burden of maitaining support for new
architectures to the package. Please bear with me, but I'm trying to
understand the issue: is the cost of calling access(2) or stat(2)
really so high? I see for example that on start up the file
/etc/ld.so.nohwcap is accessed multiple times (and it's not present,
isn't that a race? what happens if the file suddenly appears in the
middle of program start up? what's that file anyway, I can't find it
mentioned in the documentation).