public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29800] -fbounds-check: For derived types, write not also compound name
Date: Wed, 26 Jun 2013 17:59:00 -0000	[thread overview]
Message-ID: <bug-29800-4-PqSLQp6nfA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29800-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Wed Jun 26 15:39:25 2013
New Revision: 200425

URL: http://gcc.gnu.org/viewcvs?rev=200425&root=gcc&view=rev
Log:
2013-06-26  Tobias Burnus  <burnus@net-b.de>

        PR fortran/29800
        * trans-array.c (gfc_conv_array_ref): Improve out-of-bounds
        diagnostic message.
        * trans-array.c (gfc_conv_array_ref): Update prototype.
        * trans-expr.c (gfc_conv_variable): Update call.

2013-06-26  Tobias Burnus  <burnus@net-b.de>

        PR fortran/29800
        * gfortran.dg/bounds_check_17.f90: New.


Added:
    trunk/gcc/testsuite/gfortran.dg/bounds_check_17.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-array.c
    trunk/gcc/fortran/trans-array.h
    trunk/gcc/fortran/trans-expr.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2013-06-26 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-29800-4@http.gcc.gnu.org/bugzilla/>
2013-06-26 10:43 ` burnus at gcc dot gnu.org
2013-06-26 10:45 ` Joost.VandeVondele at mat dot ethz.ch
2013-06-26 17:59 ` burnus at gcc dot gnu.org [this message]
2013-06-26 18:00 ` burnus at gcc dot gnu.org
2013-06-26 18:05 ` Joost.VandeVondele at mat dot ethz.ch
2006-11-10 22:57 [Bug fortran/29800] New: " burnus at gcc dot gnu dot org
2007-01-22 21:32 ` [Bug fortran/29800] " fxcoudert at gcc dot gnu dot org
2010-05-20 17:01 ` dfranke at gcc dot gnu dot 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=bug-29800-4-PqSLQp6nfA@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: 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).