public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104968] [nvptx][OpenMP] SIGSEGV / ICE in final_scan_insn_1 Date: Fri, 18 Mar 2022 15:35:47 +0000 [thread overview] Message-ID: <bug-104968-4-qhGIu61njA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104968-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104968 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Target Milestone|--- |12.0 Status|UNCONFIRMED |RESOLVED --- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> --- Fixed by https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=356e2720e9030927579024c2f060d665a0b9080f .
prev parent reply other threads:[~2022-03-18 15:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-17 13:50 [Bug target/104968] New: " burnus at gcc dot gnu.org 2022-03-17 14:18 ` [Bug target/104968] " vries at gcc dot gnu.org 2022-03-17 14:35 ` vries at gcc dot gnu.org 2022-03-17 14:43 ` vries at gcc dot gnu.org 2022-03-17 15:12 ` vries at gcc dot gnu.org 2022-03-17 21:08 ` vries at gcc dot gnu.org 2022-03-18 12:44 ` vries at gcc dot gnu.org 2022-03-18 15:35 ` vries at gcc dot gnu.org [this message]
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-104968-4-qhGIu61njA@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).