From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> Date: Mon, 15 Mar 2010 16:18:33 +1100 > Or is there any good reason -not- to do that in glibc ? The whole point of syscall() is to handle cases where the C library doesn't know about the system call yet. I think it's therefore very much "buyer beware". On sparc it'll never work to use the workaround you're proposing since we pass everything in via registers. So arch knowledge will always need to be present in these situations. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
