public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/103039] [12 Regression] Segfault with openmp block within a select type block since r12-1016-g0e3b3b77e13cac76 Date: Fri, 18 Mar 2022 16:42:48 +0000 [thread overview] Message-ID: <bug-103039-4-ceXhJLoThY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103039-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103039 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from Tobias Burnus <burnus at gcc dot gnu.org> --- Should be FIXED (on mainline, which will become 12.1) Thanks for the report, Martin – sorry for fixing it not more quickly. Thanks Richard & Jakub for the debugging!
next prev parent reply other threads:[~2022-03-18 16:42 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-02 9:08 [Bug fortran/103039] New: Segfault with openmp block within a select type block mscfd at gmx dot net 2021-11-02 9:12 ` [Bug fortran/103039] " mscfd at gmx dot net 2021-11-02 9:20 ` marxin at gcc dot gnu.org 2021-11-02 10:26 ` [Bug fortran/103039] Segfault with openmp block within a select type block since r12-1016-g0e3b3b77e13cac76 mscfd at gmx dot net 2022-01-25 8:28 ` mscfd at gmx dot net 2022-01-25 9:16 ` [Bug fortran/103039] [12 Regression] " jakub at gcc dot gnu.org 2022-03-09 14:27 ` rguenth at gcc dot gnu.org 2022-03-17 16:41 ` jakub at gcc dot gnu.org 2022-03-18 12:29 ` burnus at gcc dot gnu.org 2022-03-18 12:37 ` jakub at gcc dot gnu.org 2022-03-18 13:50 ` cvs-commit at gcc dot gnu.org 2022-03-18 16:40 ` cvs-commit at gcc dot gnu.org 2022-03-18 16:42 ` burnus at gcc dot gnu.org [this message] 2022-03-21 11:59 ` mscfd at gmx dot net
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-103039-4-ceXhJLoThY@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).