From: David Mosberger <davidm@napali.hpl.hp.com>
Date: Wed, 27 Nov 2002 09:10:47 -0800
You conveniently cut of the important part of my message:
Remember that most compatibility syscalls go straight to the
64-bit syscall handlers. You're probably hosed anyhow if a
64-bit syscall returns, say, 0x1ffffffff, but on ia64 I'd
still rather play it safe and consistently have all
compatibility syscalls return a 64-bit sign-extended value
like all other syscall handlers ("least surprise" principle).
If the return path is different for the 32-bit syscalls,
which is the point I was talking about, then that code path
can sign extend, truncate, or whatever the upper 32-bits of
the return value.
You need to do things differently in the 32-bit return path anyways.
I didn't miss the content of your email at all David, quite the
opposite in fact.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Nov 30 2002 - 22:00:19 EST