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: Code optimization: warning for code that hangs

From: Robert Dewar <dewar at adacore dot com>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: gcc-help at gcc dot gnu dot org, "Peter A. Felvegi" <petschy at praire-chicken dot com>, gcc at gcc dot gnu dot org
Date: Sun, 24 Jun 2012 17:53:15 -0400
Subject: Re: Code optimization: warning for code that hangs
References: <4FE5B390.1000203@praire-chicken.com> <mcrsjdmnizh.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <CAFiYyc0rG=WpPf9Huee-oAsEfrjT0fH8iUG+GDzKbB4a-wGVFw@mail.gmail.com>

On 6/24/2012 11:22 AM, Richard Guenther wrote:

I suppose I think it would be reasonable to issue a -Wall warning for
code like that.  The trick is detecting it.  Obviously there is nothing
wrong with a recursive call.  What is different here is that the
recursive call is unconditional.  I don't see a way to detect that
without writing a specific warning pass to look for that case.

Ada has this warning, and it has proved useful!

References:
- Code optimization: warning for code that hangs
  - From: Peter A. Felvegi
- Re: Code optimization: warning for code that hangs
  - From: Ian Lance Taylor
- Re: Code optimization: warning for code that hangs
  - From: Richard Guenther

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