public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/14067] [gfortran]  ICE when character data statement overflows declared size
Date: Mon, 31 May 2004 17:58:00 -0000	[thread overview]
Message-ID: <20040530163332.992.qmail@sourceware.org> (raw)
In-Reply-To: <20040207205100.14067.bdavis9659@comcast.net>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-05-30 16:33 -------
Subject: Bug 14067

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	tobi@gcc.gnu.org	2004-05-30 16:33:29

Modified files:
	gcc/fortran    : ChangeLog trans-const.c 

Log message:
	PR fortran/14067
	* trans-const.c (gfc_conv_string_init): Allow variable string
	length lower than initialization string length.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&r1=1.53&r2=1.54
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans-const.c.diff?cvsroot=gcc&r1=1.4&r2=1.5



-- 


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


  parent reply	other threads:[~2004-05-30 16:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07 20:51 [Bug fortran/14067] New: " bdavis9659 at comcast dot net
2004-02-07 22:17 ` [Bug fortran/14067] " pinskia at gcc dot gnu dot org
2004-05-26 11:48 ` pinskia at gcc dot gnu dot org
2004-05-31 16:45 ` pinskia at gcc dot gnu dot org
2004-05-31 17:09 ` tobi at gcc dot gnu dot org
2004-05-31 17:58 ` cvs-commit at gcc dot gnu dot org [this message]
2004-05-31 18:32 ` [Bug fortran/14067] [gfortran] no warning " tobi at gcc dot gnu dot org
2005-01-06 14:40 ` [Bug fortran/14067] " tobi at gcc dot gnu dot org
2005-03-26 17:48 ` pinskia 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=20040530163332.992.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).