Re: Possible Bug in GCC 4
Re: Possible Bug in GCC 4
- Subject: Re: Possible Bug in GCC 4
- From: David Fang <email@hidden>
- Date: Sun, 15 May 2005 21:41:40 -0400 (EDT)
Hi,
I'm experiencing similar problems with warnings about
uninitialized variables in the standard C++ library/headers, such as:
/usr/include/gcc/darwin/4.0/c++/bits/stl_pair.h:85: warning: 'SR.859' is
used uninitialized in this function
I believe these are auxiliary variables used by the intermediate
representation. This problem does not arise, however, with FSF's
gcc/g++-4.0, (nor earlier versions in the 3.x series). Suspecting that
something is terribly broken, I filed a bug report to Apple #4113854 last
week. I suggest filing a bug report so they have more cases to look at.
(I didn't take the time to reduce mine, I was in a hurry.)
There's a remote chance that our problems may be related, but even if
they're not, the behavior you see is still wrong.
> Maybe this is me, but this chunk of code:
>
> void test(model_type *model)
> {
> register int n;
> model_texture_type *texture;
>
> texture=model->textures;
>
> for (n=0;n!=max_model_texture;n++) {
> texture->bitmaps[0].name[0]=0x0;
> texture++;
> }
> }
>
> Returns: "warning: 'texture' is used uninitialized in this function"
>
> And there's no more corruption in the code. This code compiled fine
> in gcc 3.3.
David Fang
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden