public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111937] [RISCV][lto][offload] When `NUM_POLY_INT_COEFFS` > 1, the `poly_xxx` made `lto_input_mode_table` unable to parse binary gimple data. Date: Mon, 23 Oct 2023 17:12:24 +0000 [thread overview] Message-ID: <bug-111937-4-6xArtdpvln@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111937-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111937 Thomas Schwinge <tschwinge at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tschwinge at gcc dot gnu.org --- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- Created attachment 56178 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56178&action=edit 0001-WIP-STATIC_ASSERT-MAX_MACHINE_MODE-256.patch (In reply to Xiao Ma from comment #0) > Recently, I wanted to port an open source gpgpu target (a custom > modification of RISCV) to GCC/openmp (Following the approach of gcu and > nvptx, using offloading (https://gcc.gnu.org/wiki/Offloading)). Interesting! Please keep us posted how this works out. > However, the > upstream after this patch > (https://github.com/mxlol233-ventus/gcc/commit/ > 3496ca4e6566fc3c5f1093a0290bb88c34d368f8#diff- > 98b71abedd6e59eb80cb43e75ebb507ffa8bf540ee88aa099c6c7fe7cf90ae3e), > NUM_POLY_INT_COEFFS became greater than 1, while for the x86-64-*-* target, > NUM_POLY_INT_COEFFS=1. This makes it impossible for a RISC-V*-*-* lto1 to > parse the data in the LTO sections (e.g. gnu.offload_lto_*) of the object > files generated by x86-64-*-*. I'm not sure about your initial analysis; I'm not familiar with the code/changes you cite. However, please try building with the attached '0001-WIP-STATIC_ASSERT-MAX_MACHINE_MODE-256.patch'. If that triggers, we've (likely...) found (one of) your issue(s).
next prev parent reply other threads:[~2023-10-23 17:12 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-23 14:06 [Bug target/111937] New: " mxlol233 at outlook dot com 2023-10-23 17:12 ` tschwinge at gcc dot gnu.org [this message] 2023-10-24 1:55 ` [Bug target/111937] " mxlol233 at outlook dot com 2023-10-24 5:42 ` mxlol233 at outlook dot com 2023-10-24 7:27 ` rguenth at gcc dot gnu.org 2023-10-24 7:39 ` mxlol233 at outlook dot com 2024-04-09 1:14 ` pinskia at gcc dot gnu.org 2024-04-09 1:15 ` [Bug target/111937] offloading from x86_64-linux-gnu to riscv*-linux-gnu will have issues 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-111937-4-6xArtdpvln@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).