public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/27766] [meta] -fbounds-check related bugs
Date: Sun, 23 Nov 2008 20:53:00 -0000	[thread overview]
Message-ID: <20081123205231.23024.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27766-10259@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from dominiq at lps dot ens dot fr  2008-11-23 20:52 -------
For gfortran.dg/g77/dnrm2.f the failure comes from the old style array
declaration:

     double precision   dx(1), cutlo, cuthi, hitest, sum, xmax,zero,one

If 'dx(1)' is replaced by 'dx(*)', -fbounds-check does not detect any error
(which may be wrong, but I don't think there is any way to detect the problem
with a local analysis).


-- 


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


  parent reply	other threads:[~2008-11-23 20:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 21:46 [Bug fortran/27766] New: " fxcoudert at gcc dot gnu dot org
2006-05-24 21:51 ` [Bug fortran/27766] " fxcoudert at gcc dot gnu dot org
2006-05-27  9:04 ` fxcoudert at gcc dot gnu dot org
2008-04-30 20:03 ` tkoenig at gcc dot gnu dot org
2008-04-30 20:48 ` tkoenig at gcc dot gnu dot org
2008-11-22 23:54 ` tkoenig at gcc dot gnu dot org
2008-11-23  0:33 ` dominiq at lps dot ens dot fr
2008-11-23  8:56 ` tkoenig at gcc dot gnu dot org
2008-11-23 20:53 ` dominiq at lps dot ens dot fr [this message]
2008-11-23 21:03 ` dominiq at lps dot ens dot fr
2008-11-23 22:40 ` dominiq at lps dot ens dot fr
2009-01-03 20:30 ` dfranke at gcc dot gnu dot org
2009-01-03 21:03 ` dfranke at gcc dot gnu dot org
     [not found] <bug-27766-4@http.gcc.gnu.org/bugzilla/>
2013-06-26 18:00 ` burnus at gcc dot gnu.org
2013-08-09  7:55 ` tkoenig at gcc dot gnu.org

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=20081123205231.23024.qmail@sourceware.org \
    --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: 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).