This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
On Fri, Sep 22, 2000 at 05:52:01PM +0200, Andreas Jaeger wrote: > > > Take a look at glibc and ask why we have to save/restore errno all > > over places where we support both new and old system calls. There are > > reasons behind that. I don't recall the details. Someone may remember > > it. > Initially we used to save/restore errno, later we noticed that this is > not needed. All new code (at least code that Ulrich and I recently > added) doesn't save/restore errno - only older code does. I agree, we > should unify this, but so far nobody spoke up. > > Btw. this issue of saving/restoring errno has been discussed already > on the list and we came to the conclusion that it's not needed in this > situation. It has been a while since I ran vsx. Has anyone else ever tried vsx on glibc? H.J.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |