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 target/96265] building nvptx-none on aarch64-linux-gnu
Date: Fri, 13 Nov 2020 09:12:18 +0000 [thread overview]
Message-ID: <bug-96265-4-O349kmKe4y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96265-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96265
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|building nvptx-none on |building nvptx-none on
|platforms other than |aarch64-linux-gnu
|x86_64-linux-gnu, e.g. |
|aarch64-linux-gnu and |
|powerpc64le-linux-gnu |
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(Remove powerpc64le-linux-gnu from the summary as this PR is only about
aarch64-linux and GCC is known to work on powerpc64le-linux-gnu.)
(In reply to Matthias Klose from comment #1)
> patch for the target hook posted at
> https://gcc.gnu.org/pipermail/gcc-patches/2020-July/550534.html
This patch has been committed on Fri Jul 24 16:17:44 2020 +0200 as
https://gcc.gnu.org/g:29a14a1a907947fe9e43bce62d3468559f17da97
next prev parent reply other threads:[~2020-11-13 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 11:55 [Bug target/96265] New: building nvptx-none on platforms other than x86_64-linux-gnu, e.g. aarch64-linux-gnu and powerpc64le-linux-gnu doko at debian dot org
2020-07-23 13:58 ` [Bug target/96265] " doko at debian dot org
2020-11-13 9:12 ` burnus at gcc dot gnu.org [this message]
2023-10-23 14:30 ` [Bug target/96265] building nvptx-none on aarch64-linux-gnu mxlol233 at outlook dot com
2024-02-29 17:50 ` pinskia at gcc dot gnu.org
2024-04-09 1:14 ` [Bug ipa/96265] offloading to nvptx-none from aarch64-linux-gnu (and riscv*-linux-gnu) does not work pinskia at gcc dot gnu.org
2024-04-09 1:14 ` pinskia 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-96265-4-O349kmKe4y@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: link
Be 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).