public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libf2c/18874] New: ? in namelist read leads to I/O recursion
@ 2004-12-07 16:29 Thomas dot Koenig at online dot de
  2004-12-07 19:01 ` [Bug libf2c/18874] " pinskia at gcc dot gnu dot org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: Thomas dot Koenig at online dot de @ 2004-12-07 16:29 UTC (permalink / raw)
  To: gcc-bugs

Typing "?" for a namelist input is supposed to
yield a description of the input variables on
standard output.  This doesn't work with g77:

$ g77 -v
Reading specs from /usr/lib/gcc-lib/ia64-redhat-linux/3.2.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit --host=ia64-redhat-linux
Thread model: posix
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-42)
$ ./a.out
$ cat nl.f
      program main
      namelist /nl/ a
      read (*,nl)
      print *,a
      end
$ g77 nl.f && a.out
?
I/O recursion: I/O started while already doing I/O
apparent state: unit 5 (unnamed)
last format: list io
lately reading direct formatted external IO
Aborted

-- 
           Summary: ? in namelist read leads to I/O recursion
           Product: gcc
           Version: 3.2.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libf2c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: Thomas dot Koenig at online dot de
                CC: gcc-bugs at gcc dot gnu dot org


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug libf2c/18874] ? in namelist read leads to I/O recursion
  2004-12-07 16:29 [Bug libf2c/18874] New: ? in namelist read leads to I/O recursion Thomas dot Koenig at online dot de
@ 2004-12-07 19:01 ` pinskia at gcc dot gnu dot org
  2004-12-08  1:38 ` bdavis at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-12-07 19:01 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-12-07 19:01 -------
I don't know if any libf2c bugs are going to be fixed any more since 4.0.0 uses a different library for 
fortran library.

-- 


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug libf2c/18874] ? in namelist read leads to I/O recursion
  2004-12-07 16:29 [Bug libf2c/18874] New: ? in namelist read leads to I/O recursion Thomas dot Koenig at online dot de
  2004-12-07 19:01 ` [Bug libf2c/18874] " pinskia at gcc dot gnu dot org
@ 2004-12-08  1:38 ` bdavis at gcc dot gnu dot org
  2005-06-19 14:45 ` pinskia at gcc dot gnu dot org
  2005-09-26  0:56 ` pinskia at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: bdavis at gcc dot gnu dot org @ 2004-12-08  1:38 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From bdavis at gcc dot gnu dot org  2004-12-08 01:38 -------
i would imagine that the number of bugs fixed in g77 / libf2c will be small, but
gcc3.4.X will be actively supported for a while.

having the bugs reported let's users know that this is a known problem.  maybe
someone will fix it...even if it is not included in a release, the user might
want the fix.

so, my opinion, if bugs are found in g77/libf2c, they should be reported.   if
someone wants to fix them, great, but not likely due to most effort going in to
gfortran.


--bud davis

 

-- 


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug libf2c/18874] ? in namelist read leads to I/O recursion
  2004-12-07 16:29 [Bug libf2c/18874] New: ? in namelist read leads to I/O recursion Thomas dot Koenig at online dot de
  2004-12-07 19:01 ` [Bug libf2c/18874] " pinskia at gcc dot gnu dot org
  2004-12-08  1:38 ` bdavis at gcc dot gnu dot org
@ 2005-06-19 14:45 ` pinskia at gcc dot gnu dot org
  2005-09-26  0:56 ` pinskia at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-06-19 14:45 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-06-19 14:45 -------
This works with me in 3.4.0.

-- 


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug libf2c/18874] ? in namelist read leads to I/O recursion
  2004-12-07 16:29 [Bug libf2c/18874] New: ? in namelist read leads to I/O recursion Thomas dot Koenig at online dot de
                   ` (2 preceding siblings ...)
  2005-06-19 14:45 ` pinskia at gcc dot gnu dot org
@ 2005-09-26  0:56 ` pinskia at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-09-26  0:56 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-09-26 00:56 -------
Fixed in 3.4.0.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|---                         |3.4.0


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2005-09-26  0:56 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-12-07 16:29 [Bug libf2c/18874] New: ? in namelist read leads to I/O recursion Thomas dot Koenig at online dot de
2004-12-07 19:01 ` [Bug libf2c/18874] " pinskia at gcc dot gnu dot org
2004-12-08  1:38 ` bdavis at gcc dot gnu dot org
2005-06-19 14:45 ` pinskia at gcc dot gnu dot org
2005-09-26  0:56 ` pinskia at gcc dot gnu dot org

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).