public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46079] New: ABI for empty stop statement broken
Date: Tue, 19 Oct 2010 02:30:00 -0000 [thread overview]
Message-ID: <bug-46079-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46079
Summary: ABI for empty stop statement broken
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: jvdelisle@gcc.gnu.org
Prior to 4.6 a an empty STOP is translated into:
_gfortran_stop_numeric (-1);
The runtime looks for -1 as a signal for an empty STOP and just exist quietly.
However, this statement, if run inadvertently with the 4.6 library will not
exit quietly and will emit "STOP -1" with a -1 exit code. A -1 is a valid STOP
code with later Fortran standards. I will post a proposed patch.
next reply other threads:[~2010-10-19 2:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 2:30 jvdelisle at gcc dot gnu.org [this message]
2010-10-19 2:46 ` [Bug fortran/46079] " jvdelisle at gcc dot gnu.org
2010-10-19 11:21 ` [Bug fortran/46079] [4.6 Regression] " burnus at gcc dot gnu.org
2010-10-19 13:07 ` jvdelisle at gcc dot gnu.org
2010-10-20 8:18 ` jakub at gcc dot gnu.org
2010-10-21 0:45 ` jvdelisle at gcc dot gnu.org
2010-10-21 0:48 ` jvdelisle at gcc dot gnu.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=bug-46079-4@http.gcc.gnu.org/bugzilla/ \
--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).