public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/23091] ICE in gfc_trans_auto_array_allocation Date: Wed, 07 Jun 2006 07:46:00 -0000 [thread overview] Message-ID: <20060607072058.27551.qmail@sourceware.org> (raw) In-Reply-To: <bug-23091-1492@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from pault at gcc dot gnu dot org 2006-06-07 07:20 ------- Subject: Bug 23091 Author: pault Date: Wed Jun 7 07:20:39 2006 New Revision: 114461 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114461 Log: 2006-06-07 Paul Thomas <pault@gcc.gnu.org> PR fortran/23091 * resolve.c (resolve_fl_variable): Error if an automatic object has the SAVE attribute. PR fortran/24168 * expr.c (simplify_intrinsic_op): Transfer the rank and the locus to the simplified expression. PR fortran/25090 PR fortran/25058 * gfortran.h : Add int entry_id to gfc_symbol. * resolve.c : Add static variables current_entry_id and specification_expr. (resolve_variable): During code resolution, check if a reference to a dummy variable in an executable expression is preceded by its appearance as a parameter in an entry. Likewise check its specification expressions. (resolve_code): Update current_entry_id on EXEC_ENTRY. (resolve_charlen, resolve_fl_variable): Set and reset specifiaction_expr. (is_non_constant_shape_array): Do not return on detection of a variable but continue to resolve all the expressions. (resolve_codes): set current_entry_id to an out of range value. 2006-06-07 Paul Thomas <pault@gcc.gnu.org> PR fortran/23091 * gfortran.dg/saved_automatic_1.f90: New test. PR fortran/24168 * gfortran.dg/array_simplify_1.f90: New test. PR fortran/25090 * gfortran.dg/entry_dummy_ref_1.f90: New test. PR fortran/25058 * gfortran.dg/entry_dummy_ref_2.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/array_simplify_1.f90 trunk/gcc/testsuite/gfortran.dg/entry_dummy_ref_1.f90 trunk/gcc/testsuite/gfortran.dg/entry_dummy_ref_2.f90 trunk/gcc/testsuite/gfortran.dg/saved_automatic_1.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/expr.c trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/resolve.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23091
next prev parent reply other threads:[~2006-06-07 7:21 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23091-1492@http.gcc.gnu.org/bugzilla/> 2005-12-22 4:43 ` pinskia at gcc dot gnu dot org 2005-12-30 6:44 ` pinskia at gcc dot gnu dot org 2006-01-05 13:41 ` mimo2 at free dot fr 2006-01-05 14:18 ` pinskia at gcc dot gnu dot org 2006-05-13 23:25 ` pinskia at gcc dot gnu dot org 2006-06-06 14:09 ` paul dot richard dot thomas at cea dot fr 2006-06-06 22:04 ` patchapp at dberlin dot org 2006-06-07 7:46 ` pault at gcc dot gnu dot org [this message] 2006-06-11 22:33 ` pault at gcc dot gnu dot org 2006-06-11 22:36 ` pault at gcc dot gnu dot org 2006-06-20 4:14 ` pinskia at gcc dot gnu dot org 2006-06-20 4:15 ` pinskia at gcc dot gnu dot org 2005-07-27 12:23 [Bug fortran/23091] New: " valera dot veryazov at teokem dot lu dot se 2005-07-27 12:50 ` [Bug fortran/23091] " reichelt at gcc dot gnu dot org 2005-07-27 12:59 ` reichelt at gcc dot gnu dot org 2005-07-27 13:00 ` reichelt 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=20060607072058.27551.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: linkBe 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).