public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/94143] [9/10 Regression] Asynchronous execute_command_line() breaks following synchronous calls Date: Sat, 18 Apr 2020 15:54:17 +0000 [thread overview] Message-ID: <bug-94143-4-lLa8zslKk0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94143-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94143 Thomas Koenig <tkoenig at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-04-18 Keywords| |wrong-code Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- Confirmed. It would be nice to get this fixed before releasing 10.0.
next prev parent reply other threads:[~2020-04-18 15:54 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-11 14:54 [Bug libfortran/94143] New: " trnka at scm dot com 2020-03-12 8:43 ` [Bug libfortran/94143] " rguenth at gcc dot gnu.org 2020-03-12 11:58 ` jakub at gcc dot gnu.org 2020-04-18 15:54 ` tkoenig at gcc dot gnu.org [this message] 2020-05-07 21:05 ` [Bug libfortran/94143] [9/10/11 " anlauf at gcc dot gnu.org 2020-05-08 9:57 ` trnka at scm dot com 2021-06-01 8:16 ` [Bug libfortran/94143] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-27 9:42 ` [Bug libfortran/94143] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:40 ` jakub at gcc dot gnu.org 2023-07-07 10:37 ` [Bug libfortran/94143] [11/12/13/14 " rguenth 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-94143-4-lLa8zslKk0@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).