public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jpr at csc dot fi" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/35064] New: gfortran internal write leaks windows handles & memory Date: Sun, 03 Feb 2008 13:47:00 -0000 [thread overview] Message-ID: <bug-35064-11807@http.gcc.gnu.org/bugzilla/> (raw) Hi, We have a somewhat serious problem with gfortran on x86/mingw32 system: program test implicit none character(len=10) :: string integer :: m,n do m = 1,1000 do n = 1,10000 write(string,*) 'nice' end do print *,'Check memory and handles and press ENTER...' call flush read(*,*) end do end program test Start the task manager and run the small program above to see memory and windows handle usage (1 / internal write) to skyrocket. The fortran versions i see this include the latest 4.3 & the mingw 4.2_sjlj versions at least: $ gfortran -v Using built-in specs. Target: i386-pc-mingw32 Configured with: ../trunk/configure --prefix=/mingw --enable-languages=c,fortran --with-gmp=/home/FX/local --with-ld=/mingw/bin/ld --with-as=/mingw/bin/as --disable-werror --enable-bootstrap --enable-threads --disable-nls --build=i386-pc-mingw32 --enable-libgomp --disable-shared Thread model: win32 gcc version 4.3.0 20080127 (experimental) [trunk revision 131883] (GCC) Regards, Juha -- Summary: gfortran internal write leaks windows handles & memory Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jpr at csc dot fi GCC host triplet: i386-mingw32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35064
next reply other threads:[~2008-02-03 13:47 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-03 13:47 jpr at csc dot fi [this message] 2008-02-03 14:38 ` [Bug fortran/35064] " jpr at csc dot fi
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-35064-11807@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).