public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Robert.C.Haskell@rolls-royce.com
To: gcc-gnats@gcc.gnu.org
Subject: fortran/1832: -list directed i/o overflow hangs, -fbounds-check doesn't detect
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <20010201181749.20100.qmail@sourceware.cygnus.com> (raw)

>Number:         1832
>Category:       fortran
>Synopsis:       -list directed i/o overflow hangs, -fbounds-check doesn't detect
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 01 10:26:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Bob Haskell
>Release:        g77 version 2.95.3 19991030 (prerelease)
>Organization:
>Environment:
(from FSF-g77 version 0.5.25 19991030 (prerelease))
Driving: g77 -v t.f -o t -lg2c -lm
Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux/2.95.3/specs
gcc version 2.95.3 19991030 (prerelease)
 /usr/lib/gcc-lib/i586-mandrake-linux/2.95.3/f771 t.f -quiet -dumpbase
t.f -version -fversion -o /tmp/ccHM9EZy.s
GNU F77 version 2.95.3 19991030 (prerelease) (i586-mandrake-linux)
compiled by GNU C version 2.95.3 19991030 (prerelease).
GNU Fortran Front End version 0.5.25 19991030 (prerelease)
 as -V -Qy -o /tmp/ccebCcp0.o /tmp/ccHM9EZy.s
GNU assembler version 2.10.90 (i586-mandrake-linux) using BFD version
2.10.0.24
 /usr/lib/gcc-lib/i586-mandrake-linux/2.95.3/collect2 -m elf_i386
-dynamic-linker /lib/ld-linux.so.2 -o t /usr/lib/crt1.o /usr/lib/crti.o
/usr/lib/gcc-lib/i586-mandrake-linux/2.95.3/crtbegin.o
-L/usr/lib/gcc-lib/i586-mandrake-linux/2.95.3
-L/usr/i586-mandrake-linux/lib /tmp/ccebCcp0.o -lg2c -lm -lgcc -lc -lgcc
/usr/lib/gcc-lib/i586-mandrake-linux/2.95.3/crtend.o /usr/lib/crtn.o

>Description:
The following program has a coding mistake - internal i/o overflow in
the write statement.  This program will generate a runtime error message
when compiled with the HP-UX and AIX fortran compilers.  When compiled
using g77, program execution will hang at the write statement. 
Compiling with the -fbounds-check has no effect.  If the format is
changed to "(2a)", then the program will run without any messages.  But
it ought to generate a runtime error about the overflow, at least when
compiled with -fbounds-check.
>How-To-Repeat:

      implicit none

      character*120 file
      character*5 string

      file = "c:/dos/adir/bdir/cdir/text.doc"

      write( string, * ) "a ", file
      print *, string

      stop
      end

>Fix:
not known
>Release-Note:
>Audit-Trail:
>Unformatted:
>From lerdsuwa@gcc.gnu.org Sun Apr 01 00:00:00 2001
From: lerdsuwa@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/750
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010220095600.1025.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg01522.html
Content-length: 598

The following reply was made to PR c++/750; it has been noted by GNATS.

From: lerdsuwa@gcc.gnu.org
To: arasu@india.ti.com, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/750
Date: 20 Feb 2001 09:49:59 -0000

 Synopsis: "Field out of range" Error while using g++ on HP 10.20
 
 State-Changed-From-To: open->feedback
 State-Changed-By: lerdsuwa
 State-Changed-When: Tue Feb 20 01:49:59 2001
 State-Changed-Why:
     Please submit a preprocessed file.  See 
     http://gcc.gnu.org/bugs.html for instructions.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=750&database=gcc


             reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01  0:00 Robert.C.Haskell [this message]
2003-04-12 11:46 toon

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=20010201181749.20100.qmail@sourceware.cygnus.com \
    --to=robert.c.haskell@rolls-royce.com \
    --cc=gcc-gnats@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: link
Be 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).