This is the mail archive of the
mailing list for the GCC project.
Re: Is this a gcc bug?
- To: Joern Rennecke <amylaar at cambridge dot redhat dot com>
- Subject: Re: Is this a gcc bug?
- From: Geoff Keating <geoffk at geoffk dot org>
- Date: 14 Jan 2001 02:19:59 -0800
- CC: gcc at gcc dot gnu dot org
- References: <200101140245.f0E2jhi15832@phal.cambridge.redhat.com>
Joern Rennecke <firstname.lastname@example.org> writes:
> > Warning: Multiple uses of 'x' in statement modifying 'x'. Statement results
> > are implementation dependant. Randomizer invoked to minimize predicability.
> > Attempting to reformat all Hard Drives: Failed.
> The standard only talks about undefined behaviour at program run time, not
> at compile time.
The standard doesn't distinguish between 'run time' and 'compile
> Of course, you could argue that the standard doesn't forbid you to reformat
> all hard drives at compilation time, but then, you could do that irrespective
> of the input program. I'd say that's a quality of implementation issue.
I agree. It's better that the compiler doesn't do weird stuff, no
matter what the input---the compiler should not dump core, should not
crash your system, and should always print a helpful error message on
invalid input. Indeed, this is a QoI issue.
- Geoffrey Keating <email@example.com>