[pc386 BSP] ticker.exe issue (CVS head)

[Karel Gardas]

Hello,

short followup. I've tested also these configurations with today CVS head, 
but all were broken:

vanilla gcc3.4.5 + vanilla newlib1.14.0
patched gcc4.0.0 + patched newlib1.13.0 (gcc-4.0.0-rtems-20050502.diff, newlib-1.13.0-rtems-20050512.diff)
vanilla gcc3.4.3 + patched newlib1.13.0 (newlib-1.13.0-rtems-20050512.diff)
patched gcc3.4.0 + patched newlib1.13.0 (gcc-3.4.0-rtems-20040510.diff, newlib-1.13.0-rtems-20050512.diff)

everything with patched binutils 2.16.1 (binutils-2.16.1-rtems-20050816.diff)

Is there anybody here running some kind of older CVS head where ticker 
runs fine? I'm asking, since I know it was running fine at least a bit 
before August 23 2005, when I submited patch for pc386 automatic timer 
functionality detection.

Thanks,
Karel

On Sat, 28 Jan 2006, Karel Gardas wrote:

>
> Joel,
>
> IIRC you've had some issues with ticker test for pc386 BSP on CVS head with 
> latest tool-chain. I remember you've been talking about miscompilation. Now, 
> I've used vanilla gcc4.0.2, vanilla newlib1.14.0 and binutils 2.16.1 + 
> binutils-2.16.1-rtems-20050816.diff patch. I've compiled pc386 BSP from today 
> sources and while testing I've found that ticker.exe prints first four lines:
>
> *** CLOCK TICK TEST ***
> TA1 - tm_get - 09:00:00   12/31/1988
> TA2 - tm_get - 09:00:00   12/31/1988
> TA3 - tm_get - 09:00:00   12/31/1988
>
>
> then "blocks", but it seems processor is strangely "working" since
> after some time I see it is corrupting content of the console (VGA)
> RAM. i.e. I see few random chars with few random colors spread over
> the screen.
>
> My question is: have you already solved this your "ticker miscompilation" 
> issue or is it still unsolved and I'm hitting exactly this issue?
>
> Thanks,
> Karel
> --
> Karel Gardas                  kgardas at objectsecurity.com
> ObjectSecurity Ltd.           http://www.objectsecurity.com
>

--
Karel Gardas                  kgardas at objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com