Hi! > > > If you want to go ahead and start runtest/libc, testcases/libc and move > > > all the libc tests there I'm all for it. > > > > On the other hand, I'm not sure where to draw the line. > > For this particular regression test it seemed clear cut, but in general > for functional and stress tests I don't a have good answer.
The most reasonable definition to me seems to call things that have very thin wrapper in glibc or are called by syscall() to be syscall testcases and the rest, even when they end up calling particular syscall to be libc tests. But that is still wrong as any other simple definition. The other simple and wrong option is to move everything that is implemented purely in userspace to testcases/libc/. Or we can stop pretending that there is a clear line between kernel and libc and rename the syscalls to something else. The question is what should be the new name, I do not have a good idea for that. -- Cyril Hrubis chru...@suse.cz ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
