public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/97224] [8/9/10/11 Regression] SPECCPU 2006 Gamess fails to build after g:e5a76af3a2f3324efc60b4b2778ffb29d5c377bc Date: Mon, 07 Dec 2020 08:32:16 +0000 [thread overview] Message-ID: <bug-97224-4-UkzDDEE9Vc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97224-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97224 --- Comment #12 from Tamar Christina <tnfchris at gcc dot gnu.org> --- @Martin I believe this was re-opened as the patch was reverted on master but was still pending reverts on the release branches. @Mark I assume you committed the reverts to the branches too?
next prev parent reply other threads:[~2020-12-07 8:32 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-28 9:48 [Bug fortran/97224] New: " tnfchris at gcc dot gnu.org 2020-09-28 10:06 ` [Bug fortran/97224] " mark.eggleston at codethink dot co.uk 2020-09-28 10:14 ` markeggleston at gcc dot gnu.org 2020-09-28 10:15 ` tnfchris at gcc dot gnu.org 2020-09-28 10:43 ` jakub at gcc dot gnu.org 2020-09-28 11:01 ` mark.eggleston at codethink dot co.uk 2020-09-28 11:19 ` rguenth at gcc dot gnu.org 2020-09-28 14:42 ` sgk at troutmask dot apl.washington.edu 2020-09-29 11:24 ` drikosev at gmail dot com 2020-10-02 14:33 ` drikosev at gmail dot com 2020-10-04 12:47 ` dominiq at lps dot ens.fr 2020-10-04 15:02 ` drikosev at gmail dot com 2020-12-04 14:16 ` marxin at gcc dot gnu.org 2020-12-07 8:32 ` tnfchris at gcc dot gnu.org [this message] 2020-12-07 14:31 ` marxin 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-97224-4-UkzDDEE9Vc@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).