public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth 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: Tue, 24 Oct 2023 07:27:52 +0000 [thread overview] Message-ID: <bug-111937-4-NFOuRvqqZj@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org, | |rsandifo at gcc dot gnu.org --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- The host and the target compiler have to be "similar" enough for the LTO bytecode to be transferable. May I suggest to use aarch64 with SVE as host instead? I fear differing NUM_POLY_INT_COEFFS is almost impossible to support. Well, we could maybe stream NUM_POLY_INT_COEFFS and adjust reading to rewrite to the target supported number - rewriting from 1 to 2 should be possible but I'm not sure how to handle the reverse ...
next prev parent reply other threads:[~2023-10-24 7:27 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 ` [Bug target/111937] " tschwinge at gcc dot gnu.org 2023-10-24 1:55 ` 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 [this message] 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-NFOuRvqqZj@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).