public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "domob at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/44602] [F2008] EXIT: Jump to end of construct Date: Fri, 03 Sep 2010 08:02:00 -0000 [thread overview] Message-ID: <20100903080210.10449.qmail@sourceware.org> (raw) In-Reply-To: <bug-44602-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from domob at gcc dot gnu dot org 2010-09-03 08:02 ------- Subject: Bug 44602 Author: domob Date: Fri Sep 3 08:01:51 2010 New Revision: 163798 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=163798 Log: 2010-09-03 Daniel Kraft <d@domob.eu> PR fortran/44602 * gfortran.h (struct gfc_code): Renamed `whichloop' to `which_construct' as this is no longer restricted to loops. * parse.h (struct gfc_state_data): New field `construct'. * match.c (match_exit_cycle): Handle EXIT from non-loops. * parse.c (push_state): Set `construct' field. * resolve.c (resolve_select_type): Extend comment. * trans-stmt.c (gfc_trans_if): Add exit label. (gfc_trans_block_construct), (gfc_trans_select): Ditto. (gfc_trans_simple_do): Store exit/cycle labels on the gfc_code itself. (gfc_trans_do), (gfc_trans_do_while): Ditto. (gfc_trans_exit): Use new name `which_construct' instead of `whichloop'. (gfc_trans_cycle): Ditto. (gfc_trans_if_1): Use fold_build3_loc instead of fold_build3. 2010-09-03 Daniel Kraft <d@domob.eu> PR fortran/44602 * gfortran.dg/exit_2.f08; Adapt error messages. * gfortran.dg/exit_3.f08: New test. * gfortran.dg/exit_4.f08: New test. * gfortran.dg/exit_5.f03: New test. Added: trunk/gcc/testsuite/gfortran.dg/exit_3.f08 trunk/gcc/testsuite/gfortran.dg/exit_4.f08 trunk/gcc/testsuite/gfortran.dg/exit_5.f03 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/match.c trunk/gcc/fortran/parse.c trunk/gcc/fortran/parse.h trunk/gcc/fortran/resolve.c trunk/gcc/fortran/trans-stmt.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/exit_2.f08 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44602
next prev parent reply other threads:[~2010-09-03 8:02 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-20 19:58 [Bug fortran/44602] New: " burnus at gcc dot gnu dot org 2010-06-20 20:52 ` [Bug fortran/44602] " burnus at gcc dot gnu dot org 2010-06-21 7:41 ` burnus at gcc dot gnu dot org 2010-07-23 8:56 ` burnus at gcc dot gnu dot org 2010-08-30 12:08 ` domob at gcc dot gnu dot org 2010-08-30 18:27 ` domob at gcc dot gnu dot org 2010-09-03 8:02 ` domob at gcc dot gnu dot org [this message] 2010-09-03 8:04 ` domob at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100903080210.10449.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).