This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: Why is chmod in libgfortran implemented as fork/exec?
- From: FX <fxcoudert at gmail dot com>
- To: H.J. Lu <hjl dot tools at gmail dot com>
- Cc: fxcoudert at gcc dot gnu dot org, "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>
- Date: Mon, 7 Jul 2008 22:53:43 +0200
- Subject: Re: Why is chmod in libgfortran implemented as fork/exec?
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=KwtRYx6X0qlkGElTjx8CF98i6sv70r+QtADfPToJig4=; b=Ita51vvEM3bsH3GuyNKPhQfLhg3uJz1EQNIbsse/GwWAex2FB8vQkSw6qWYpd/q2iu gqS14fr4VqQ83u9fHAjIAAQ7bJJ1JYBYvXniHAUi0MVlqiJP/xeG1ZUeYFSMkiFxefPZ bRuWuEWpT8UOTEmI1erhqFQ/VBL9SM9dgxjpc=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=Ps6HOZ4Ungx/8bnOIJhV+NO0TS6nhlcQvEsIr2uoV62lG69Fis+rrKXimZzWNytppM hF5PF9lvvqYqWBnwW/XK/p7rR4dPsRR72HvccgKrjUgl0PBz5+K8BwfL+NxAXx0xG4I6 1gVf56nl7qzjgO+a0FBB2QPsOx9sEto0DPg6w=
- References: <6dc9ffc80807071344j5f9ff7l62766669744fc429@mail.gmail.com>
It may be a dump question. Why does libgfortran implement chmod
intrinsic
with fork/exec? Why can't it call chmod () directly?
Because if we called chmod(), we have to translate symbolic modes
into absolute ones, so I went for the easy option. Patches changing
this behaviour are of course welcome.
FX
--
François-Xavier Coudert
http://www.homepages.ucl.ac.uk/~uccafco/