[lkml]   [2006]   [Apr]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Compiling C++ modules
On Tue, 25 Apr 2006, Kyle Moffett wrote:
> On Apr 25, 2006, at 03:08:02, Avi Kivity wrote:
> > {
> > spinlock_t::guard foo_guard(foo_lock);
> > Foo item1;
> > Foo item2;
> > }
> Let me point out _again_ how unobvious and fragile the flow of code there is.
> Not to mention the fact that the C++ compiler can easily notice that item1 and
> item2 are never used and optimize them out entirely. You also totally missed

Only if the constructor and destructor of Foo is inline. Else there may be side

This is commonly used for function scope debugging, and I never saw the
compiler optimize away any of these debug objects, even if they look unused to
the casual reader.



Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-04-25 19:58    [W:0.111 / U:1.456 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site