GCC 3.3 error worth a bug report?
GCC 3.3 error worth a bug report?
- Subject: GCC 3.3 error worth a bug report?
- From: Dirk Stegemann <email@hidden>
- Date: Fri, 2 Jun 2006 03:39:01 +0200
Hi,
I encountered an compiler (more precisely: a preprocessor) bug in GCC
3.3 which seems to be fixed in GCC 4.
I need GCC 3.3 to create binaries which run on Mac OS X 10.2.x and
later.
It is easy to work-around that bug; is it worth to write a bug report
anyway...?
That's the code which compiles fine with GCC 4.0, but fails with GCC
3.3:
----- start of file "main.m" -----
int main(int argc, const char *argv[])
{
return 0;
}
#if 1
// this '#if / #else / #endif' branch will be evaluated by the
preprocessor
#warning "This warning is read and displayed by the preprocessor
as expected"
#else
// this '#if / #else / #endif' branch should not be evaluated by
the preprocessor
1=2 // won't produce error because ignored by the compiler
#warning "This warning is ignored by the preprocessor"
#warning "This warning *is not* ignored by the preprocessor and
bails due to missing terminating character...
#endif
----- end of file "main.m" -----
[tbook:~] me% /usr/bin/gcc-4.0 main.m
main.m:9:6: warning: #warning "This warning is read and displayed by
the preprocessor as expected"
[tbook:~] me% /usr/bin/gcc-3.3 main.m
main.m:9:6: warning: #warning "This warning is read and displayed by
the preprocessor as expected"
main.m:16:14: missing terminating " character
Regards,
Dirk Stegemann
_______________________________________________
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