On Mon, Feb 22, 2010 at 8:34 AM, Patrick Georgi patrick@georgi-clan.de wrote:
The other issue is that in an .s file, we're bound to function calling conventions. with __asm__, we can really include code.
I understand. But I work with a very nice operating system that has never had a need for __asm__, so I question the need for it myself.
I'd still like to see the reason that memset is so slow.
Also, I realize we have dropped support for other architectures, but coreboot is still in principle portable. This change will be the beginning of the removal of the portability. Before we start to make such a change we need to make a conscious decision that losing portability is what we want.
Part of "portability", in this case, is eventually moving to native 64-bit mode for the x86_64. I think we'll have to do that when we have machines with more memory than PAE can address.
thanks
ron