public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tobi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/20888] dereferencing NULL still accepted
Date: Thu, 19 May 2005 17:10:00 -0000	[thread overview]
Message-ID: <20050519170958.19217.qmail@sourceware.org> (raw)
In-Reply-To: <20050408160236.20888.jv244@cam.ac.uk>


------- Additional Comments From tobi at gcc dot gnu dot org  2005-05-19 17:09 -------
2005-04-06  Tobias Schl"uter  <tobias.schlueter@physik.uni-muenchen.de>

	* expr.c (gfc_check_assign): Don't allow NULL as rhs in a
	non-pointer assignment.

fixed only part of the cases where NULL is not allowed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tobi at gcc dot gnu dot org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-05-19 17:09:57
               date|                            |
            Summary|error needed                |dereferencing NULL still
                   |                            |accepted


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


  reply	other threads:[~2005-05-19 17:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08 16:02 [Bug fortran/20888] New: error needed jv244 at cam dot ac dot uk
2005-05-19 17:10 ` tobi at gcc dot gnu dot org [this message]
2005-09-30 20:47 ` [Bug fortran/20888] dereferencing NULL still accepted pinskia at gcc dot gnu dot org
     [not found] <bug-20888-6642@http.gcc.gnu.org/bugzilla/>
2007-06-22 18:50 ` patchapp at dberlin dot org
2007-07-03  8:02 ` burnus at gcc dot gnu dot org
2007-07-03 18:08 ` burnus 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=20050519170958.19217.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).