[openbeos] Re: driver dprintf question
- From: "Allen Brunson" <brunsona@xxxxxxxxxxx>
- To: <openbeos@xxxxxxxxxxxxx>
- Date: Fri, 25 Jul 2003 04:23:10 -0500
Alexander G.M. Smith wrote:
> There's also quad word, %qd, which works in UserLand x86 for 64
> bit numbers, but not in Kernel land.
Don't forget the Intel versus PPC distinction as well! I've never written
kernel-space code, but in userland x86, "%lld" or "%Ld" both work equally
well, but on PPC you can only use "%Ld". No doubt due to differences
between gcc and the Metrowerks compiler.
It seems odd to me that the kernel-land dprintf() sounds so limited. Why no
floating point? Couldn't they just transplant the sprintf() code from the
gcc runtime library into the kernel? Is it a licensing issue?
- Follow-Ups:
- [openbeos] Re: driver dprintf question
- From: François Revol
Other related posts:
- » [openbeos] driver dprintf question
- » [openbeos] Re: driver dprintf question
- » [openbeos] Re: driver dprintf question
- » [openbeos] Re: driver dprintf question
- » [openbeos] Re: driver dprintf question
- » [openbeos] Re: driver dprintf question
- » [openbeos] Re: driver dprintf question
- » [openbeos] Re: driver dprintf question
- » [openbeos] Re: driver dprintf question
- [openbeos] Re: driver dprintf question
- From: François Revol