On Sat, Jun 23, 2012 at 5:30 PM, Ian Lance Taylor wrote:
> "Peter A. Felvegi" writes:
>
>> My question is: wouldn't it be possible to print a warning when a jmp
>> to itself or trivial infinite recursion is generated? The code
>> compiled fine w/ -Wall -Wextra -Werror w/ 4.6 and 4.7.
>
> This que
"Peter A. Felvegi" writes:
>>> My question is: wouldn't it be possible to print a warning when a jmp
>>> to itself or trivial infinite recursion is generated? The code
>>> compiled fine w/ -Wall -Wextra -Werror w/ 4.6 and 4.7.
Note that if the target architecture is a microcontroller, an endless
lo
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
On 6/24/2012 12:09 PM, Ángel González wrote:
"Peter A. Felvegi" writes:
My question is: wouldn't it be possible to print a warning when a jmp
to itself or trivial infinite recursion is generated? The code
compiled fine w/ -Wall -Wextra -Werror w/ 4.6 and 4.7.
Note that if the target architectur
On 24/06/12 23:54, Robert Dewar wrote:
On 6/24/2012 12:09 PM, Ángel González wrote:
"Peter A. Felvegi" writes:
My question is: wouldn't it be possible to print a warning when a jmp
to itself or trivial infinite recursion is generated? The code
compiled fine w/ -Wall -Wextra -Werror w/ 4.6 and 4
Snapshot gcc-4.8-20120624 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20120624/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
