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/96102] ICE in check_host_association, at fortran/resolve.c:5994
Date: Sun, 02 Aug 2020 12:27:50 +0000 [thread overview]
Message-ID: <bug-96102-4-ia1KHa0Vg8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96102-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96102
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
--- Comment #3 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 48983
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48983&action=edit
Proposed patch for the PR
Steve's proposed patch caused regressions in host_assoc_function_[1,2].f90.
This one regtests OK.
I don't know if the gcc_assert needs to be retained or not. I will go through
all the possible cases that can arrive here. If the only one is caught by the
condition above, then the assert can go as can the second and third lines in
the condition.
Paul
next prev parent reply other threads:[~2020-08-02 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 17:27 [Bug fortran/96102] New: " gscfq@t-online.de
2020-07-07 17:27 ` [Bug fortran/96102] " gscfq@t-online.de
2020-07-07 21:51 ` kargl at gcc dot gnu.org
2020-08-02 12:27 ` pault at gcc dot gnu.org [this message]
2020-08-10 5:19 ` cvs-commit at gcc dot gnu.org
2020-12-28 12:00 ` pault 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-96102-4-ia1KHa0Vg8@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).