NLS files reparsed i.e. strerror(3)

Anyone noticed how often the NLS files are re-read and re-parsed?
Any call to strerror(3) for instance causes this.

I am wondering if some others agree that NLS files could be parsed once
per process only ideally, to know if it's worth it that I try to patch
libc for this eventually...

Thanks,
Matt

-- 
Note: Please only reply on the list, other mail is blocked by default.
Private messages from your address can be allowed by first asking.