I can't remember the details off-hand, but I know it doesn't support all
the printf-style options. We have a gap in documentation and need to
add which options GT does support in which environments.
The rationale for GT only supporting a subset is that it's a little more
speedy and lighter footprint. But GT is so 'over the top' configurable
that what options are supported in what environment isn't quite a
straightforward answer. I'll try to dig this up and get the details on
the wiki.
(I like the sprintf workaround, though!)
Chris
________________________________
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
com] On Behalf Of Joshua Hintze
Sent: Wednesday, January 30, 2008 10:26 AM
To: [email protected]
Subject: RE: GT_trace1 and floats/doubles
Thanks, I tried the sprintf, but then I passed in the char *
directly into the GT_trace. I will try it with the %s format specifier.
Josh
From: Ben White [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 30, 2008 9:04 AM
To: Joshua Hintze;
[email protected]
Subject: RE: GT_trace1 and floats/doubles
Hi,
Actually the only way I found to do it was to sprint into a char
buffer first and then do a %s with the buffer. That seems to work OK.
Cheers,
Ben
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Joshua Hintze
Sent: 29 January 2008 21:29
To: [email protected]
Subject: GT_trace1 and floats/doubles
Is there any way to show floats and our double values in the GT
trace output?
I've tried %f and %lf in the format specifier without luck. %d,
%s, %x seem to work.
Has anybody got this working?
Thanks,
Josh
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
