public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93635] Get ICE instead of error message if user incorrectly equivalences allocateable variables that are in a NAMELIST group
Date: Sun, 21 Jun 2020 19:19:28 +0000	[thread overview]
Message-ID: <bug-93635-4-m0Np2dEOhB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93635-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sun, Jun 21, 2020 at 05:44:51PM +0000, drikosev at gmail dot com wrote:
> 
> The attached patch contains various test cases for the PR's you mentioned at:
> https://groups.google.com/d/msg/comp.lang.fortran/Xu73gGydAJk/X2YXyjndCAAJ
> 
> You simply apply it to your local working tree (ignore whatever fails).
> 
> patch -p0 < gcc48-tc93635-n.patch
> 
> Just ensure that these test cases indeed make some sense; they need a review.
> 

Thanks.  Now, what is needed is someone taking the next
step to becoming a gfortran contributor in the sense 
that she/he can commit changes to source tree.

  parent reply	other threads:[~2020-06-21 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93635-4@http.gcc.gnu.org/bugzilla/>
2020-06-21 17:44 ` drikosev at gmail dot com
2020-06-21 19:19 ` sgk at troutmask dot apl.washington.edu [this message]
2020-06-21 20:07 ` drikosev at gmail dot com
2023-03-13 20:42 ` anlauf at gcc dot gnu.org
2023-03-13 21:08 ` anlauf at gcc dot gnu.org
2024-05-24 19:30 ` cvs-commit at gcc dot gnu.org
2024-05-25 18:57 ` anlauf at gcc dot gnu.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-93635-4-m0Np2dEOhB@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).