--- Comment #5 from pcarlini at suse dot de 2007-09-24 18:01 ---
Isn't the C++ front-end also fixed? I can confirm that currently the error
comes from cp_parser_jump_statement. In general, the check in build_bc_goto is
apparently dead: I have been able to build and test with gcc_assert
--- Comment #4 from bangerth at math dot tamu dot edu 2006-10-12 01:25
---
Subject: Re: bad break/continue is not dectected until the
gimplifier
> Yes but this semantics anyalsis is done while gimplifing and not while
> parsing.
But I get the message also when using -fsyntax-only.
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-10-12 01:12 ---
(In reply to comment #2)
> What exactly is the problem here? I get this as an error message:
>
> g/x> /home/bangerth/bin/gcc-4.2-pre/bin/c++ -c x.cc
> x.cc: In function ‘void f()’:
> x.cc:3: error: break statement n
--- Comment #2 from bangerth at dealii dot org 2006-10-12 01:08 ---
What exactly is the problem here? I get this as an error message:
g/x> /home/bangerth/bin/gcc-4.2-pre/bin/c++ -c x.cc
x.cc: In function ‘void f()’:
x.cc:3: error: break statement not within loop or switch
That seems ac
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-03-18 16:29 ---
This is only for the C++ front-end, the C front-end was fixed a while back.
Continue is the same issue
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
-
