public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99036] [11/12 Regression] ICE in gfc_current_interface_head, at fortran/interface.c:4699
Date: Wed, 10 Nov 2021 21:04:33 +0000	[thread overview]
Message-ID: <bug-99036-4-rzavMDeZof@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99036-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from kargl at gcc dot gnu.org ---
(In reply to G. Steinmetz from comment #5)
> Another try with a case that is probably/hopefully related.
> The following example with a module and submodule in different files
> is valid for e.g. -std=f2008, but invalid for -std=f2003 or -std=f95 :
> 

Patch posted in comment #1 allows this case to compile.

  parent reply	other threads:[~2021-11-10 21:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 17:44 [Bug fortran/99036] New: [11 " gscfq@t-online.de
2021-02-10  2:01 ` [Bug fortran/99036] " kargl at gcc dot gnu.org
2021-02-10  7:23 ` rguenth at gcc dot gnu.org
2021-02-10  9:09 ` marxin at gcc dot gnu.org
2021-04-27 11:40 ` [Bug fortran/99036] [11/12 " jakub at gcc dot gnu.org
2021-07-28  7:05 ` rguenth at gcc dot gnu.org
2021-11-10 18:01 ` gscfq@t-online.de
2021-11-10 21:04 ` kargl at gcc dot gnu.org [this message]
2022-04-21  7:48 ` rguenth at gcc dot gnu.org
2023-03-20 20:36 ` [Bug fortran/99036] [11/12/13 " anlauf at gcc dot gnu.org
2023-03-20 20:40 ` anlauf at gcc dot gnu.org
2023-03-20 20:58 ` anlauf at gcc dot gnu.org
2023-03-21 19:01 ` cvs-commit at gcc dot gnu.org
2023-03-22 18:00 ` cvs-commit at gcc dot gnu.org
2023-03-24 18:41 ` cvs-commit at gcc dot gnu.org
2023-03-24 18:43 ` 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-99036-4-rzavMDeZof@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).