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 libfortran/48960] OPEN statement modifies NEWUNIT variable on error Date: Tue, 25 Dec 2012 04:52:00 -0000 [thread overview] Message-ID: <bug-48960-4-na3Sw5lrbp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48960-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48960 --- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2012-12-25 04:52:04 UTC --- A slight modification and still testing. @@ -859,6 +856,10 @@ st_open (st_parameter_open *opp) else already_open (opp, u, &flags); } - + + if ((opp->common.flags & IOPARM_OPEN_HAS_NEWUNIT) + && (opp->common.flags & IOPARM_LIBRETURN_MASK) == IOPARM_LIBRETURN_OK) + *opp->newunit = opp->common.unit; + library_end (); }
next prev parent reply other threads:[~2012-12-25 4:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-11 8:51 [Bug libfortran/48960] New: " thenlich at users dot sourceforge.net 2011-05-12 18:39 ` [Bug libfortran/48960] " jvdelisle at gcc dot gnu.org 2012-12-25 4:24 ` jvdelisle at gcc dot gnu.org 2012-12-25 4:52 ` jvdelisle at gcc dot gnu.org [this message] 2012-12-26 18:12 ` jvdelisle at gcc dot gnu.org 2012-12-27 6:37 ` jvdelisle at gcc dot gnu.org 2012-12-27 20:14 ` jvdelisle at gcc dot gnu.org 2012-12-27 20:15 ` 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-48960-4-na3Sw5lrbp@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: 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).