From: Thomas Lahoda <tlahoda@tmctechnologies.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Compiling C++ kernel module + Makefile
Date: 20 Jan 2004 13:38:10 +0000 [thread overview]
Message-ID: <1074605893.1066.10.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.53.0401201306030.12044@chaos>
Not that I'm calling for the use of c++ in a kernel, but if you're going
to argue against it you should get your c++ example correct. You are
erroneously using fstream to get your cout. In c++, cout is an ostream
object. With the above correction compiled using g++ 3.3.2 I get the
following:
-rwxrwxr-x 1 tlahoda tlahoda 3820 Jan 20 13:27 hello+
-rwxrwxr-x 1 tlahoda tlahoda 2760 Jan 20 13:30 helloc
On Tue, 2004-01-20 at 18:10, Richard B. Johnson wrote:
> On Tue, 20 Jan 2004, Zan Lynx wrote:
>
> > On Tue, 2004-01-20 at 08:20, Richard B. Johnson wrote:
> > > Nevertheless, I provide three programs, one written in
> > > C, the other in C++ and the third in assembly. A tar.gz
> > > file is attached for those interested.
> > >
> > > -rwxr-xr-x 1 root root 57800 Jan 20 10:16 hello+
> > > -rwxr-xr-x 1 root root 460 Jan 20 10:16 helloa
> > > -rwxr-xr-x 1 root root 2948 Jan 20 10:16 helloc
> > >
> > > The code size, generated from assembly is 460 bytes.
> > > The code size, generated from C is 2,948 bytes.
> > > The code size, generated from C++ is 57,800 bytes.
> > >
> > > Clearly, C++ is not the optimum language for writing
> > > a "Hello World" program.
> >
> > I like C++ and hate to see it so unfairly maligned. Here's a much
> > better example:
> >
> > Makefile:
> > helloc: hello.c
> > gcc -Os -s -o helloc hello.c
> >
> > hellocpp: hello.cpp
> > g++ -Os -fno-rtti -fno-exceptions -s -o hellocpp hello.cpp
> >
> > Both programs contain exactly the same code: one main() function using
> > puts("Hello world!").
> >
> > # ls -l
> > -rwxrwxr-x 1 jbriggs jbriggs 2840 Jan 20 10:02 helloc
> > -rwxrwxr-x 1 jbriggs jbriggs 2948 Jan 20 10:06 hellocpp
> >
> > 108 extra bytes is hardly the end of the world.
> > --
> > Zan Lynx <zlynx@acm.org>
> >
>
> Well you just fell into the usual trap of using the "C-like"
> capabilities of C++ to call a 'C' function. If you are going
> to use 'C' library functions, you don't use an object-oriented
> language to call them. That is using a hatchet like a hammer.
>
> I did not malign C++. I used it as it was designed and let
> the chips fall where they may.
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
> Note 96.31% of all statistics are fiction.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-01-20 18:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 21:09 Ashish sddf
2004-01-16 22:07 ` Richard B. Johnson
2004-01-17 12:59 ` Bart Samwel
2004-01-19 13:46 ` Richard B. Johnson
2004-01-19 17:40 ` Bart Samwel
2004-01-19 18:39 ` Richard B. Johnson
2004-01-19 20:02 ` Bart Samwel
2004-01-19 20:37 ` Richard B. Johnson
2004-01-19 21:24 ` Bart Samwel
2004-01-20 15:20 ` Richard B. Johnson
2004-01-20 17:34 ` Zan Lynx
2004-01-20 18:10 ` Richard B. Johnson
2004-01-20 13:38 ` Thomas Lahoda [this message]
2004-01-21 2:24 ` Michael Clark
2004-01-20 18:16 ` Chris Friesen
2004-01-21 17:01 ` Giuliano Pochini
2004-01-21 17:16 ` Bart Samwel
2004-01-20 0:59 ` Robin Rosenberg
2004-01-20 6:46 ` Linus Torvalds
2004-01-20 7:32 ` Robin Rosenberg
2004-01-20 10:46 ` Bart Samwel
2004-01-20 5:29 ` Valdis.Kletnieks
2004-01-20 9:48 ` Bart Samwel
2004-01-16 22:40 ` Sam Ravnborg
2004-01-19 13:21 Petr Vandrovec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1074605893.1066.10.camel@localhost.localdomain \
--to=tlahoda@tmctechnologies.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®