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: Sun, 04 May 2008 11:24:00 -0000	[thread overview]
Message-ID: <20080504112342.24729.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36112-15965@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from d at domob dot eu  2008-05-04 11:23 -------
Now I believe I found out where the problem might be; as far as I can tell,
gfc_array_ctor_strlen in trans-array.c is the point where we determine the
length of the elements of a character array constructor; in the loop over all
elements, it seems that the output length is overwritten on each iteration,
thus returning the length of the last element, as I reported above.

I can't really tell how this value is used later and if this behaviour is
correct and the error comes later, but breaking the loop there after the first
iteration gives the correct result for the test-case I was looking at, so the
problem might really be there.

Any ideas/suggestions/comments on this?  And now I'll probably really wait...
:D


-- 


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


  parent reply	other threads:[~2008-05-04 11:24 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
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 [this message]
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=20080504112342.24729.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).