From: Wes Groleau <wesgroleau@despammed.com>
Subject: Re: Compiler default initialization of array types
Date: Fri, 18 Oct 2002 10:28:31 -0500
Date: 2002-10-18T10:28:31-05:00 [thread overview]
Message-ID: <AMVr9.1519$Bd4.11681@dfw-service2.ext.raytheon.com> (raw)
In-Reply-To: wcc3cr4vcti.fsf@shell01.TheWorld.com
> It turned out that initializing all those unused pointers to null was a
> serious performance problem. So I cheated: I declared the array as an
> array of integers (where the integer type was chosen to be the same size
> as a pointer), and used unchecked_conversion.
I'd use an overlay so that the array is the type I want.
next prev parent reply other threads:[~2002-10-18 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 12:55 Compiler default initialization of array types Sebastian
2002-10-17 13:10 ` Lutz Donnerhacke
2002-10-17 22:39 ` Peter Richtmyer
2002-10-17 13:42 ` Matthew Heaney
2002-10-17 23:57 ` Robert A Duff
2002-10-18 9:50 ` Larry Kilgallen
2002-10-18 14:40 ` Robert A Duff
2002-10-18 15:04 ` Larry Kilgallen
2002-10-18 13:36 ` Matthew Heaney
2002-10-18 15:28 ` Wes Groleau [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-17 14:23 Grein, Christoph
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox