Re: Compiling C++ modules

linux-os (Dick Johnson)
2006-05-02T11:42:00Z

On Tue, 2 May 2006, Avi Kivity wrote:

> Martin Mares wrote:
>> Hello!
>>
>>
>>> Perhaps people who developed kernel-level code in _both_ C and C++ would
>>> be qualified to speculate on that (I have, but apparently I don't have a
>>> clue).
>>>
>>
>> Well, what about just showing an example of kernel code in C++, which
>> you consider nice?
>>
>
> I don't have access to that code (which was closed source anyway).
>
> But it executed C++ code within a few cycles of entering the reset
> vector (no standard BIOS), including but not limited to: programming the
> memory controller (430MX chipset), servicing interrupts, hardware
> accelerated 2D graphics (C&T 65550), IDE driver, simple filesystem,
> simple windowing GUI, network driver (Tulip) etc.
>

Oh wow! I'm impressed. You, know back in the '50s we did something
like that. It was a dynamic abacus for fast math. Since it's
proprietary, I can't disclose its exact nature. It's even used
by the CIA.

> More recently I participated in writing a filesystem in C++. That's in
> userspace, but many of the techniques used in writing kernel code are
> necessary there (extreme robustness, can't assume infinite memory,
> locking, etc.)

Sure, kernel code is probably written using symbols, too. It's a
lot like user-space as well.

>
> There are C++ embedded kernels in http://www.zipworld.com.au/~akpm/ and
> http://ecos.sourceware.org/, but I haven't looked at them, so I can't
> say whether I consider them nice or not.
>

While you are at it, look at:

http://www.google.com/search?hl=en&q=bullshit

> --
> error compiling committee.c: too many arguments to function
>

Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.4 on an i686 machine (5592.89 BogoMips).
New book: http://www.lymanschool.com
_
\x1a\x04

****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.