public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "d at domob dot eu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36112] Bounds-checking on character length not working for array-constructors
Date: Sat, 03 May 2008 13:32:00 -0000	[thread overview]
Message-ID: <20080503133149.19704.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36112-15965@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from d at domob dot eu  2008-05-03 13:31 -------
Created an attachment (id=15568)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15568&action=view)
Four test cases for character-array constructors

This "patch" includes four test-cases that should all triger a bounds-checking
runtime error for character-array-constructors (including the one given in the
bug description); currently only one of them does this (also as written above).

I'm not sure about the correct dejagnu-format and the expected error messages,
but of course I'll adapt this during working on the patch if needed.  Are the
tests ok or do I misinterpret what the expected behaviour for them should be?

Do you think we need more tests?  Is there some thing despite character-arrays
that could/should trigger a bounds-checking error, like values with different
KIND parameters?  Do we need succeeding test cases, maybe in combination with
typespecs on array constructors (PR27997) when this is fixed?

Thanks for the comments!


-- 


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


  parent reply	other threads:[~2008-05-03 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 19:05 [Bug fortran/36112] New: " d at domob dot eu
2008-05-03  6:15 ` [Bug fortran/36112] " burnus at gcc dot gnu dot org
2008-05-03 13:32 ` d at domob dot eu [this message]
2008-05-03 13:35 ` d at domob dot eu
2008-05-03 14:46 ` d at domob dot eu
2008-05-03 18:27 ` d at domob dot eu
2008-05-04 11:24 ` d at domob dot eu
2008-06-17 20:25 ` domob at gcc dot gnu dot org
2008-06-17 20:26 ` domob at gcc dot gnu dot org
2008-06-18 13:56 ` domob 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=20080503133149.19704.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).