答复: 答复: [COMMIT] romcc 0.63 and some fixes...

[YhLu]

After I get USB boot done, I will try that and modify the auto.c.....

Regards

YH

-----邮件原件-----
发件人: [e-mail] [mailto:[e-mail]] 
发送时间: 2004年5月28日 9:56
收件人: YhLu
抄送: LinuxBIOS
主题: Re: 答复: [COMMIT] romcc 0.63 and some fixes...

YhLu  writes:
> I'd like to wait it to produce smaller code. Otherwise if I enable superio

+
> ati support, It will be greater than 64K in debug mode.
>
> When will that be ready?

The code is feature complete so it will correctly not inline functions
(producing smaller code) if it does not run out of registers.

My simple test cases have worked well.

My complicated test case that uses an old version of production code
ran out of registers after consuming just the 8 general purpose
registers.  So mostly it is a matter of playing with the code, and
figuring out why weird things are happening.

Eric

答复: 答复: [COMMIT] romcc 0.63 and some fixes...

YhLu  writes:
> After I get USB boot done, I will try that and modify the auto.c.....

Ok.

A quick update.

In playing around I wrote the function:

static void printo_debug(const char *str) __attribute__((noinline))
{
    print_debug(str);
}

And started replacing the calls to print_debug one by one.
On the port I am currently working on I managed to shave off 4K
pretty quickly.

So it looks like for the really commonly called functions we
will need 2 names.  One inline that will be inlined the other that won't.

It is not a very elegant solution but it works and is not very hard to
manage.

Eric