public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Boyce at engineer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108649] allocation segmentation fault for pointer derive type and ICE for final-binding
Date: Fri, 03 Feb 2023 16:19:53 +0000	[thread overview]
Message-ID: <bug-108649-4-zDFH4T6Dxh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108649-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Scott Boyce <Boyce at engineer dot com> ---
(In reply to Jerry DeLisle from comment #6)

Thanks that is excellent news about the finalization.
There also is the issue with the ALLOCATION as well.

Another set of test cases are my Batteries Included Fortran Library (its part
of this project under the folder bif_lib).

The full repository for BiF is located at

https://code.usgs.gov/fortran/bif


I was not sure if I should post that code on here as a separate issue (it has
lots of allocation issues as well with gfortran).

  parent reply	other threads:[~2023-02-03 16:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03  0:07 [Bug fortran/108649] New: " Boyce at engineer dot com
2023-02-03  0:20 ` [Bug fortran/108649] " Boyce at engineer dot com
2023-02-03  0:21 ` Boyce at engineer dot com
2023-02-03  0:21 ` Boyce at engineer dot com
2023-02-03  0:21 ` Boyce at engineer dot com
2023-02-03  0:24 ` Boyce at engineer dot com
2023-02-03  2:21 ` jvdelisle at gcc dot gnu.org
2023-02-03 16:19 ` Boyce at engineer dot com [this message]
2023-02-03 16:22 ` Boyce at engineer dot com

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-108649-4-zDFH4T6Dxh@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).