[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #17 from Thomas Koenig --- The fix will be in gcc 7.3 which is planned for release during the third week of January according to https://gcc.gnu.org/ml/gcc/2017-12/msg00102.html .

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #16 from Daan van Vugt --- Thanks guys :) What version will this be included in? On Thu, Dec 21, 2017 at 11:36 AM, tkoenig at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 >

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 Thomas Koenig changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #14 from Thomas Koenig --- Author: tkoenig Date: Thu Dec 21 10:34:35 2017 New Revision: 255940 URL: https://gcc.gnu.org/viewcvs?rev=255940=gcc=rev Log: 2017-12-21 Thomas Koenig Backport from trunk

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #13 from Thomas Koenig --- Author: tkoenig Date: Wed Dec 20 20:36:22 2017 New Revision: 255902 URL: https://gcc.gnu.org/viewcvs?rev=255902=gcc=rev Log: 2017-12-20 Thomas Koenig PR fortran/83436

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #12 from Thomas Koenig --- This also does not occur with 20171219. So, my guess would be that this was a side-effect of one of the recent patches, and was fixed in the meantime. I will commit a test case and then close this as

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #11 from Thomas Koenig --- The problem went away after updating to a clean trunk, re-bootstrapping and installing. Let's try gcc-7 next...

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #10 from Daan van Vugt --- (In reply to Steve Kargl from comment #8) > Thanks. Can you add the -v option to the above command line > and report the output (up to the ld line)? Do you have > more than one version of gfortran

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #9 from Thomas Koenig --- I am also seeing this. However, we have made some incompatible changes in the development phase of gcc-8. (We bumped the library version only once). This behavior could be the result of one of these

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #8 from Steve Kargl --- On Mon, Dec 18, 2017 at 08:00:57PM +, daanvanvugt at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 > > --- Comment #7 from Daan van Vugt --- > (In reply to kargl from comment

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #7 from Daan van Vugt --- (In reply to kargl from comment #6) > That is not gfortran. What happens if (1) you remove all of the > options and (2) you actually invoke gfortran? gfortran -g read_urandom.f90 -o read_urandom

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #5 from Daan van Vugt --- Okay, turned out I missed the critical lines in my bug report... Could you try again with this example? module mod_random_seed implicit none contains !> Read an int from /dev/urandom subroutine

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #3 from Jerry DeLisle --- Daan, Works for me here. It could be that the compiler is trying to use a wrong library version. Did you build gfortran yourself? What system are you running on?

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #2 from Jerry DeLisle --- (In reply to Thomas Koenig from comment #1) > I can not check this right. Jerry, van you take a look? Looking

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 Thomas Koenig changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org,