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/29371] Coredump when using -fbounds-check with pointer & nullify
Date: Sat, 14 Oct 2006 13:10:00 -0000	[thread overview]
Message-ID: <20061014131010.3240.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29371-1719@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from pault at gcc dot gnu dot org  2006-10-14 13:10 -------
Subject: Bug 29371

Author: pault
Date: Sat Oct 14 13:09:56 2006
New Revision: 117732

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=117732
Log:
2006-10-14 Paul Thomas <pault@gcc.gnu.org>

        PR fortran/29371
        * trans-expr.c (gfc_trans_pointer_assignment): Add the expression
        for the assignment of null to the data field to se->pre, rather
        than block.     

2006-10-14 Paul Thomas <pault@gcc.gnu.org>

        PR fortran/29371
        * gfortran.dg/nullify_3.f90: New test.

Added:
    trunk/gcc/testsuite/gfortran.dg/nullify_3.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-expr.c
    trunk/gcc/testsuite/ChangeLog


-- 


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


  parent reply	other threads:[~2006-10-14 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 14:29 [Bug fortran/29371] New: " tobias dot burnus at physik dot fu-berlin dot de
2006-10-07 21:23 ` [Bug fortran/29371] " pault at gcc dot gnu dot org
2006-10-07 21:24 ` pault at gcc dot gnu dot org
2006-10-11 20:43 ` pault at gcc dot gnu dot org
2006-10-12  0:15 ` patchapp at dberlin dot org
2006-10-14 13:10 ` pault at gcc dot gnu dot org [this message]
2006-10-14 13:19 ` pault at gcc dot gnu dot org
2006-11-10 21:53 ` 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=20061014131010.3240.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).