This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc-2.95 OK, gcc-{3,4}.X not OK
- From: Andrew Haley <aph at redhat dot com>
- To: Andris Kalnozols <andris at hpl dot hp dot com>
- Cc: gcc <gcc at gcc dot gnu dot org>
- Date: Fri, 01 Jan 2010 11:47:54 +0000
- Subject: Re: gcc-2.95 OK, gcc-{3,4}.X not OK
- Followup-to: GCC-help,<gcc-help@gcc.gnu.org>
- References: <201001010544.VAA00734@nasdaq.hpl.hp.com>
[redir to gcc-help]
On 01/01/2010 05:44 AM, Andris Kalnozols wrote:
> If the bug was a basic programming error, one would expect a
> runtime failure (dereferencing a NULL pointer) no matter which
> compiler was used.
I would not expect that, and I have no idea whay you would. Undefined
behaviour can happen in any way: maybe the program appears to run
correctly, maybe it faults.
> The application compiles cleanly with no warnings using "-Wall".
> Were there any transition issues with the newer gcc compilers of
> which I may not be aware?
No. As you've done the obvious first stage (using -Wall) you now
should run your program under Valgrind, assuming that it is available
on your system.
Andrew.