public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/103796] ICE in gfc_conv_expr_val, at fortran/trans-expr.c:9446 since r8-6395-gf8862a1b2afad9d1 Date: Sat, 08 Jul 2023 14:28:07 +0000 [thread overview] Message-ID: <bug-103796-4-OwFJWvnfjY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103796-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103796 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |--- Status|RESOLVED |REOPENED --- Comment #9 from anlauf at gcc dot gnu.org --- Steve correctly noted in pr105526#c5 that his patch provides parsing of the form-team-spec-list, although it will only emit a sorry-type error message for a not implemented feature, instead of a syntax error. Reopening, so that his patch won't be lost. This PR might be referenced in a suitable coarray meta-bug.
next prev parent reply other threads:[~2023-07-08 14:28 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-21 18:19 [Bug fortran/103796] New: ICE in gfc_conv_expr_val, at fortran/trans-expr.c:9446 gscfq@t-online.de 2021-12-22 8:45 ` [Bug fortran/103796] ICE in gfc_conv_expr_val, at fortran/trans-expr.c:9446 since r8-6395-gf8862a1b2afad9d1 marxin at gcc dot gnu.org 2021-12-22 21:10 ` kargl at gcc dot gnu.org 2021-12-22 23:21 ` kargl at gcc dot gnu.org 2021-12-22 23:21 ` kargl at gcc dot gnu.org 2023-05-29 23:50 ` kargl at gcc dot gnu.org 2023-07-04 21:34 ` jvdelisle at gcc dot gnu.org 2023-07-07 17:50 ` sgk at troutmask dot apl.washington.edu 2023-07-07 18:19 ` anlauf at gcc dot gnu.org 2023-07-08 14:28 ` anlauf at gcc dot gnu.org [this message] 2023-07-08 17:04 ` [Bug fortran/103796] form-team-spec-list is unsupported kargl 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-103796-4-OwFJWvnfjY@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: linkBe 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).