public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/94397] [9/10/11 Regression] the compiler consider "type is( real(kind(1.)) )" as a syntax error since r10-7369-gc38daa7976886a59 Date: Thu, 07 May 2020 11:56:15 +0000 [thread overview] Message-ID: <bug-94397-4-797LQoiWxk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94397-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94397 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|10.0 |10.2 --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> --- GCC 10.1 has been released.
next prev parent reply other threads:[~2020-05-07 11:56 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-30 7:06 [Bug fortran/94397] New: [10 Regression] the compiler consider "type is( real(kind(1.)) )" as a syntax error chinoune.mehdi at hotmail dot com 2020-03-30 8:29 ` [Bug fortran/94397] " rguenth at gcc dot gnu.org 2020-03-30 8:58 ` marxin at gcc dot gnu.org 2020-03-30 16:23 ` [Bug fortran/94397] [10 Regression] the compiler consider "type is( real(kind(1.)) )" as a syntax error since r10-7369-gc38daa7976886a59 kargl at gcc dot gnu.org 2020-03-30 16:41 ` sgk at troutmask dot apl.washington.edu 2020-03-31 7:12 ` markeggleston at gcc dot gnu.org 2020-03-31 14:33 ` kargl at gcc dot gnu.org 2020-04-01 7:51 ` markeggleston at gcc dot gnu.org 2020-04-29 20:46 ` [Bug fortran/94397] [9/10 " anlauf at gcc dot gnu.org 2020-04-30 6:41 ` markeggleston at gcc dot gnu.org 2020-05-07 11:56 ` jakub at gcc dot gnu.org [this message] 2020-05-28 12:27 ` [Bug fortran/94397] [9/10/11 " cvs-commit at gcc dot gnu.org 2020-05-28 13:45 ` cvs-commit at gcc dot gnu.org 2020-05-28 15:06 ` cvs-commit at gcc dot gnu.org 2020-05-28 15:08 ` markeggleston 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-94397-4-797LQoiWxk@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).