Re: gcc3.3.3 vs gcc4.0.0

5 msg	__DBL_HAS_DENORM__ et al required in recent lib...
2 msg	Seg fault
2 msg	problem with solaris compiler
3 msg	Looking for GNU toolchain solution for ARM
1 msg	Remove redundant includes from C, C++ source fi...
1 msg	build toolchain for ARM target
11 msg	Strict aliasing and pointers to functions
3 msg	typeinfo problem (bug?)
2 msg	Phase Ordering of Scheduling and Allocation in GCC
21 msg	Comments in assember output
15 msg	Problem with the string

gcc3.3.3 vs gcc4.0.0
\ jayashree.nair (24 Nov 2006)
. \ Tim Prince (24 Nov 2006)

3 msg	Help for warning: type attributes are honored o...
2 msg	help compiling java code
1 msg	32 bit Global Offset Table on MIPS: howto?
1 msg	Removal of GCC/GAS tailing .code segment NOP pa...
2 msg	compilation issues with gcc v3.2.3p3--building ...
3 msg	ARM GCC COMPILATION ERROR
4 msg	problem with a structure nested within a template
1 msg	Another clobber problem

Subject:	Re: gcc3.3.3 vs gcc4.0.0
Group:	Gcc-help
From:	Tim Prince
Date:	24 Nov 2006

jayashree.nair wrote:
> In one m/c with gcc3.3.3 installed, I have no problem in compiling and
> linking.
>
> In another m/c with gcc4.0.0 installed, I was getting the following error:
>
> p15.c:4857: error: conflicting types for 'logerror'
> p15.c:4812: error: previous implicit declaration of 'logerror' was here
>
> logerror() was not declared in the p15.pc file.
>
> So I changed the code and declared the method before my main routine and it
> solved my problem.
>
> What I would like to know is that why is this giving me such different
> results with the different versions.

Recent gcc versions have become much more thorough about checking for
these errors, which might or might not have generated visible problems
if ignored. It looks like the policy has changed from passing over it,
if the compiler can't tell whether legacy code is a problem, to
strictness under the same conditions.
I have run into cases where legacy code fails inscrutably on Windows,
and the new gcc error checking pointed out the problem.