public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mxlol233 at outlook dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96265] building nvptx-none on aarch64-linux-gnu Date: Mon, 23 Oct 2023 14:30:38 +0000 [thread overview] Message-ID: <bug-96265-4-12fOG2pTJ3@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 Xiao Ma <mxlol233 at outlook dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mxlol233 at outlook dot com --- Comment #3 from Xiao Ma <mxlol233 at outlook dot com> --- I think this issue and #111937 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111937) have the same root cause: aarch64 also sets NUM_POLY_INT_COEFFS to 2, which makes it incompatible with the default value for nvptx (which is 1).
next prev parent reply other threads:[~2023-10-23 14:30 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 ` [Bug target/96265] building nvptx-none on aarch64-linux-gnu burnus at gcc dot gnu.org 2023-10-23 14:30 ` mxlol233 at outlook dot com [this message] 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-12fOG2pTJ3@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).