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/15326] ICE with assumed length character strings
Date: Thu, 08 Sep 2005 18:46:00 -0000 [thread overview]
Message-ID: <20050908184630.6379.qmail@sourceware.org> (raw)
In-Reply-To: <20040506164815.15326.Tobias.Schlueter@physik.uni-muenchen.de>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-09-08 18:46 -------
Subject: Bug 15326
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: rsandifo@gcc.gnu.org 2005-09-08 18:46:06
Modified files:
gcc/fortran : ChangeLog trans-array.c trans-expr.c
gcc/testsuite : ChangeLog
Added files:
gcc/testsuite/gfortran.dg: char_result_1.f90 char_result_2.f90
char_result_3.f90 char_result_4.f90
char_result_5.f90 char_result_6.f90
char_result_7.f90 char_result_8.f90
Log message:
PR fortran/15326
* trans-array.c (gfc_add_loop_ss_code): Set ss->string_length in
the GFC_SS_FUNCTION case too.
* trans-expr.c (gfc_conv_function_val): Allow symbols to be bound
to function pointers as well as function decls.
(gfc_interface_sym_mapping, gfc_interface_mapping): New structures.
(gfc_init_interface_mapping, gfc_free_interface_mapping)
(gfc_get_interface_mapping_charlen, gfc_get_interface_mapping_array)
(gfc_set_interface_mapping_bounds, gfc_add_interface_mapping)
(gfc_finish_interface_mapping, gfc_apply_interface_mapping_to_cons)
(gfc_apply_interface_mapping_to_ref)
(gfc_apply_interface_mapping_to_expr)
(gfc_apply_interface_mapping): New functions.
(gfc_conv_function_call): Evaluate the arguments before working
out where the result should go. Make the null pointer case provide
the string length in parmse.string_length. Cope with non-constant
string lengths, using the above functions to evaluate such lengths.
Use a temporary typespec; don't assign to sym->cl->backend_decl.
Don't assign to se->string_length when returning a cached array
descriptor.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&r1=1.540&r2=1.541
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans-array.c.diff?cvsroot=gcc&r1=1.56&r2=1.57
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans-expr.c.diff?cvsroot=gcc&r1=1.59&r2=1.60
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.6030&r2=1.6031
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/char_result_1.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/char_result_2.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/char_result_3.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/char_result_4.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/char_result_5.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/char_result_6.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/char_result_7.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/char_result_8.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15326
next prev parent reply other threads:[~2005-09-08 18:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 16:48 [Bug fortran/15326] New: [gfortran] " Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-05-06 17:08 ` [Bug fortran/15326] " Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-05-06 18:02 ` pinskia at gcc dot gnu dot org
2004-05-27 3:08 ` pinskia at gcc dot gnu dot org
2004-06-13 9:25 ` pinskia at gcc dot gnu dot org
2004-06-27 20:30 ` [Bug fortran/15326] " pinskia at gcc dot gnu dot org
2004-08-09 15:56 ` pinskia at gcc dot gnu dot org
2004-09-25 15:04 ` tobi at gcc dot gnu dot org
2004-10-10 21:04 ` tobi at gcc dot gnu dot org
2004-10-10 21:08 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-01-06 14:40 ` tobi at gcc dot gnu dot org
2005-02-12 21:55 ` pinskia at gcc dot gnu dot org
2005-08-31 15:26 ` pinskia at gcc dot gnu dot org
2005-08-31 20:54 ` rsandifo at gcc dot gnu dot org
2005-09-08 18:46 ` cvs-commit at gcc dot gnu dot org [this message]
2005-09-08 18:51 ` rsandifo at gcc dot gnu dot org
2005-09-18 19:53 ` [Bug fortran/15326] [4.0 only] " tkoenig at gcc dot gnu dot org
2005-09-18 20:09 ` rsandifo at gcc dot gnu dot org
2005-09-18 20:27 ` 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=20050908184630.6379.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).