public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/36755] Avoid fork/exec in chmod intrinsic
Date: Thu, 12 Jan 2012 20:28:00 -0000	[thread overview]
Message-ID: <bug-36755-4-doxQ90OVY4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-36755-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36755

--- Comment #10 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-12 20:26:18 UTC ---
Author: burnus
Date: Thu Jan 12 20:26:10 2012
New Revision: 183137

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183137
Log:
2012-01-12  Tobias Burnus  <burnus@net-b.de>

        PR fortran/36755
        * intrinsic.texi (CHMOD): Extend a bit and remove statement
        that /bin/chmod is called.

2012-01-12  Tobias Burnus  <burnus@net-b.de>

        PR fortran/36755
        * intrinsics/chmod.c (chmod_func): Replace call to /bin/chmod


Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/intrinsic.texi
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/intrinsics/chmod.c


  parent reply	other threads:[~2012-01-12 20:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-36755-4@http.gcc.gnu.org/bugzilla/>
2011-11-09 22:25 ` burnus at gcc dot gnu.org
2012-01-12  8:06 ` burnus at gcc dot gnu.org
2012-01-12 17:32 ` burnus at gcc dot gnu.org
2012-01-12 19:26 ` burnus at gcc dot gnu.org
2012-01-12 20:28 ` burnus at gcc dot gnu.org [this message]
2012-01-12 20:33 ` burnus at gcc dot gnu.org
2008-07-07 20:58 [Bug libfortran/36755] New: " hjl dot tools at gmail dot com
2008-07-07 21:01 ` [Bug libfortran/36755] " pinskia at gcc dot gnu dot org
2008-07-09 20:35 ` hjl dot tools at gmail dot com
2008-07-09 20:49 ` pinskia at gcc dot gnu dot org
2008-07-09 21:18 ` hjl dot tools at gmail dot com
2008-07-09 21:22 ` hjl dot tools at gmail dot com
2008-07-09 21:25 ` hjl dot tools at gmail dot com
2008-09-28  0:03 ` steven 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=bug-36755-4-doxQ90OVY4@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).