public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tobi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/18540] Jumping into blocks gives error rather than warning Date: Wed, 18 Jan 2006 20:54:00 -0000 [thread overview] Message-ID: <20060118205452.23720.qmail@sourceware.org> (raw) In-Reply-To: <bug-18540-9236@http.gcc.gnu.org/bugzilla/> ------- Comment #18 from tobi at gcc dot gnu dot org 2006-01-18 20:54 ------- Subject: Bug 18540 Author: tobi Date: Wed Jan 18 20:54:49 2006 New Revision: 109914 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109914 Log: PR fortran/18540 PR fortran/18937 * gfortran.h (BBT_HEADER): Move definition up. (gfc_st_label): Add BBT_HEADER, remove 'prev' and 'next'. * io.c (format_asterisk): Adapt initializer. * resolve.c (resolve_branch): Allow FORTRAN 66 cross-block GOTOs as extension. * symbol.c (compare_st_labels): New function. (gfc_free_st_label, free_st_labels, gfc_get_st_label): Convert to using balanced binary tree. * decl.c (match_char_length, gfc_match_old_kind_spec): Do away with 'cnt'. (warn_unused_label): Adapt to binary tree. * match.c (gfc_match_small_literal_int): Only set cnt if non-NULL. * primary.c (match_kind_param): Do away with cnt. Also converted the ChangeLog to use latin1 characters. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/decl.c trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/io.c trunk/gcc/fortran/match.c trunk/gcc/fortran/primary.c trunk/gcc/fortran/resolve.c trunk/gcc/fortran/symbol.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18540
next prev parent reply other threads:[~2006-01-18 20:54 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-18540-9236@http.gcc.gnu.org/bugzilla/> 2006-01-07 0:16 ` pinskia at gcc dot gnu dot org 2006-01-08 21:30 ` steven at gcc dot gnu dot org 2006-01-08 21:32 ` steven at gcc dot gnu dot org 2006-01-08 21:33 ` steven at gcc dot gnu dot org 2006-01-08 21:42 ` tobi at gcc dot gnu dot org 2006-01-08 21:45 ` steven at gcc dot gnu dot org 2006-01-08 21:54 ` steven at gcc dot gnu dot org 2006-01-08 22:16 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2006-01-08 22:23 ` steven at gcc dot gnu dot org 2006-01-08 22:53 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2006-01-09 16:46 ` tobi at gcc dot gnu dot org 2006-01-09 16:50 ` tobi at gcc dot gnu dot org 2006-01-09 18:35 ` steven at gcc dot gnu dot org 2006-01-09 18:56 ` tobi at gcc dot gnu dot org 2006-01-14 19:03 ` tobi at gcc dot gnu dot org 2006-01-18 20:54 ` tobi at gcc dot gnu dot org [this message] 2006-01-18 21:08 ` tobi at gcc dot gnu dot org 2006-01-25 22:34 ` tobi at gcc dot gnu dot org 2006-01-25 23:38 ` tobi at gcc dot gnu dot org 2006-01-26 10:15 ` tobi at gcc dot gnu dot org 2006-01-28 20:59 ` pinskia at gcc dot gnu dot org 2004-11-18 11:26 [Bug fortran/18540] New: " paul dot richard dot thomas at cea dot fr 2004-11-18 12:31 ` [Bug fortran/18540] " pinskia at gcc dot gnu dot org 2005-01-06 14:42 ` tobi at gcc dot gnu dot org 2005-01-06 18:17 ` paulthomas2 at wanadoo dot fr 2005-01-06 18:19 ` pinskia at gcc dot gnu dot org 2005-03-24 12:02 ` fxcoudert 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=20060118205452.23720.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).