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/35680] [4.3/4.4 regression] ICE on invalid transfer in variable declaration Date: Sat, 11 Oct 2008 10:01:00 -0000 [thread overview] Message-ID: <20081011100000.9922.qmail@sourceware.org> (raw) In-Reply-To: <bug-35680-10259@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from pault at gcc dot gnu dot org 2008-10-11 09:59 ------- Subject: Bug 35680 Author: pault Date: Sat Oct 11 09:58:38 2008 New Revision: 141056 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=141056 Log: 2008-10-11 Paul Thomas <pault@gcc.gnu.org> PR fortran/35680 * gfortran.h : Add 'error' bit field to gfc_expr structure. * expr.c (check_inquiry): When checking a restricted expression check that arguments are either variables or restricted. (check_restricted): Do not emit error if the expression has 'error' set. Clean up detection of host-associated variable. 2008-10-11 Paul Thomas <pault@gcc.gnu.org> PR fortran/35680 * gfortran.dg/transfer_array_intrinsic_5.f90: New test. Added: branches/gcc-4_3-branch/gcc/testsuite/gfortran.dg/transfer_array_intrinsic_5.f90 Modified: branches/gcc-4_3-branch/gcc/fortran/ChangeLog branches/gcc-4_3-branch/gcc/fortran/expr.c branches/gcc-4_3-branch/gcc/fortran/gfortran.h branches/gcc-4_3-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35680
next prev parent reply other threads:[~2008-10-11 10:01 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-24 18:45 [Bug fortran/35680] New: " fxcoudert at gcc dot gnu dot org 2008-03-25 20:46 ` [Bug fortran/35680] " pault at gcc dot gnu dot org 2008-03-25 23:18 ` burnus at gcc dot gnu dot org 2008-03-27 22:26 ` rguenth at gcc dot gnu dot org 2008-06-06 15:04 ` rguenth at gcc dot gnu dot org 2008-07-22 12:12 ` burnus at gcc dot gnu dot org 2008-08-27 22:08 ` jsm28 at gcc dot gnu dot org 2008-09-17 8:56 ` pault at gcc dot gnu dot org 2008-09-28 19:34 ` pault at gcc dot gnu dot org 2008-09-28 19:50 ` pault at gcc dot gnu dot org 2008-09-28 20:51 ` dominiq at lps dot ens dot fr 2008-09-29 20:26 ` dominiq at lps dot ens dot fr 2008-10-02 15:22 ` pault at gcc dot gnu dot org 2008-10-02 15:49 ` dominiq at lps dot ens dot fr 2008-10-03 12:14 ` pault at gcc dot gnu dot org 2008-10-03 22:24 ` dominiq at lps dot ens dot fr 2008-10-04 11:57 ` pault at gcc dot gnu dot org 2008-10-05 18:56 ` pault at gcc dot gnu dot org 2008-10-11 10:01 ` pault at gcc dot gnu dot org [this message] 2008-10-11 10:03 ` pault 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=20081011100000.9922.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).