public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/24636] gfortran: STOP without stop-code too noisy, regression w.r.t. g77 Date: Fri, 04 Nov 2005 22:18:00 -0000 [thread overview] Message-ID: <20051104221826.21877.qmail@sourceware.org> (raw) In-Reply-To: <bug-24636-6318@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from kargl at gcc dot gnu dot org 2005-11-04 22:18 ------- Subject: Bug 24636 Author: kargl Date: Fri Nov 4 22:18:22 2005 New Revision: 106509 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106509 Log: PR fortran/24636 * match.c (gfc_match_stopcode): Set stop_code = -1. * runtime/stop.c (stop_numeric): Use stop_code = -1. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/match.c trunk/libgfortran/ChangeLog trunk/libgfortran/runtime/stop.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24636
next prev parent reply other threads:[~2005-11-04 22:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-02 14:10 [Bug fortran/24636] New: " anlauf at gmx dot de 2005-11-02 14:59 ` [Bug fortran/24636] " pinskia at gcc dot gnu dot org 2005-11-02 18:28 ` kargl at gcc dot gnu dot org 2005-11-04 22:18 ` kargl at gcc dot gnu dot org [this message] 2005-11-04 23:21 ` kargl at gcc dot gnu dot org 2005-11-04 23:24 ` kargl 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=20051104221826.21877.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).