Small Device C Compiler suite

I was using build  20041220  and upgraded to 20050222 of the Linux x86 
binary build
and now the zero padding in printf_fast is not working.

printf_fast("%d:%02d",HOUR,MIN);

I get output of a what appears to be a space in my serial console where 
there should be a leading "0".

I am using 8051 specifically  Analog Devices ADUC814 
my compile command is
sdcc -c  --iram-size 256 --model-small --code-size 8000 --opt-code-size 
--xram-size 0 uart.c

Is there a #define or compile flag to get the leading zero back?

For the moment I downgraded back to 20041220

-- 

---
Karl Hiramoto <karl@...>
US VOIP: 603.966.4448
Spain Home from US 011(34) 952.827.554
Spain Home from EU 00 (34) 952.827.554
Spain Mobil 011 (34) 617.463.826
Yahoo_IM = karl_hiramoto   jabber.org=karl_hiramoto
------
-
If built in great numbers, motels will be used for nothing but illegal
purposes.
		-- J. Edgar Hoover

Re: [Sdcc-user] printf_fast behavior change From: Paul Stoffregen <paul@pj...> - 2005-03-09 20:53 Opps...... > and now the zero padding in printf_fast is not working. Looks like I broke it while adding float support (eg, library printf_fast_f supports %f for floats), and several more options to customize if you recompile printf_fast. Checked in a fix. Look for #969 (or higher) with "sdcc -v". If you hit any other bugs in printf_fast, probably best to email me directly. I only occasionally check this list. Always send sample code and corresponding wrong output. If you lose my address, it's in the comments in the printf_fast.c source code. Paul

3 messages have been excluded from this view by a project administrator.