public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/95177] error: array subscript has type char Date: Sat, 18 Dec 2021 08:26:04 +0000 [thread overview] Message-ID: <bug-95177-4-pjYKEpnUpv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95177-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95177 Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #19 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- Patch committed, bug fixed in mainline.
next prev parent reply other threads:[~2021-12-18 8:26 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-17 19:40 [Bug libfortran/95177] New: " roland.illig at gmx dot de 2020-05-19 0:43 ` [Bug libfortran/95177] " kargl at gcc dot gnu.org 2020-05-19 4:38 ` roland.illig at gmx dot de 2020-05-19 12:40 ` egallager at gcc dot gnu.org 2020-05-19 14:52 ` sgk at troutmask dot apl.washington.edu 2020-05-19 16:20 ` msebor at gcc dot gnu.org 2020-05-19 16:34 ` msebor at gcc dot gnu.org 2020-05-20 4:02 ` tkoenig at gcc dot gnu.org 2020-05-20 4:10 ` tkoenig at gcc dot gnu.org 2020-05-20 4:30 ` sgk at troutmask dot apl.washington.edu 2020-05-20 6:19 ` roland.illig at gmx dot de 2021-11-11 16:10 ` egallager at gcc dot gnu.org 2021-11-11 20:29 ` anlauf at gcc dot gnu.org 2021-11-11 21:05 ` tkoenig at gcc dot gnu.org 2021-11-11 22:03 ` anlauf at gcc dot gnu.org 2021-11-14 9:43 ` roland.illig at gmx dot de 2021-12-16 17:39 ` fxcoudert at gcc dot gnu.org 2021-12-16 19:57 ` roland.illig at gmx dot de 2021-12-16 20:23 ` fxcoudert at gcc dot gnu.org 2021-12-18 8:26 ` fxcoudert at gcc dot gnu.org [this message] 2021-12-18 8:26 ` fxcoudert 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-95177-4-pjYKEpnUpv@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).