public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43851] Add _gfortran_error_stop_numeric
Date: Thu, 20 May 2010 19:40:00 -0000 [thread overview]
Message-ID: <20100520194044.6612.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43851-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from jvdelisle at gcc dot gnu dot org 2010-05-20 19:40 -------
Subject: Bug 43851
Author: jvdelisle
Date: Thu May 20 19:40:30 2010
New Revision: 159638
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159638
Log:
2010-05-20 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR fortran/43851
* runtime/stop.c (stop_string): Make sure nothing is emitted for
blank stop.
Modified:
trunk/libgfortran/ChangeLog
trunk/libgfortran/runtime/stop.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43851
next prev parent reply other threads:[~2010-05-20 19:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 13:23 [Bug fortran/43851] New: " burnus at gcc dot gnu dot org
2010-04-22 13:31 ` [Bug fortran/43851] " burnus at gcc dot gnu dot org
2010-05-08 13:06 ` jvdelisle at gcc dot gnu dot org
2010-05-13 16:58 ` jvdelisle at gcc dot gnu dot org
2010-05-20 4:45 ` jvdelisle at gcc dot gnu dot org
2010-05-20 7:40 ` burnus at gcc dot gnu dot org
2010-05-20 13:33 ` jvdelisle at gcc dot gnu dot org
2010-05-20 19:40 ` jvdelisle at gcc dot gnu dot org [this message]
2010-05-23 0:01 ` jvdelisle at gcc dot gnu dot org
2010-06-06 6:10 ` jvdelisle at gcc dot gnu dot org
2010-07-19 13:48 ` burnus at gcc dot gnu dot org
2010-07-20 1:08 ` jvdelisle 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=20100520194044.6612.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: link
Be 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).