http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #12 from Thomas Henlich
2011-05-15 09:26:02 UTC ---
(In reply to comment #11)
> (In reply to comment #9)
> > Thus, I do not see how one can solve this better than currently done.
>
> We might call system() in a separate thread instea
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #11 from Thomas Henlich
2011-05-15 09:13:28 UTC ---
(In reply to comment #9)
> Thus, I do not see how one can solve this better than currently done.
We might call system() in a separate thread instead of a separate process which
is m
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #10 from Tobias Burnus 2011-05-14
14:05:19 UTC ---
(In reply to comment #9)
> execl(, "sh", "-c", command, (char *)0);
> where is an unspecified pathname for the sh utility."
> Thus, for a POSIX system, one could use:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #9 from Tobias Burnus 2011-05-14
14:00:26 UTC ---
(In reply to comment #8)
> We fork() and then call system(), which forks again and runs a shell, then the
> shell exits, the forked process inside system() exits, the we exit our forke
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #8 from Thomas Henlich
2011-05-14 12:54:26 UTC ---
Maybe I'm wrong, but I'm not sure the current implementation of asynchronous
execution is very efficient (on Unix systems):
We fork() and then call system(), which forks again and ru
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #7 from Tobias Burnus 2011-05-14
11:52:34 UTC ---
EXECUTE_COMMAND_LINE(WAIT=.false.) now should no longer fail on systems without
fork().
Remains to do: Implement asynchronous execution on MinGW, cf. attachment 24228.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #6 from Tobias Burnus 2011-05-14
06:35:21 UTC ---
Author: burnus
Date: Sat May 14 06:35:18 2011
New Revision: 173748
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173748
Log:
2011-05-14 Tobias Burnus
PR fortran/48
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #5 from Tobias Burnus 2011-05-11
22:27:03 UTC ---
Patch: http://gcc.gnu.org/ml/fortran/2011-05/msg00087.html
Regarding the implementation of true async on Windows: One should also remember
to update
http://gcc.gnu.org/onlinedocs/gfor
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #4 from Tobias Burnus 2011-05-11
19:52:02 UTC ---
Created attachment 24228
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24228
async_system - example program for MinGW by Kai
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #3 from Tobias Burnus 2011-05-11
19:19:40 UTC ---
Created attachment 24226
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24226
Draft patch (untested)
(In reply to comment #2)
> The program is executed, as the called program "he
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
--- Comment #2 from Thomas Henlich
2011-05-11 16:38:52 UTC ---
The program is executed, as the called program "hello.exe" prints "Hello
world". After that hello.exe returns and the runtime error occurs.
Further testing shows that it is executed
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48961
Tobias Burnus changed:
What|Removed |Added
CC||burnus at gcc dot gnu.org
--- Comment #1
14 matches
Mail list logo
