public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35718] deallocating non-allocated pointer target does not fail
Date: Thu, 10 Dec 2020 16:03:37 +0000	[thread overview]
Message-ID: <bug-35718-4-aUphpwVp2D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-35718-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|pault at gcc dot gnu.org           |unassigned at gcc dot gnu.org

--- Comment #9 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #8)
> We have an unsigned short in our descriptor that we can use
> for keeping track of what we allocated and where.
> 
> So, we have 16 bits. State we can keep around is:
> 
> Type of descriptor: Allocatable, pointer, passed argument.  2 bits.
> 
> Associated: No, allocated, target.  2 bits.
> 
> Contiguous: 1 bit.
> 
> Anything else we would need?  That would still leave us 11 bit in reserve.

Hi Thomas,

That was the intention of the field in the descriptor. I just never got round
to it.

I have unassigned myself since I have a huge backlog of other issues.

Cheers

Paul

  parent reply	other threads:[~2020-12-10 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-35718-4@http.gcc.gnu.org/bugzilla/>
2020-06-14 14:54 ` tkoenig at gcc dot gnu.org
2020-06-14 15:10 ` tkoenig at gcc dot gnu.org
2020-12-10 16:03 ` pault at gcc dot gnu.org [this message]
2020-12-11 18:00 ` dominiq at lps dot ens.fr
2008-03-27 16:01 [Bug fortran/35718] New: " dick dot hendrickson at gmail dot com
2008-03-27 16:50 ` [Bug fortran/35718] " burnus at gcc dot gnu dot org
2008-04-13 20:59 ` tkoenig at gcc dot gnu dot org
2008-08-08 21:14 ` jv244 at cam dot ac dot uk
2008-09-28 19:55 ` pault at gcc dot gnu dot org
2008-11-06  6:24 ` pault at gcc dot gnu dot org
2009-04-06 10:56 ` 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=bug-35718-4-aUphpwVp2D@http.gcc.gnu.org/bugzilla/ \
    --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).