This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Empty loop elimination in 4.0 ?

From: Robert Dewar <dewar at adacore dot com>
To: Michael Veksler <VEKSLER at il dot ibm dot com>
Cc: Neil Booth <neil at daikokuya dot co dot uk>, gcc at gcc dot gnu dot org
Date: Mon, 10 Jan 2005 11:55:51 -0500
Subject: Re: Empty loop elimination in 4.0 ?
References: <OF1E4E9425.FA5EEE85-ON42256F85.0056BF23-42256F85.0057EF74@il.ibm.com>

Michael Veksler wrote:

Your claim that "Any warning can be triggered by... macro..." should
not apply to a standard (as in ISO/ANSI) macro like assert. My example
is a reasonable use of assert. You don't want to uglify this code by an
"#ifndef NDEBUG" block, do you?

Also, most macros can be written in a way that does not produce
warnings. Not with this warning message.


Not necessarily, it would often be possible to just put the whole loop
under control of a conditional that would make it disappear at the level
of deleting unreachable code.

References:
- Re: Empty loop elimination in 4.0 ?
  - From: Michael Veksler

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]