* tap function args:long on x86
@ 2007-09-26 4:06 Dave Nomura
2007-09-26 4:21 ` Frank Ch. Eigler
0 siblings, 1 reply; 2+ messages in thread
From: Dave Nomura @ 2007-09-26 4:06 UTC (permalink / raw)
To: systemtap
I'm working on an x86 system where in C sizeof(int)==sizeof(long)=4
My understanding is that stap function arguments are all either string or
long. But I was expecting long to match C's idea of long (32 bits.
I have a stap function that looks like:
function init_user(block_step:long, handler:long, init:long)
but if I look in the generated source module code I see
struct function_init_user_locals {
int64_t block_step;
int64_t handler;
int64_t init;
/* no return value */
Is this the behavior that I should expect? stap's long == 64bits on
both 32bit and 64bit architectures
--
Dave Nomura
LTC Linux Power Toolchain
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: tap function args:long on x86
2007-09-26 4:06 tap function args:long on x86 Dave Nomura
@ 2007-09-26 4:21 ` Frank Ch. Eigler
0 siblings, 0 replies; 2+ messages in thread
From: Frank Ch. Eigler @ 2007-09-26 4:21 UTC (permalink / raw)
To: dcnltc; +Cc: systemtap
Dave Nomura <dcnltc@us.ibm.com> writes:
> [...] Is this the behavior that I should expect? stap's long ==
> 64bits on both 32bit and 64bit architectures
That's right. There is only one numeric type in systemtap: signed
64-bit integer that we nickname "long".
- FChE
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-09-25 23:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-09-26 4:06 tap function args:long on x86 Dave Nomura
2007-09-26 4:21 ` Frank Ch. Eigler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).