public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/95316] Offload compilation fails when not all offload compilers are installed that were configured Date: Tue, 26 May 2020 12:42:30 +0000 [thread overview] Message-ID: <bug-95316-4-dEgo1XekLY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95316-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95316 --- Comment #2 from Matthias Klose <doko at debian dot org> --- I see it as a usage regression, because suddenly a developer using the nxptx offloading gets an error message about an unrelated offload compiler that didn't exist before.
next prev parent reply other threads:[~2020-05-26 12:42 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-25 15:56 [Bug other/95316] New: [10 Regression] binary built with -fopenacc fails to run " doko at debian dot org 2020-05-26 7:17 ` [Bug other/95316] " rguenth at gcc dot gnu.org 2020-05-26 8:28 ` [Bug other/95316] Offload compilation fails " tschwinge at gcc dot gnu.org 2020-05-26 12:42 ` doko at debian dot org [this message] 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-06-28 10:40 ` jakub at gcc dot gnu.org 2023-07-07 8:53 ` rguenth at gcc dot gnu.org 2023-07-26 22:30 ` burnus@net-b.de
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-95316-4-dEgo1XekLY@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).